[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Cloudflare 22.214.171.124 public DNS broken w/ AT&T CPE
That sounds like a provider problem with their configuration most likely. I run hundreds of 844E, 844Gs and have one at my house even, and it continues out fine for 126.96.36.199 when I was testing over the weekend with our config.
IP Services Supervisor
From: NANOG <nanog-bounces at nanog.org> On Behalf Of Darin Steffl
Sent: Monday, April 02, 2018 11:03 AM
To: North American Network Operators' Group <nanog at nanog.org>
Subject: Re: Cloudflare 188.8.131.52 public DNS broken w/ AT&T CPE
I am behind a Calix router at home for my ISP and 184.108.40.206 goes to my router and not any further. When I enter the IP into my browser, it opens the login page for my router. So it appears 220.127.116.11 is used as a loopback in my Calix router.
18.104.22.168 goes to the proper place fine.
On Sun, Apr 1, 2018 at 3:59 PM, Jeremy L. Gaddis <lists-nanog at gadd.is>
> If anyone at 7018 wants to pass a message along to the correct folks,
> please let them know that Cloudflare's new public DNS service
> (22.214.171.124) is completely unusable for at least some of AT&T's customers.
> There is apparently a bug with some CPE (including the 5268AC). From
> behind such CPE, the services at 126.96.36.199 are completely unreachable,
> whether via (ICMP) ping, DNS, or HTTPS.
> Using the 5268AC's web-based diagnostic tools, pinging 188.8.131.52 returns
> the following results:
> ping successful: icmp seq:0, time=2.364 ms
> ping successful: icmp seq:1, time=1.085 ms
> ping successful: icmp seq:2, time=1.160 ms
> ping successful: icmp seq:3, time=1.245 ms
> ping successful: icmp seq:4, time=0.739 ms
> RTTs to the CPE's default gateway are, at minimum, ~20 ms.
> A traceroute (using the same web-based diagnostic tool built-in to the
> CPE) reports, simply:
> traceroute 184.108.40.206 with: 64 bytes of data
> 1: 220.127.116.11(1dot1dot1dot1.cloudflare-dns.com), time=0 ms
> I haven't bothered to report this to AT&T through the standard
> customer support channels (for reasons that should be obvious to
> anyone who has ever called AT&T's consumer/residential technical
> support) but if anyone at AT&T wants to pass the info along to the
> appropriate group, it would certainly be appreciated.
> Jeremy L. Gaddis
> "The total budget at all receivers for solving senders' problems is
> $0. If you want them to accept your mail and manage it the way you
> want, send it the way the spec says to." --John Levine
<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.facebook.com%2Fminnesotawifi&data=02%7C01%7C%7C44b0d324ba284c19f9b108d598ab2d27%7C453303889ca9424bbe1a29721272041d%7C1%7C0%7C636582783328080128&sdata=W4P%2BUzI82FABcW8sAkxaGNM2FJmVLmrix58KVgdxax0%3D&reserved=0> Like us on Facebook <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.facebook.com%2Fminnesotawifi&data=02%7C01%7C%7C44b0d324ba284c19f9b108d598ab2d27%7C453303889ca9424bbe1a29721272041d%7C1%7C0%7C636582783328080128&sdata=W4P%2BUzI82FABcW8sAkxaGNM2FJmVLmrix58KVgdxax0%3D&reserved=0>