New Directadmin install and DNS problem from start

# dig atvprojekt.pl @78.9.100.211

; <<>> DiG 9.16.48-Debian <<>> atvprojekt.pl @78.9.100.211
;; global options: +cmd
;; connection timed out; no servers could be reached
Click to expand...
 
something wrong with your bind/named.

maybe UDP 53 closed/nat ?
 
Ok, but nmap from outer server looks like:

:~# nmap ns1.interaktywa.com.pl
Starting Nmap 7.93 ( https://nmap.org ) at 2024-06-14 19:35 UTC
Nmap scan report for ns1.interaktywa.com.pl (78.9.100.211)
Host is up (0.048s latency).
rDNS record for 78.9.100.211: 78-9-100-211.actus-info.pl
Not shown: 984 filtered tcp ports (no-response)
PORT STATE SERVICE
20/tcp closed ftp-data
21/tcp open ftp
22/tcp open ssh
25/tcp open smtp
53/tcp open domain
80/tcp open http
110/tcp open pop3
143/tcp open imap
443/tcp open https
465/tcp open smtps
587/tcp open submission
993/tcp open imaps
995/tcp open pop3s
2222/tcp open EtherNetIP-1
8080/tcp open http-proxy
35500/tcp closed unknown

Nmap done: 1 IP address (1 host up) scanned in 11.27 seconds
Click to expand...
 
Bind use UDP, not TCP.

did your bind still working or not ?
dig with "127.0.0.1" on the same server, should show result normally.
 
Outer server:
:~# dig atvprojekt.pl @127.0.0.1
;; communications error to 127.0.0.1#53: connection refused
;; communications error to 127.0.0.1#53: connection refused
;; communications error to 127.0.0.1#53: connection refused

; <<>> DiG 9.18.16-1~deb12u1-Debian <<>> atvprojekt.pl @127.0.0.1
;; global options: +cmd
;; no servers could be reached
Click to expand...
Lan server:
:~# dig atvprojekt.pl @127.0.0.1

; <<>> DiG 9.16.48-Debian <<>> atvprojekt.pl @127.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49561
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: 50ab4d4fa992e68f01000000666c9d5cb17075610ad63048 (good)
;; QUESTION SECTION:
;atvprojekt.pl. IN A

;; ANSWER SECTION:
atvprojekt.pl. 3600 IN A 78.9.100.211

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri Jun 14 21:43:24 CEST 2024
;; MSG SIZE rcvd: 86
Click to expand...
 
outer server:
:~# dig atvprojekt.pl @ns1.interaktywa.com.pl
;; communications error to 78.9.100.211#53: timed out
;; communications error to 78.9.100.211#53: timed out
;; communications error to 78.9.100.211#53: timed out

; <<>> DiG 9.18.16-1~deb12u1-Debian <<>> atvprojekt.pl @ns1.interaktywa.com.pl
;; global options: +cmd
;; no servers could be reached
Click to expand...
 
Port forwarding on router like below, and DMZ set to 192.168.1.150 (LAN IP of server)

1718395039298.png
 
Yeah it should work, but you already know how to debug this issued, just fixed port 53 and re-check like you do in post #26

Or your ISP just block UDP 53 in their backend.
 
I don't work with home DNS so can't help you, but I can tell you that most likely you have a local firewall issue.

See your message #25 in outer server:
;; communications error to 127.0.0.1#53: connection refused
Click to expand...
You should -always- be able to access any port on localhost, so if something is even blocking localhost access, then outside it will never work.
Check your server.
 
I have other DA server which is in datacenter and I'm using the same outside DNS in my server and it works ok.
I wanted to run my home test server using same method, my ISP confirmed that is not blocking anything on my internet access, it looks like I have got wrong config on my local home DA server?
 
I'm not sure, I never seen router panel like that. but we can confirm that something blocked connection to your server.

maybe some other config ? trying play with your router in all function.


if all default install from directadmin setup, it should work fine in all server interface.
 
You must log in or register to reply here.
Back
Top