Saladiator
New Member
- Impact
- 0
Hey All,
I was hoping I could get some assistance with an issue I’m having with a few of my GTLD domains. I updated my domain’s nameservers (let’s say MYDOMAIN.ONE) 72 hours ago via the name.com control panel, but my new nameservers haven’t propagated yet.
Not unheard of, but I think I have a bigger issue. The .one authoritative nameservers (a.nic.one, b.nic.one, c.nic.one, d.nic.one) are still serving the old AND the new nameservers when queried directly. Propagation is working as expected, but since authoritative nameservers are still serving the old nameservers at least 50% of the time, non-authoritative dns servers are still caching the old entry thinking it’s valid.
I verified this using DIG against the .one authoritative nameservers (a.nic.one, b.nic.one, c.nic.one, d.nic.one)
$ DIG NS MYDOMAIN.ONE @a.nic.one
;; AUTHORITY SECTION:
mydomain.one. 3600 IN NS ns1.NEWNS.com
mydomain.one. 3600 IN NS ns2.NEWNS.com
Then a few seconds later…same command, different nameservers
$ DIG NS MYDOMAIN.ONE @a.nic.one
;; AUTHORITY SECTION:
mydomain.one. 3600 IN NS ns1.OLDNS.com
mydomain.one. 3600 IN NS ns2.OLDNS.com
I understand it, the process goes something like this. (PLEASE CORRECT ME IF I AM MISTAKEN)
Step 1. I update the name servers at my registrar (name.com in this case). This should be fairly quick.
Step 2. Name.com sends a request to update the authoritative nameservers for my domain MYDOMAIN.one which are (a.nic.one, b.nic.one, c.nic.one, d.nic.one). This also should be fairly quick.
Step 3. Propagation - Caching DNS servers from around the world query the .one authoritative nameservers for my new namesservers when the TTL expires. This is the step that can take up to 72 hours
Relating this to my problem, it seems step 2 hasn’t completely finished as it’s still serving the old entries as well as the new entries.
I tried reaching out to name.com support but I’ve been told that the new gTLD’s just take longer to propagate.
The plot Thickens!
I have a .cloud domain with a completely different registrar (dreamhost.com) and am experiencing the exact same issue. The two seem unrelated until you look at the authoritative name servers for .cloud (a.nic.cloud, b.nic.cloud, c.nic.cloud, d.nic.cloud). The IPs for the .cloud nameservers and the .one nameservers are similar and both show to be owned by Neustar.
a.nic.CLOUD – 37.209.192.10
a.nic.ONE – 37.209.192.9
Is there an issue with Neustar? How do I peruse this if my domain registrar is telling me I just need to wait?
I was hoping I could get some assistance with an issue I’m having with a few of my GTLD domains. I updated my domain’s nameservers (let’s say MYDOMAIN.ONE) 72 hours ago via the name.com control panel, but my new nameservers haven’t propagated yet.
Not unheard of, but I think I have a bigger issue. The .one authoritative nameservers (a.nic.one, b.nic.one, c.nic.one, d.nic.one) are still serving the old AND the new nameservers when queried directly. Propagation is working as expected, but since authoritative nameservers are still serving the old nameservers at least 50% of the time, non-authoritative dns servers are still caching the old entry thinking it’s valid.
I verified this using DIG against the .one authoritative nameservers (a.nic.one, b.nic.one, c.nic.one, d.nic.one)
$ DIG NS MYDOMAIN.ONE @a.nic.one
;; AUTHORITY SECTION:
mydomain.one. 3600 IN NS ns1.NEWNS.com
mydomain.one. 3600 IN NS ns2.NEWNS.com
Then a few seconds later…same command, different nameservers
$ DIG NS MYDOMAIN.ONE @a.nic.one
;; AUTHORITY SECTION:
mydomain.one. 3600 IN NS ns1.OLDNS.com
mydomain.one. 3600 IN NS ns2.OLDNS.com
I understand it, the process goes something like this. (PLEASE CORRECT ME IF I AM MISTAKEN)
Step 1. I update the name servers at my registrar (name.com in this case). This should be fairly quick.
Step 2. Name.com sends a request to update the authoritative nameservers for my domain MYDOMAIN.one which are (a.nic.one, b.nic.one, c.nic.one, d.nic.one). This also should be fairly quick.
Step 3. Propagation - Caching DNS servers from around the world query the .one authoritative nameservers for my new namesservers when the TTL expires. This is the step that can take up to 72 hours
Relating this to my problem, it seems step 2 hasn’t completely finished as it’s still serving the old entries as well as the new entries.
I tried reaching out to name.com support but I’ve been told that the new gTLD’s just take longer to propagate.
The plot Thickens!
I have a .cloud domain with a completely different registrar (dreamhost.com) and am experiencing the exact same issue. The two seem unrelated until you look at the authoritative name servers for .cloud (a.nic.cloud, b.nic.cloud, c.nic.cloud, d.nic.cloud). The IPs for the .cloud nameservers and the .one nameservers are similar and both show to be owned by Neustar.
a.nic.CLOUD – 37.209.192.10
a.nic.ONE – 37.209.192.9
Is there an issue with Neustar? How do I peruse this if my domain registrar is telling me I just need to wait?
