5 ms·
EDIT: fixed DNS IP. Technically, there may be an advantage to using a 'closer' DNS server with 'less hops', but many national ISPs don't push DNS servers to al
by justizin 12y ago
EDIT: fixed DNS IP.
Technically, there may be an advantage to using a 'closer' DNS server with 'less hops', but many national ISPs don't push DNS servers to all POPs. DNS infrastructure at large ISPs tends to be heavily loaded and is scaled based on demand.
It's common, and many wifi routers do this for you by default, to run a local caching nameserver which uses some other ISP nameservers as 'forwarders'. You create less demand upstream as well as getting faster response if you do this.
Obviously you should also be concerned about creating load on DNS services provided by someone you have no relationship with. Some might even consider it rude.
In addition to OpenDNS, Google runs free DNS servers at 8.8.8.8 and 8.8.4.4, but obviously there are concerns with relying upon Google to provide all of the internet's infrastructure.
What we should really all be talking about is decentralized, peer-to-peer DNS, or a system of forwarders we all provide from places like Linode and DigitalOcean, both of which I've used to provide off-site secondary and tertiary DNS for large networks. We should be looking at NameCoin, not just leeching off some other random ISP.
- mclarke 12y ago8.8.4.4 should be the second google ip address.
- justizin 12y agothanks, fixed.
- scott_karana 12y agoPersonally, I find it obnoxious that OpenDNS hijacks nonresolving domains and uses them as "search pages", but to each their own. Nothing is worse than trying to SSH into a server with a domain typo, and thinking it exists...
- rhubarbquid 12y agoDidn't they just announce they were going to stop doing that?
- kbar13 12y agoyes, starting june 6th. http://blog.opendns.com/2014/05/29/no-more-ads/ http://blog.opendns.com/2014/05/29/no-more-ads/
- rakoo 12y ago> We should be looking at NameCoin Take a look at dnschain [0], which allows you to query Namecoin domains using standard DNS or HTTP: $ dig @dns.dnschain.net otokar.bit [....] ;; ANSWER SECTION: otokar.bit. 527 IN A 109.190.29.155 [...] [0] https://github.com/okTurtles/dnschain https://github.com/okTurtles/dnschain