[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[public-dns-discuss] Re: Can't resolve vultr.com on 8.8.8.8 from Asia



When you are able to resolve a domain in one region of the world, but not another, the problems are often due to connectivity issues.

https://zonalizer.makeinstall.se/?knvbBywLQdCflUWk3ONwAQ reports that all the name servers for vultr.com are in a single AS, and it is possible that Google's connectivity to that network was lost in parts of Asia.

DNS zones should have at least two different nameservers running in each of at least two different Autonomous System (AS) routing zones (https://tools.ietf.org/html/rfc1537#section-6).

You may want to consider adding secondary DNS service from other providers, e.g. https://www.keycdn.com/blog/best-free-dns-hosting-providers/ — dns.he.net offers very good coverage, and is free: you would need to enter the he.net nameserver IP (216.218.130.2) to the AXFR allowed whitelist of your primary nameserver, and then add the he.net nameservers and/or replace some of the duplicate nameservers on your single subnet with he.net nameservers in your domain registration.

That Zonalizer report also shows that the .COM TLD lists these name servers and IP addresses:

;; AUTHORITY SECTION:
vultr.com. 172800 IN NS ns1.vultr.com.
vultr.com. 172800 IN NS ns2.vultr.com.

;; ADDITIONAL SECTION:
ns1.vultr.com. 172800 IN A 173.199.96.96
ns1.vultr.com. 172800 IN AAAA 2001:19f0:ccd::1
ns2.vultr.com. 172800 IN A 173.199.96.97
ns2.vultr.com. 172800 IN AAAA 2001:19f0:ccd::2

while the NS records at the vultr.com name servers show a different set of name servers and IP addresses.

ns1.choopadns.com     17 A    68.232.191.191
ns1.choopadns.com    599 AAAA 2001:19f0:ccc::1
ns2.choopadns.com     44 A    68.232.191.232 [AS20473]
ns2.choopadns.com    599 AAAA 2001:19f0:ccc::2

Google Public DNS will only use the name server names listed in the .COM TLD registry, for best results generally, you should configure the delegation records in the TLD to match the names in the zone itself, making sure that all listed name servers are able to respond successfully to queries for the zone.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dns-discuss AT googlegroups.com
To unsubscribe from this group, send email to
public-dns-discuss+unsubscribe AT googlegroups.com
For more options, visit this group at
http://groups.google.com/group/public-dns-discuss
For more information on Google Public DNS, please visit
http://developers.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsubscribe AT googlegroups.com.
For more options, visit https://groups.google.com/d/optout.