Solved Nameservers IP blocked?

[Krisauseu]

Hi,

I have become a second IP for my server, just for use as needed for the 2nd DNS nameserver. I could also assign the Nameserver to the different IPs in DA.



But when I check this with dig lowendhost.de NS @ns1.lowendhost.de I get the following:

; <<>> DiG 9.18.24-1-Debian <<>> lowendhost.de NS @ns1.lowendhost.de
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43421
;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 3
;; WARNING: recursion requested but not available
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: f7a7199c697fd0aa010000006661e3e11bc3bbbc77775b20 (good)
;; QUESTION SECTION:
;lowendhost.de. IN NS
;; ANSWER SECTION:
lowendhost.de. 3600 IN NS ns1.lowendhost.de.
lowendhost.de. 3600 IN NS ns2.lowendhost.de.
;; ADDITIONAL SECTION:
ns1.lowendhost.de. 3600 IN A 185.162.248.247
ns2.lowendhost.de. 3600 IN A 188.68.44.56
;; Query time: 7 msec
;; SERVER: 185.162.248.247#53(ns1.lowendhost.de) (UDP)
;; WHEN: Thu Jun 06 18:29:21 CEST 2024
;; MSG SIZE rcvd: 138

root@server:~# dig lowendhost.de NS @ns2.lowendhost.de
;; communications error to 88.68.44.56#53: host unreachable

For me ns1 looks good, while ns2.lowendhost.de resolves although its correct IP, but is blocked by anything else to send more data.. This is the additional IP which I've ordered for my server. Is that something to configure in bind, in firewall or in Debian Network configuration?

Regards Kristian

 

[Richard G]

but is blocked by anything else to send more data..

What do you mean. What is blocked?

Did you take into account that changing nameservers take time to synchronise?
When looking at intodns.com at this moment your nameservers are not pointing to your server at this moment. Did you change them at your registrar? I'm still seeing this:

lowendhost.de.          3600    IN      NS      pns53.cloudns.net.
lowendhost.de.          3600    IN      NS      pns52.cloudns.net.
lowendhost.de.          3600    IN      NS      pns51.cloudns.net.
lowendhost.de.          3600    IN      NS      pns54.cloudns.net.

So it's either not changed at your registrar or you did change it, but then it can take 4-24 hours to synchronise.

 

[Krisauseu]

Ah okay, thank you. I just forgot to change the name servers at domain registrar (which is in this case CloudNS, too).

I just made this and looked at into DNS: the first time I see nothing in yellow or red marked there