[vcf-midatlantic] Comcast

[Mike Loewen]

On Thu, 5 Apr 2018, Dave McGuire via vcf-midatlantic wrote:

> On 04/05/2018 09:56 PM, David Riley 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. :-)
>
>  soda -> keyboard 
>
>> 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.
>
>  Yup.
>
>          -Dave

    I just spent 40 minutes chatting online with a trained monkey at Comcast. 
He persisted in blaming my computer for the problem, despite my providing the 
traceroute listing.  I finally got tired of it when he wanted my to connect my 
computer directly to the modem, and suggested he forward my message to someone 
who understands how traceroute works, as a ROUTING issue.

    I just posted a note in their support forum.


Mike Loewen				mloewen at cpumagic.scol.pa.us
Old Technology				http://q7.neurotica.com/Oldtech/