Although this is massively discussed, we have already gone through all the suggested options and verifications.
We have transferred the domain garnachasolutions.com to Cloudflare a few months ago, when checking NS propagation using Dnschecker it seems to be complete, but there are two A records that are still showing mismatching IPs.
These are the only entries for ns1. and ns2. and yet, when we do a search using Dns checker we can see that some locations are seeing the IP 18.104.22.168
We have already tried to change TTL, delete the entries and recreate, and they always come back as this (showing the correct IP for some locations and wrong for others). Our last resource will be a Registrar transfer (current one is GoDaddy).
Any suggestions will be highly appreciated.
They resolve just fine.
nslookup ns1.garnachasolutions.com wilson.ns.cloudflare.com
nslookup ns2.garnachasolutions.com wilson.ns.cloudflare.com
If you still get wrong addresses, that will be a local propagation issue with that particular resolver.
Yes, it’s resolving to the right IP when using Cloudflare, Google, OpenDNS, but still returning the old IP for customers in some regions using local providers (and we confirmed that through DNSmap and DNSchecker).
We’ll try to transfer the registrar, this domain is behaving awkwardly since when its DNS was still being managed from GoDaddy.
The registrar should not make a difference. The authoritative server is Cloudflare and Cloudflare returns the right address. If you get the wrong address somewhere else that will be an issue with these resolvers and is probably propagation related.
Technically I perfectly understand that, but there are dozens of regional servers not recognizing this propagation even after months, so we are kind of without options.
This is a Server in South Africa:
nslookup ns2.garnachasolutions.com 22.214.171.124
This is in Austria:
nslookup ns2.garnachasolutions.com 126.96.36.199
I understand that, but that’s still a question for those running these resolvers. The authority returns the right records and everything else is beyond the control of the authority.
If you have changed these records recently I’d suggest you just wait until propagation settled. Otherwise you might want to contact them to refresh their resolvers. Nothing Cloudflare can do.
Thank you for your suggestion.
I’ll try to reach some of these and see what happens.
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.