DNS Record not found

Community Support
1

I have configured the DNS on the server and at the registrar and pointed the name to the server. netmack.com with the IP also added.
But 4 hours later I still get ‘A record not found’ while those days all domains propagate withing even 60 minutes.
Is something else wrong?

2

I’ve checked your domain and .net dns servers resolve correctly your ns and glue a records:

$ dig @e.gtld-servers.net netmack.com ns

; <<>> DiG 9.18.19-1~deb12u1-Debian <<>> @e.gtld-servers.net netmack.com ns
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17979
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 3
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;netmack.com.                   IN      NS

;; AUTHORITY SECTION:
netmack.com.            172800  IN      NS      ns1.netmack.com.
netmack.com.            172800  IN      NS      ns2.netmack.com.

;; ADDITIONAL SECTION:
ns1.netmack.com.        172800  IN      A       172.107.203.43
ns2.netmack.com.        172800  IN      A       172.107.203.43

;; Query time: 3 msec
;; SERVER: 192.12.94.30#53(e.gtld-servers.net) (UDP)
;; WHEN: Sat Jan 20 12:20:37 CET 2024
;; MSG SIZE  rcvd: 108

But seems your server is not answering for dns queries:

dig @172.107.203.43 netmack.com ns
;; communications error to 172.107.203.43#53: timed out
;; communications error to 172.107.203.43#53: timed out
;; communications error to 172.107.203.43#53: timed out

; <<>> DiG 9.18.19-1~deb12u1-Debian <<>> @172.107.203.43 netmack.com ns
; (1 server found)
;; global options: +cmd
;; no servers could be reached

Also, seems all your ports are closed/filtered:

Starting Nmap 7.80 ( https://nmap.org ) at 2024-01-20 12:18 CET
Initiating SYN Stealth Scan at 12:18
Scanning 172.107.203.43 [65535 ports]
Completed SYN Stealth Scan at 12:18, 27.27s elapsed (65535 total ports)
Nmap scan report for 172.107.203.43
Host is up, received user-set.
All 65535 scanned ports on 172.107.203.43 are filtered because of 65535 no-responses

Read data files from: /usr/bin/../share/nmap
Nmap done: 1 IP address (1 host up) scanned in 27.35 seconds
           Raw packets sent: 131070 (5.767MB) | Rcvd: 0 (0B)
1 Like
3

Ok Thanks.

So I got to find the command to open my ports then.

4

From your Hestia server you can view the open ports from Web UI or from command line:

v-list-firewall

But I think that the firewall that is blocking all is outside your server, check in your hosting provider control panel because I guess the firewall is active there.

1 Like
5

2024-01-20_170116
2024-01-20_170116759×376 8.25 KB

Here a pic of it. Will check hosting cp now.

6

Algunos proveedores de VPS o hosting no te permiten iniciar tu propio bind9, pero sí te dan acceso para modificar el dns desde su portal.

Verifica con tu proveedor

Some VPS or hosting providers do not allow you to start your own bind9, but they do give you access to modify the DNS from their portal.

Check with your provider