[vcf-midatlantic] Comcast

[Madeline Autumn-Rose]

I worked for an ISP that for a significant time was announcing 1.1.1.1 publicly into TorIX...

Sent from my iPhone

> On Apr 5, 2018, at 18:56, David Riley via vcf-midatlantic <vcf-midatlantic at lists.vintagecomputerfederation.org> wrote:
> 
>> On Apr 5, 2018, at 9:50 PM, Dave McGuire via vcf-midatlantic <vcf-midatlantic at lists.vintagecomputerfederation.org> wrote:
>> 
>> 
>> Routing has absolutely nothing to do with DNS.
> 
> Unless you're using Cloudflare's new 1.1.1.1 service, whereupon you learn just how broken some routers are when they treat 1.1.1.1 as an internal resource, even though it's a non-reserved number or network. :-)
> 
> But that's not what we're talking about here. Unless for some reason Ian's server is resolving to a different address on Comcast (it's not; they're all showing 203.0.178.90), DNS isn't the problem here.  I've had routing breakages somewhere a few hops downstream of me on Comcast and Verizon in the past; sometimes a router just dies in a datacenter somewhere and it takes a while for BGP to catch up.
> 
> 
> - Dave
>