DNS Server is not working properly.

[hmaddy]

Domain dns management system is not working properly. All the domains are not propagating properly. When we change to Cloudflare, it will work correctly. On our server its not working. All the entries are correct. but i dont know whats happening and how it can solve. its happening only on hetzner servers.

is it any resolver issue on hetzner sever.

 

[hmaddy]

when dig A domain its showing correct IP and when check with leafdns and intodns its showing old ip. How to solve it

 

[cPanelWilliam]

Hello! You mentioned that the domains show the 'old' IP on leafdns and intodns. Is it only the domain's A record that is showing the old IP, or are the nameservers showing the old IP as well? Initially, you stated the domains are not propagating. Did you recently perform a server migration, and the domains are still incorrectly resolving to the old server?

 

[hmaddy]

recently we migrated the server to new server. after that we changed the name server ips with new one. After that all these issues happened. most of the websites are down in many locations. so we checked the dns settings like A records. All are correct and when we check on leafdns and intodns, its also showing the old server ip.

 

[cPanelWilliam]

Hi, did you already ensure the nameservers IP's were updated at both the domain registrar and within the DNS zones on the server? Additionally, if many of the websites are down, it could mean that port 53 TCP/UDP is blocked on the Hetzner server, as that would prevent domains from resolving.

If you've already checked both of these things, I'd suggest opening a ticket so our team can take a closer look. There are many moving parts when it comes to troubleshooting DNS, so having access to the server can significantly help determine the cause of the problem.

 

[hmaddy]

How to check the port is disabled or not

 

[keatonhj]

Broken. A Records show new IP's in DNS Zones editor.
It is NOT propagating to DNS servers.
When I try to edit the zones I get the error (The "serial" argument cannot be empty. )

This is a monumental clusterf*ck to an extent I've never seen before. It's such a high priority bug to fix as it completely breaks websites.
Should I completely abandon CPanel or are you guys urgently fixing it?

 

[cPRex]

@keatonhj - can you please get me more details on the situation you're seeing? If you aren't able to edit the zones through WHM, can you run this command against the zone file to see if you get more details?

named-checkzone domain.com /var/named/domain.com.db

Just change both "domain.com" entries to the specific zone file you're working with.

 

[hmaddy]

named-checkzone abcd.com /var/named/abcd.com.db
zone abcd.com/IN: loaded serial 2022120301
OK

 

[cPRex]

@hmaddy - that was meant for the other user that had replied.

 

[hmaddy]

am also facing this issues on more than 5 servers

 

[cPRex]

Can you submit a ticket to our team so we can check the configuration?