0

I forwarded my domain to the Azure DNS nameservers:

ns1-01.azure-dns.com.
ns2-01.azure-dns.net.
ns3-01.azure-dns.org.
ns4-01.azure-dns.info.

That's an NS record on the Azure side. The registrar is ...not entirely important, as far as I know, but it's Ionos.

I have two servers on different sides of the world. One is an Azure VM. The A records used to just point to that VM. I am now trying to redirect some of the records to my new server; e.g. @.mydomain.org, with CNAME www.mydomain.org.

This wasn't my problem. I don't have any inaccurate records. I do not know if it could be this because I'm not sure how to check the routers of the nameservers. The four nameservers above all return the address I want; 1.1.1.1 and 8.8.8.8 return the old IP. It's been 24 hours since I changed these records and the original TTL was 12 hours. I've since set that to ten minutes (600s).

I have never had this happen before with DNS so I don't have the foggiest idea of how to fix it. Any suggestions or advice would be appreciated. Happy to post more information if it is helpful.

Chaim Eliyah
  • 193

1 Answers1

1

You probably need to look at your registrar again. A quick whois shows they're still announcing ui-dns servers for the name servers. Changing the NS records is not the same as pointing your domain name to a different set of DNS servers. Most registrars will have an option to either host dns or use a different dns provider.

This guide might be helpful, assuming this wasn't what you followed before.

For reference this is what I see when I run a whois: 

$ whois machetessl.org | grep Name 
Domain Name: MACHETESSL.ORG
Name Server: NS1068.UI-DNS.DE 
Name Server: NS1068.UI-DNS.COM 
Name Server: NS1068.UI-DNS.BIZ 
Name Server: NS1068.UI-DNS.ORG

Because these aren't Azure, no matter what you do in Azure won't matter.

Jon Angliss
  • 1,782