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

81–90 of 132 posts

Re: Google DNS at 010.010.010.010

#81

Post by jeffbee »

JonathanMerklin wrote: post #59
mongol wrote: post #56

Why is Google providing a public DNS? Is it a PR thing?

Do you perhaps think that DNS log data could be valuable for Google? As always, when a product is free...

DNS log data is not used by Google for any purpose. Their privacy policy is actually stronger than Cloudflare's for DNS services.

The reason Google provides DNS should be obvious: when people experience a better web, Google makes more money. ISP DNS fuckery is bad for users. Since Google already needs to cache the DNS for its internal purposes, presenting it to the public as a service is close to free for them.

Re: Google DNS at 010.010.010.010

#82

Post by jeffbee »

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...

Re: Google DNS at 010.010.010.010

#83

Post by litoE »

linux2647 wrote: post #47
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?

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.

Re: Google DNS at 010.010.010.010

#84

Post by mgbmtl »

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

On IPv6, I like using 2600::1.

Short and easy to remember thanks to the classic 2600 zine (named after the Captain Crunch cereal whistle which emitted the 2600hz tone for payphones). I wonder if someone at Sprint is a fan.

Re: Google DNS at 010.010.010.010

#85

Post by EastOfTruth »

chriscjcj wrote: post #79
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

Comcast is my ISP. Would it be your assertion that if I used their DNS's, that my privacy would _increase_?

It would not increase unless you are switching away from a third party DNS. Whether you use Comcast's DNS or not, they know the sites that you visit... If you use Google as your DNS, then Google also knows.

Re: Google DNS at 010.010.010.010

#86

Post by EastOfTruth »

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...

They still know where you go ... where do you think your traffic go through?

Re: Google DNS at 010.010.010.010

#87

Post by EastOfTruth »

sodality2 wrote: post #68
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

> using anything but your ISP's DNS decrease privacy Using your ISP's DNS decreases privacy. I assume you mean that because UDP/53 DNS is unencrypted, if you switch to another DNS provider, then both the ISP and the new DNS can see your requests? In which case I present to you DNS over HTTPS

How can your ISP route the traffic if according to you it doesn't know where it goes? You need a VPN if you want to hide your traffic destinations from your ISP... not encrypted DNS

Re: Google DNS at 010.010.010.010

#88

Post by floatingatoll »

lucb1e wrote: post #14

It's also at 010.010.2056 or 0x8080808 or 01002004010. I made a little tool a while ago that iterates over all the options that I know of: https://lucb1e.com/randomprojects/php/funnip.php?ip=8.8.8.8 The variant found by OP is apparently the very last option that my tool generates. These days, Firefox is a bit boring (okay, okay, I'll admit it's a good choice for security) and translates these at the first opportunity…

Octal is a great way to mislead both human beings and software, and I kind of hope it gets removed by browsers as a result of this new attention. It’s one of those things that isn’t productive or useful in any way in our modern era and serves only to complicate with no benefit in return.

Re: Google DNS at 010.010.010.010

#89

Post by chmod775 »

keymone wrote: post #75
pbiggar wrote: post #36

Earlier quoted context omitted.

If you provide the GET parameter "source" (which means you try /the-url?source"), it prints a pretty-printed version of the source code. So basically it allows the reader to read the source directly without hunting it down on github of something.

Doesn’t this just highlight that php development ecosystem doesn’t value quality much? What even is a “file” in context of a web request? What about dependencies or logic defined in other files? This is just bizarre, I can’t see a sane codebase where this would be preferable to going on GitHub and pressing “.”

> Doesn’t this just highlight that php development ecosystem doesn’t value quality much?

As opposed to which web development ecosystem exactly? The only web development ecosystem with overall decent quality software that I could come up with is Java, and their understanding of quality is... enterprise-y.

Give me a mature PHP framework over a NPM dependency tree, python web framework, or ruby on rails any day. At least when looking for 'quality'. Relatively.

Re: Google DNS at 010.010.010.010

#90

Post by sodality2 »

EastOfTruth wrote: post #87
sodality2 wrote: post #68

Earlier quoted context omitted.

> using anything but your ISP's DNS decrease privacy Using your ISP's DNS decreases privacy. I assume you mean that because UDP/53 DNS is unencrypted, if you switch to another DNS provider, then both the ISP and the new DNS can see your requests? In which case I present to you DNS over HTTPS

How can your ISP route the traffic if according to you it doesn't know where it goes? You need a VPN if you want to hide your traffic destinations from your ISP... not encrypted DNS

The DNS lookup would be encrypted. The IP would of course not be. This means the ISP would be able to see the IP but not domain [1] of your destination.

[1]: See SNI: https://www.cloudflare.com/learning/ssl/what-is-sni/

Post reply on HN