3 ms·
For "easy to remember" my preference is to use Level 3 because I don't (directly) use them for any other service. 4.2.2.1 4.2.2.2 For as often as I manu
by mulmen 9y ago
For "easy to remember" my preference is to use Level 3 because I don't (directly) use them for any other service.
4.2.2.1
4.2.2.2
For as often as I manually configure DNS (I use DHCP) it's not onerous to look up the IPs of whatever DNS is preferable for your purpose.
edit: Depending on who you are this may redirect you to a search portal. Probably best to find an alternate DNS provider.
- duskwuff 9y agoLevel 3's resolvers will return fake NXDOMAIN responses that redirect to searchguide.level3.com.
- michaelmior 9y agoI thought NXDOMAIN responses indicated that the domain doesn't exist and there wasn't a way to actually direct the user anywhere. Your resolver could of course lie and return an IP instead of NXDOMAIN however. Perhaps I'm wrong.
- duskwuff 9y agoThey take the "lie" route: # dig +short this-should-be-a-nxdomain.com @4.2.2.2 198.105.254.11 104.239.213.7 They do it a little more cleanly than some other attempts I've seen, but there's still flaws in their approach. In particular, they will generate redirects for NXDOMAIN responses to certain records under domains that do exist: # dig +short why-does-this-resolve.example.com @4.2.2.2 198.105.254.11 104.239.213.7 Specifically, they'll generate a redirect for any record that starts with the letter "w". (No, I'm not kidding. Try it.) Other records generate a real NXDOMAIN.
- michaelmior 9y agoRight, what I meant is that you can't return an NXDOMAIN response that "redirects" the domain. (Of course this isn't really a redirect per-se.)
- hoschicz 9y agoYou are correct, their resolver is basically lying.
- manacit 9y agoThose resolvers are technically for Level3 customers only - they'll return one of those ad-filled "search" portals where an NXDOMAIN would be proper, see: ; <<>> DiG 9.9.7-P3 <<>> thisprobablydoesntexist.com @4.2.2.2 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12860 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;thisprobablydoesntexist.com. IN A ;; ANSWER SECTION: thisprobablydoesntexist.com. 10 IN A 104.239.213.7 thisprobablydoesntexist.com. 10 IN A 198.105.254.11 Contrast that with 8.8.8.8: ; <<>> DiG 9.9.7-P3 <<>> thisprobablydoesntexist.com @8.8.8.8 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 7991 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 The NXDOMAIN response is proper - the level3 DNS servers are just a faster version of my ISPs goal to garner ad revenue at this point.
- userbinator 9y agoThose resolvers are technically for Level3 customers only There is this comment from a few years ago, https://news.ycombinator.com/item?id=7120248 https://news.ycombinator.com/item?id=7120248 , linking to a blog post which is now only accessible from the Internet Archive, where a VP at Level3 stated they were public. I use 4.2.2.x and I do get NXDOMAIN from them, and I'm not a L3 customer. I wonder if they respond differently depending on who you are...
- mulmen 9y agoI get: ; <<>> DiG 9.9.7-P3 <<>> @4.2.2.1 thisprobablydoesntexist.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10665 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;thisprobablydoesntexist.com. IN A ;; ANSWER SECTION: thisprobablydoesntexist.com. 10 IN A 104.239.213.7 thisprobablydoesntexist.com. 10 IN A 198.105.254.11 ;; Query time: 29 msec ;; SERVER: 4.2.2.1#53(4.2.2.1) ;; WHEN: Fri Mar 30 09:27:39 PDT 2018 ;; MSG SIZE rcvd: 77
- deleted 9y ago[deleted]