Networking → 1.1.1.1

I haven't seen a topic on this, anyone using the new 1.1.1.1 name servers? They seem extra snappy, especially in the latest Safari.

Yes, I switched over from 8.8.8.8 and it is a little faster. Time will tell when more start using it if it will slow down.

I'm on At&t fiber. (Bay Area, California); seem 1.1.1.1 are blocked or gateway somewhere in ISP using it too.
I tracerouted 1.1.1.1 and it's request timeout after 8th hop. But 1.1 worked tho.

1.1.1.1

; <<>> DiG 9.9.4-RedHat-9.9.4-51.el7_4.2 <<>> dslreports.com @1.1.1.1
;; global options: +cmd
;; connection timed out; no servers could be reached
 

1.0.0.1

; <<>> DiG 9.9.4-RedHat-9.9.4-51.el7_4.2 <<>> dslreports.com @1.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7015
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
 
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1536
;; QUESTION SECTION:
;dslreports.com.                        IN      A
 
;; ANSWER SECTION:
dslreports.com.         2415    IN      A       64.91.255.98
 
;; Query time: 7 msec
;; SERVER: 1.0.0.1#53(1.0.0.1)
;; WHEN: Sun Apr 01 19:57:06 PDT 2018
;; MSG SIZE  rcvd: 59
 

1.1

; <<>> DiG 9.9.4-RedHat-9.9.4-51.el7_4.2 <<>> dslreports.com @1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58420
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
 
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1536
;; QUESTION SECTION:
;dslreports.com.                        IN      A
 
;; ANSWER SECTION:
dslreports.com.         2258    IN      A       64.91.255.98
 
;; Query time: 7 msec
;; SERVER: 1.0.0.1#53(1.0.0.1)
;; WHEN: Sun Apr 01 19:59:43 PDT 2018
;; MSG SIZE  rcvd: 59
 

 
I saw mention on a mailing list that 1.1.1.1 has been used so frequently (and incorrectly) in documentation that some "providers" may block it.

YMMV, and all that.

 

If you have the desire to traverse the thread... have at it...

»mailman.nanog.org/piperm ··· 665.html

You might have to update your Safari browser to get the extra snap. But so far it seems to be working well I switched from OpenDNS

Here is there blog: »blog.cloudflare.com/dns- ··· 1-1-1-1/

The IPv6 address is 2606:4700:4700::1111

I haven't tried it yet as google's public DNS is working fine for me and I have no compelling reason to switch at the moment.

See topic, »AT&T gateway (5268ac, maybe others) misrouting 1.1.1.0/24?

I'm using them via DNS over TLS.

I have my pfsense routers running Stunnel and Bind.

Bind's Forwarder settings are pointed at 4 Stunnel Loopback IP/Port Combos, Bind is Set for TCP only, that TCP DNS request is encapsulated in TLS and sent to 2606:4700:4700::1111, 2606:4700:4700::1001, 1.1.1.1 or 1.0.0.1.

After this post, realized/decided I should do IPv6 with IPv4 fall back, updated accordingly.

and 2606:4700:4700::1001

APNIC's post about it, they claim it's a research project: »blog.apnic.net/2018/04/0 ··· udflare/
(they're the ones who own those addresses)

Good find.

Always interesting to see how /8s are allocated.
»www.iana.org/assignments ··· ce.xhtml

I'm not using it but I did check and the address is accessible.

/tom

Folks might be interested to know that both DNS-over-TLS and DNS-over-HTTPS are supported at launch.

You can read developer information here. »developers.cloudflare.co ··· 1.1.1.1/

Thanks for the info... may have to add these guys to my NMS, just from a benchmarking perspective.

Regards

Ya I suspect many will have trouble with this as so many wrongly use that address.

Well using my Ripe Probe credits I've setup a monitor on 1.1.1.1, so I'll see how many come back with unreachable.

 

Cloudflare touts privacy-friendly 1.1.1.1 public DNS service. Hmm, let's take a closer look at that
»www.theregister.co.uk/20 ··· privacy/

---

...Ironically for a project predicated on privacy, Cloudflare is sharing DNS query data with APNIC Labs, a part of Asian registry APNIC, in exchange for the use of its 1.1.1.1 network address. The regional internet registry insists it wants to better understand the technical intricacies of DNS, in order to mitigate denial-of-service attacks and to optimize server communication.

The research relationship is set to run for at least five years, after which it may be renewed and APNIC will consider permanently allocating the 1.1.1.1 IP address – along with 1.0.0.1 – to Cloudflare.....

---

Oh great bringing Russia into it.

Well presuming I have the test set right I'll be hitting them with queries for www.google.com from 10 different probes.

The setup page on 1.1.1.1 did not say how to configure a Verizon FiOS router. This worked for me: From the main page, select "Broadband Connection". Then "Fiber Broadband Connection (Coax)". The DNS servers appear on the page, select "Settings" to change from Verizon's DNS to 1.1.1.1 and 1.0.0.1. Side note - I though Secondary DNS was like a "failover" DNS, in case the Primary DNS was busy. Apparently, the Primary and Secondary are shared around 50% each.

In related news
»www.theregister.co.uk/20 ··· worries/

let the hoovering begin

 

... and China. ...

DarkLogix ;
Want to add another probe to the list? PM me for probe # details.

»archive.apnic.net/news-a ··· ocation/

Or um Australia?

I just told it 10 as I think I have enough credits to cover that many.

If I connect my 2nd probe and double my earning rate I could up the number of probes.

If you need some more credits, I've got about 36M to spare...

Well since I plan to keep the test running indefinitely I only want to scale the test to the income credits I get so it doesn't stop due to running out.
Thanks for the offer.

what the heck you guys talking about?

 
RIPE Atlas probe
»[Other] Ripe Atlas Probe..

Main site:
»atlas.ripe.net/

Ok, odd I think of Ripe as Europe and APnic as Asia/Pacific
I guess Russia does have some Europe sections.

So it's China, Australia, and India.