Cloudflare 1.1.1.1 public DNS broken w/ AT&T CPE

• Subject: Cloudflare 1.1.1.1 public DNS broken w/ AT&T CPE
• From: list at satchell.net (Stephen Satchell)
• Date: Tue, 3 Apr 2018 10:34:14 -0700
• In-reply-to: <[email protected]>
• References: <[email protected]> <[email protected]> <[email protected]> <[email protected]>

On 04/02/2018 11:58 AM, Rhys Williams wrote:
> Yep, Because you should have been setting up your networks correctly in the first place. There's plenty of private space assigned, use it.
> 
> Regards,
> 
> Rhys Williams
> 
> April 2, 2018 4:54 PM, "Simon Lockhart" <simon at slimey.org> wrote:
>> and now suddenly it's our responsibility to make significant changes to live
>> infrastructures just so they can continue to look clever with the IP address.

(ah, the top-posting)

We go by the guidance of our vendors, and in this case the vendors are 
the one who made inappropriate use of Net 1.  Many of them.  So to put 
the onus on just Mr. Lockhart is plainly inappropriate.

"Fixing the blame" is not going to take us very far.  We as a community 
need to "fix the problem" -- that road will lead to proper functioning 
of all of our networks.

Even the little ones.

• References:
  • Cloudflare 1.1.1.1 public DNS broken w/ AT&T CPE
    • From: simon at slimey.org (Simon Lockhart)
  • Cloudflare 1.1.1.1 public DNS broken w/ AT&T CPE
    • From: cma at cmadams.net (Chris Adams)
  • Cloudflare 1.1.1.1 public DNS broken w/ AT&T CPE
    • From: johnl at iecc.com (John Levine)
  • Cloudflare 1.1.1.1 public DNS broken w/ AT&T CPE
    • From: lux+mailinglists at melted.me (Rhys Williams)

• Prev by Date: Cloudflare 1.1.1.1 public DNS different as path info for 1.0.0.1 and 1.1.1.1 london
• Next by Date: Cloudflare 1.1.1.1 public DNS different as path info for 1.0.0.1 and 1.1.1.1 london
• Previous by thread: Cloudflare 1.1.1.1 public DNS broken w/ AT&T CPE
• Next by thread: Cloudflare 1.1.1.1 public DNS broken w/ AT&T CPE
• Index(es):
  • Date
  • Thread