1
Do DNS record changes take longer to propagate to NextDNS DNS over HTTPS (DoH) servers vs. legacy DNS protocol servers?
I made DNS record changes for a domain I own, and all records—NS, A, SOA, etc.—have propagated through standard DNS servers after approximately 36 hours, including my two NextDNS profiles, tested via:
dig @<my_NextDNS_IP> <my_domain> NS
dig @<my_NextDNS_IP> <my_domain> SOA
dig @<my_NextDNS_IP> <my_domain> A
HOWEVER, checking the same records via NextDNS DoH showed the old values many hours after legacy DNS had updated. The SOA record is still showing the old value, tested via:
curl -H 'accept: application/dns-json' 'https://dns.nextdns.io/<my_NextDNS_profile_id>?name=<my_domain>&type=SOA' | jq
My questions:
- Is there extra propagation lag for NextDNS DoH vs legacy DNS?
- If so, how long is that lag? How can I report an issue for a specific domain record if it goes beyond that?
2 replies
-
I have exactly the same question. How can the propagation be made faster
-
Same here. My website only opens with the legacy DNS
Content aside
-
1
Likes
- 3 mths agoLast active
- 2Replies
- 167Views
-
3
Following