mcguire at neurotica.com
Thu Apr 5 21:57:39 EDT 2018
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 126.96.36.199 service, whereupon you learn just how broken some routers are when they treat 188.8.131.52 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 184.108.40.206), 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 McGuire, AK4HZ
New Kensington, PA
More information about the vcf-midatlantic