New on LowEndTalk? Please Register and read our Community Rules.
1.1.1.1, CloudFlare public DNS
Easy enough to remember 
$ host lowendtalk.com 1.1.1.1 Using domain server: Name: 1.1.1.1 Address: 1.1.1.1#53 Aliases: lowendtalk.com has address 104.20.16.33 lowendtalk.com has address 104.20.17.33 lowendtalk.com mail is handled by 10 mail1a.lowendbox.com. lowendtalk.com mail is handled by 20 mail1b.lowendbox.com.
Seems new. Can't find any news article about it, but it works.
LowEndBox & LowEndTalk.
Comments
How about 1.1.2.2 ?
They registered the domain cloudflare-dns.com 2 days ago (It's the reverse of 1.1.1.1), interesting I guess, wonder when they will document it. They have 1.0.0.0/24 and 1.1.1.0/24.
ExtraVM - AMD Ryzen VPS starting @ $3.50
USA (TX, VA, FL), CA, FR, UK, SGP, AU
https://webcache.googleusercontent.com/search?q=cache:https://1.1.1.1/
Seems neat, might use it instead of Google DNS.
Will shill for Pop-Tarts(must be strawberry flavour).
9.9.9.9 ftw
Providing less than /64 means "we are clueless about IPv6". My geekbench results. I haz BuyVM, HostHatch, Online, ServaRica, Veesp.
primary dns: 1.1.1.1
secondary dns: 9.9.9.9
nice.
I’m seeing the secondary dns is 1.0.0.1 - also easy to remember. (From https://webcache.googleusercontent.com/search?q=cache:https://1.1.1.1/)
50 ms ping to Cloudflare, 8 ms ping to Google DNS. Well, that sucks.
It doesn't look like it's all ready yet though. Ex. their v6 doesn't work at all. I'm definitely going to check it again once they make an official announcement.
ExtraVM - AMD Ryzen VPS starting @ $3.50
USA (TX, VA, FL), CA, FR, UK, SGP, AU
The IPv6 adresses are still anounced by Telia and not by Cloudflare, that is probably why there are no news. It is just not ready yet.
I'm having better luck. Across quite few locations, 1.1.1.1 (and 1.0.0.1) seem to be better than 8.8.8.8/8.8.4.4.
14ms vs 44ms or 2ms vs 2.6ms and a whopping 1ms vs ~35ms.
Overall I think because CF has more POPs, latency/pings will be better. Google though seems to have (or be in) bigger DCs rather than more POPs with much more "power" per location.
Interestingly enough though, if you use 8.8.8.8 to resolve google.com and then ping the address that it resolves to, more often than not I get better ping times than I do using the address that 1.1.1.1 resolves google.com for. This I think makes sense since Google is probably more aware about their own servers and so gives you better/closer servers based on your query source.
I hope they address it soon. I'd like to test out IPv6 as well and see how it stacks up.
DNSWatch (based on their no-logging policy) is what I use in some locations but their IPv6 is flaky.
Also, I'm very curious about the interpretation of "We will never log your IP address (the way other companies identify you)." from https://webcache.googleusercontent.com/search?q=cache:https://1.1.1.1/
It is NOT we don't log. Seems to be a "weasely" way of denying logging and I'm a bit suspicious.
Either way, it's great to have another pretty quick and easy to remember public resolver.
the only thing i don't like about dns watch is that they only have servers in germany. otherwise, they'd be about the only organization i'd trust.
OnApp + CDN.net
[email protected]
https://www.google.com/search?q=cloudflare+1.1.1.1
ANY queries result in status: NOTIMP which is an interesting take.
Also, udp: 1536.
Providing less than /64 means "we are clueless about IPv6". My geekbench results. I haz BuyVM, HostHatch, Online, ServaRica, Veesp.
What's the difference between "We will never log" and "we don't log"? Are you an English language linguist? Sorry I'm not, so just asking. The bit in () is just explaining what "logging an IP address" means, to the layman.
edit: Oh and by all means, NEVER BELIEVE a company which says they don't log. Either this one, or any others. Always assume everything is logged in services like this.
I'm not a linguist either but the way they phrased the "We will never..." is troubling to me.
We will never implies that even in the future "We" (Cloudflare in this case) will not log. That's a fairly "powerful" statement. Of course they could change policies and then this becomes useless. On the other hand "we don't log" implies we don't log (right now) but there are no promises about the future. So my take is "we don't log" is weaker (i.e. LESS consumer friendly) than "we will never log" assuming that there is a clear intent to honor what they write.
What is concerning (legalese warning) about the "(the way other companies identify you)" is that they are NOT denying that THEY themselves (i.e. Cloudflare) can identify you somehow. What would have been nicer is to just have a statement something along the lines of dns.watch saying there is no information logged and nothing is personally identifiable etc.
I agree but wish there was a way to "trust" a legal entity making a public statement.
Some sort of a commitment about the specifics of what they log would be more comforting.
where you find it?
0.0.0.0 is the best.
You are dreaming. | And it's a nightmare. | THE SECRET THREAD | THE TRUTH | HA
VES YOU SEEN THIS YURA?„Homo homini rattus.“ | It's not nightmare, it's reality, but it's still nightmare.
Announcement 1st April maybe.
Aha - more about the 4 1's on 4/1.
We have to wait nearly one year for more informations? God damn.
... Sure ;-;
Your last monitoring solution (aff)
No. I presume that the tweet implies it is 1st April (as written in US date format as 4/1). So a couple of days away (Easter Sunday or April Fools).
I think that was a joke, but don't take my words for it...
You are probably right (and I'm a dummy to fall for it as well) but in my defense, I too get confused on the DD/MM vs MM/DD formats quite often.
I like my uptime down low and my servers all hacked. Can see me droppin' twenty-fours with a router in the rack.
Ya like ya Switch-Ports hot and ya servers all hacked. If ya pings real high and ya networks pitch black.
I hope it's legit and not some stupid April fools joke. Because 1.1.1.1 is significantly faster to ping than 8.8.8.8, I'm talking 7-10ms vs. 100ms.
depend on your isp peer with cloudflare
I dislike Cloudflare's campaign against ANY. Would certainly stop me from using their public DNS.
Yes Matthew announced they would be doing public dns on blog post once. I read that in 2017 I believe.
Kinda sad that their IPv6 resolvers are not responding