News for hackers. Stuff that matters.
Re:1.1.1.1: Fast, privacy-first consumer DNS service by nodesocket on Sunday April 01, 2018 @03:33PM (#16729994)
AT&T Fiber Gigabit in Nashville TN.

    iMac   ~ ping 1.1.1.1
    PING 1.1.1.1 (1.1.1.1): 56 data bytes
    64 bytes from 1.1.1.1: icmp_seq=0 ttl=64 time=0.688 ms
    64 bytes from 1.1.1.1: icmp_seq=1 ttl=64 time=0.814 ms
    64 bytes from 1.1.1.1: icmp_seq=2 ttl=64 time=1.153 ms
    64 bytes from 1.1.1.1: icmp_seq=3 ttl=64 time=0.752 ms
    64 bytes from 1.1.1.1: icmp_seq=4 ttl=64 time=0.755 ms
    64 bytes from 1.1.1.1: icmp_seq=5 ttl=64 time=0.789 ms
    64 bytes from 1.1.1.1: icmp_seq=6 ttl=64 time=0.876 ms
    64 bytes from 1.1.1.1: icmp_seq=7 ttl=64 time=0.869 ms
    64 bytes from 1.1.1.1: icmp_seq=8 ttl=64 time=0.830 ms
    64 bytes from 1.1.1.1: icmp_seq=9 ttl=64 time=1.387 ms
    --- 1.1.1.1 ping statistics ---
    10 packets transmitted, 10 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 0.688/0.891/1.387/0.204 ms
Pinging 8.8.8.8 averages 8ms. CloudFlare must have a POP here in Nashville?
Re:1.1.1.1: Fast, privacy-first consumer DNS service by dragonwriter on Monday April 02, 2018 @12:09PM (#16735821)
That's probably because AT&T is using 1.1.1.1 for something internal and breaking the public internet for it's users: you get a really fast ping on 1.1.1.1, but it's not the 1.1.1.1 you are trying to reach.
Re:1.1.1.1: Fast, privacy-first consumer DNS service by nodesocket on Monday April 02, 2018 @02:12PM (#16737376)
Is this just speculation or can anybody confirm?

    traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 52 byte packets
     1  1dot1dot1dot1.cloudflare-dns.com (1.1.1.1)  1.117 ms  0.710 ms  0.727 ms
Re:1.1.1.1: Fast, privacy-first consumer DNS service by _nickwhite on Friday April 06, 2018 @06:10AM (#16772158)
Seems AT&T uses 1.1.1.1 inside of their modems. Oops!

Using 1.0.0.1 works.

Re:1.1.1.1: Fast, privacy-first consumer DNS service by chrissnell on Sunday April 01, 2018 @04:42PM (#16730334)
Given that they're a CDN, I would expect them to. I'm jealous that BNA has AT&T peering but Kansas City has minimal/no peering.
Re:1.1.1.1: Fast, privacy-first consumer DNS service by mxpxrocks10 on Sunday April 01, 2018 @11:00PM (#16731984)
haha, I knew that was you when I read Nashville, nodesocket