Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google DNS at 010.010.010.010

8.8.8.8

Post reply on HN
Print view View original

101–110 of 132 posts

Re: Google DNS at 010.010.010.010

#101

Post by kiwijamo »

jeffbee wrote: post #82
EastOfTruth wrote: post #60

another DNS to avoid... using anything but your ISP's DNS decrease privacy... unless you are using a VPN, then the DNS should be from your VPN's ISP

Some ISPs actually sell DNS responses to the highest-bidding advertiser. ISP DNS is the worst possible choice for all users. https://www.icsi.berkeley.edu/pubs/networking/redirectingdns...

Not all users. ISPs around my part of the world do not behave as badly as US ISPs seem to. Most (although I actually believe it is all) ISPs in my home country do not do anything special to DNS lookups. This means there is literally no benefit to using an off-shore DNS resolver such as those provided by Google, Cloudflare, et al. It just makes DNS lookups slower for us.

Re: Google DNS at 010.010.010.010

#102

Post by [deleted] »

jcims wrote: post #54

This is the first time I've seen a certificate issued to an IP address. Cloudflare does the same thing for 1.1.1.1. X509v3 Subject Alternative Name: DNS:dns.google, DNS:dns.google.com, DNS:*.dns.google.com, DNS:8888.google, DNS:dns64.dns.google, IP Address:8.8.8.8, IP Address:8.8.4.4, IP Address:2001:4860:4860:0:0:0:0:8888, IP Address:2001:4860:4860:0:0:0:0:8844, IP Address:2001:4860:4860:0:0:0:0:6464, IP Address:200…

[deleted]

Re: Google DNS at 010.010.010.010

#103

Post by hda2 »

nobody9999 wrote: post #92
JeremyNT wrote: post #91

Earlier quoted context omitted.

The surveillance is additive (unless you use). Since DNS traffic is not encrypted, the ISP still sees everything even if you switch it, and now so does Google. The practical benefit is that some ISPs run bad DNS servers that e.g. automatically redirect nxdomains to their spam pages. If you use Google or Cloudflare you can bypass this particular anti-feature.

>The practical benefit is that some ISPs run bad DNS servers that e.g. automatically redirect nxdomains to their spam pages. If you use Google or Cloudflare you can bypass this particular anti-feature. As I discussed here[0], my goto DNS server is 192.168.xxx.91. Which is to say I run my own recursive resolver. This avoids ISP DNS server issues as well as other issues (like these[1][2]). Also, Google/Cloudflare/whoev…

Since ISPs generally see DNS queries from the gateway and not individual hosts, wouldn't your ISP still be able to see those requests?

AFAIK, the only way to prevent your ISP from collecting the domains you visit is if you use something like dns over https. Even then, you're tls connection leaks the domain via sni (hopefully this hole will get plugged by tls 1.3).

Re: Google DNS at 010.010.010.010

#104

Post by jalgos_eminator »

When I hover over the link, Chromium shows "https://8.8.8.8". And when I manually typed in "http://010.010.010.010", it converts it to 8.8.8.8. I also tried it with the integer representation of 8.8.8.8 and that converts it immediately as well. It looks like this is just the browser converting it. Am I missing something?

Re: Google DNS at 010.010.010.010

#105

Post by mike_d »

litoE wrote: post #83
linux2647 wrote: post #47

Earlier quoted context omitted.

One has to buy the block of IP addresses, from ARIN or some other Internet governance body, that contains the IP you’re looking for

Once you own outright a block of IP4 addresses, is there a recurring charge to allow you to keep it? And who, if anyone, gets paid.

Only 8 organizations actually "own" IP addresses (AT&T, Apple, Ford, Cogent, Prudential Insurance, USPS, Comcast, US DoD).

Almost all of IPv4 is allocated by IANA to Regional Internet Registries that in turn allocate them to customers like Google and Verizon. You pay yearly maintenance fees to keep the addresses assigned to you.

Re: Google DNS at 010.010.010.010

#107

Post by scbrg »

dharmab wrote: post #42
lucb1e wrote: post #22

Earlier quoted context omitted.

It can't only be that, or 127.1 would not work. It is doing some parsing beyond just calling a parseInt on each of them in order to recognize domain names and use name resolution rather than directly putting the bytes in the IP header. That must be why 0x9000000.-16250872 doesn't work (if negative worked, that should also resolve to 8.8.8.8).

I looked into this a while back, IIRC BSD added the "omit zeroes" as a nonstandard convenience feature and other OSes copied it. I'm far afk for I'd find my notes on this.

It's not "omit zeroes". It's, "represent the last three octets with just one integer".

127.256 is valid, and would be equivalent to 127.0.1.0. The last integer can be up to 16777215 (2²⁴-1).

Similarly, if you instead include three groups of integers, the first two represents one octet each, and the last represents two. 127.2.256 is equivalent to 127.2.1.0.

Re: Google DNS at 010.010.010.010

#108

Post by SturgeonsLaw »

xanathar wrote: post #46
shireboy wrote: post #43

Out of sheer curiosity, how does one go about reserving an IP address like this, or the ones CloudFlare and google dns use?

The main prerequisite is "having a bloatload of money".

> bloatload

Sounds like a good unit of measurement for Javascript

Re: Google DNS at 010.010.010.010

#109

Post by RKearney »

vmoore wrote: post #25

For those interested in more memorable DNS IPs, there is the following: Just be careful, because TWNIC/Quad101 was subjected to a BGP hijack in 2019[0] 101.101.101.101 [TWNIC] 80.80.80.80 [FREENOM][1] 4.2.2.2 [Level 3] [0] https://www.manrs.org/2019/05/public-dns-in-taiwan-the-lates... [1] https://www.freenom.world/en/index.html?lang=en

4.2.2.2 is only for Level 3 customers (now Lumen). You will get mixed results and I believe they have hijacked NXDOMAIN responses for non-customers in the past.

Re: Google DNS at 010.010.010.010

#110

Post by broodbucket »

jalgos_eminator wrote: post #104

When I hover over the link, Chromium shows " https://8.8.8.8 ". And when I manually typed in " http://010.010.010.010 ", it converts it to 8.8.8.8. I also tried it with the integer representation of 8.8.8.8 and that converts it immediately as well. It looks like this is just the browser converting it. Am I missing something?

No, I think the post is basically "here's a reminder octal exists"
Post reply on HN