Hello, after migrating to a new registrar Im not able to reconfigure my netlify site. Removed the original one and started fresh, then changed the NS on the new hosting site to point to Netlify
Seems like the domain is still pointing to your registrar’s nameservers. You may want to double check that you have changed that to Netlify’s nameservers.
The nameserver changes for plasticamurillo.com are still propagating, so in some cases NS will show Netlify, in other cases your registrar. This is evident on the DNS Checker link you posted.
DNS changes do take up to 48 Hours or according to NS1, even up to 72 hours. Usually propagation happens within an hour or so.
If you check the whois record for your domain at ICANN Lookup, you will see that the nameservers are still pointing to your registrar.
What you seems to have done, is add NS records on your registrar’s DNS system.
The top result is the NS record currently stored by the .com registry, and the bottom is the NS record stored by the nameservers on the .com registry (i.e. IONOS UI-DNS nameservers). As you can see there’s a mismatch there.
This will result in an unexpected behavior. Some DNS resolver will resolve your domain successfully using Netlify DNS (the NS1 nameservers), while other will query the nameserver listed on the registry nameservers (the IONOS UI-DNS nameservers).
Ok I contacted IONOS and they said everything is done on their side. If you see the DNS
Everything has been propagated already… However ICANN Lookup
still shows the old ones… Should I contact Icann automatically, it has been a few days already. That is weird.
Mainly, Google DNS, OpenDNS and Cloudflare DNS wouldn’t resolve your domain.
So DNS form a chain. When someone wants to find out what IP addresses plasticamurillo.com resolved to, it will first go to the root servers, which will then direct the request to the .com nameservers.
In this case, the .com nameservers would direct user to the IONOS’ nameservers, which have no knowledge of any A record for your domain. Thus, some user will get ERR_NAME_NOT_RESOLVED.
What you want to do is set it so that the Netlify’s nameservers are used instead of IONOS’.
Hi @coelmay Yes all added and re-added after see screenshot. Something is missing but not really know what to do now, IONOS (the domain registrar) is sending me to netlify…
When I test using dig ... +trace ... as specified in that guide I see.
% dig plasticamurillo.com NS +trace | tail -6
plasticamurillo.com. 86400 IN NS dns1.p04.nsone.net.
plasticamurillo.com. 86400 IN NS dns2.p04.nsone.net.
plasticamurillo.com. 86400 IN NS dns3.p04.nsone.net.
plasticamurillo.com. 86400 IN NS dns4.p04.nsone.net.
;; Received 137 bytes from 2001:8d8:fe:53:0:d9a0:533b:100#53(ns1059.ui-dns.org) in 315 ms
So, based on that guide, the registrar’s nameservers answered my request, NOT Netlify’s.
Many thanks all for your help. At the end I contacted IONOS one more time and they refreshed the DNS on their side, now NS seems to be correct and website up and running.
dig plasticamurillo.com NS +trace | tail -6
plasticamurillo.com. 3600 IN NS dns1.p04.nsone.net.
plasticamurillo.com. 3600 IN NS dns2.p04.nsone.net.
plasticamurillo.com. 3600 IN NS dns3.p04.nsone.net.
plasticamurillo.com. 3600 IN NS dns4.p04.nsone.net.
;; Received 137 bytes from 198.51.44.68#53(dns3.p04.nsone.net) in 57 ms