DNS not resolving although nameservers are running
I installed cPanel on Ubuntu 20.04 operating system on Google Cloud.
Although my hostname and nameserver addresses work, my queries on dnschecker.org are not resolved on some country servers. When I query dnschecker again, the closed country opens, the others are closed. I had this problem on Amazon EC2 as well as on google cloud.
There were no such problems in google cloud centos 7 before. I installed Almalinux and tried it, it still didn't work.
-
I installed cPanel on Ubuntu 20.04 operating system on Google Cloud. Hostname: lily.zumuhost.com NS: ns1.zumuhost.com ns2.zumuhost.com Although my hostname and nameserver addresses work, my queries on dnschecker.org are not resolved on some country servers. When I query dnschecker again, the closed country opens, the others are closed. I had this problem on Amazon EC2 as well as on google cloud. There were no such problems in google cloud centos 7 before. I installed Almalinux and tried it, it still didn't work.
I"ve checked the ns. It working fine0 -
I also am not seeing any issues with the DNS on my end when I check using a tool like intodns.com. If you're seeing intermittent problems with the DNS connecting, it would be best to reach out to your hosting provider or datacenter and have them do some additional testing. 0 -
intodns problem this issue already exists on some country servers. dnschecker will give more accurate results. something is not right 0 -
I"ve checked the ns. It working fine
There are problems in countries like T"rkiye and we are in Turkey. It was working fine for Turkey on Centos 7 installed on Google Cloud.0 -
intodns problem this issue already exists on some country servers. dnschecker will give more accurate results. something is not right
Even this query shows the old google server's ip. Why does the old server IP appear from Turkey even though the a records are up to date? Two different companies show in two different ways. I will go crazy0 -
Did you recently make a DNS change? If so, this could just be propagation that you're seeing. 0 -
It has been 4 days since the DNS change was made. Every time you press renew on DNSchecker site, T"rkiye gives a response, not a response. 0 -
Did you recently make a DNS change? If so, this could just be propagation that you're seeing.
Could it be that my restoring the backups from the old server to the new server with restorepkg is causing this issue?0 -
Anything is possible - this would really be best handled in a ticket so we can have access to both machines and see all the affected IP addresses. 0 -
Should I open a ticket and share root information? 0 -
You certainly could - just let me know the ticket number here once that's done so I can follow along. 0
Please sign in to leave a comment.
Comments
12 comments