[Discuss] Not Able to Access Fedoraforum Within Home Comcast Network

[jbk at kjkelra.com (jbk)]

On 12/5/19 8:00 AM, jbk wrote:
> On 12/4/19 8:47 PM, jbk wrote:
>> On 12/4/19 7:56 PM, Dan Ritter wrote:
>>> Dan Ritter wrote:
>>>> jbk wrote:
>>>>> On 12/4/19 5:15 AM, Steven Santos wrote:
>>>>>> try a different dns.
>>>>>>
>>>>>> It was unreachable with the comcast dns.
>>>>>>
>>>>>> Works fine with 8.8.8.8 and opendns
>>>>> Changing dns server has not succeeded yet. How long 
>>>>> should I expect to wait
>>>>> before new server provides results?
>>>> 60 seconds, max.
>>> 207.210.201.125 is the IP I resolved.
>>>
>>> It appears to be a cPanel controlled virtual server, 
>>> owned by
>>> Endurance, which, interestingly, has offices in 
>>> Burlington and
>>> Waltham. Oh -- they're the corporate parent of Constant 
>>> Contact,
>>> Hostgator, Sitebuilder, and a bunch of others.
>>>
>>> The connectivity is via Cogent, and that might or might 
>>> not be
>>> the issue: Cogent has a history of getting into spats 
>>> with other
>>> major ISPs; it wouldn't be too surprising if there was a 
>>> game of
>>> one-upsmanship going on between Comcast and Cogent. But 
>>> I don't
>>> know, I'm just speculating.
>>>
>>> -dsr-
>>>
>> That ip agrees with what I found. The thing is I can 
>> access Fedoraforum at work through a comcast modem with 
>> no trouble. I've tried the google dns and opendns without 
>> success so far.
>>
>> Is there any possibility that my dd-wrt router could be 
>> blocking a single address w/o me actively blocking a 
>> particular site? Since I'm bridged that is the direction 
>> the finger is going to point when comcasts tech comes so 
>> I'd really like to nip that in the bud.
>>
> I ran traceroute this AM my dns is pointing to opendns
>
>
> traceroute to fedoraforum.org (207.210.201.125), 30 hops 
> max, 60 byte packets
> ?1? bagshot (10.251.227.1)? 1.351 ms? 1.355 ms? 1.804 ms
> ?2? 96.120.64.65 (96.120.64.65)? 18.290 ms? 19.116 ms? 
> 20.290 ms
> ?3? 68.87.181.193 (68.87.181.193)? 19.296 ms? 20.987 ms? 
> 20.961 ms
> ?4? 96.108.157.94 (96.108.157.94)? 21.663 ms? 21.638 ms? 
> 22.022 ms
> ?5? be-98-ar01.needham.ma.boston.comcast.net 
> (68.85.106.13) 23.213 ms? 27.160 ms? 27.136 ms
>
I brought my laptop to the office today and connected 
through their network to fedoraforum without any delay. They 
provide a dns server in house. I then did a traceroute from 
here and the first five hops are slightly different, first 
being it skips the gateway hop.

traceroute to fedoraforum.org (207.210.201.125), 30 hops 
max, 60 byte packets
 ?1? 96.120.66.205 (96.120.66.205)? 14.347 ms? 14.891 ms? 
15.322 ms
 ?2? 162.151.168.1 (162.151.168.1)? 12.913 ms? 13.392 ms? 
19.308 ms
 ?3? 162.151.151.170 (162.151.151.170)? 17.457 ms? 19.447 ms 
19.413 ms
 ?4? be-345-ar01.needham.ma.boston.comcast.net 
(96.108.70.33) 22.050 ms? 21.154 ms? 22.246 ms
 ?5? be-1003-pe02.onesummer.ma.ibone.comcast.net 
(68.86.90.173) 19.369 ms? 20.121 ms? 19.679 ms
 ?6? as174.onesummer.ma.ibone.comcast.net (50.242.149.54)? 
27.633 ms? 20.582 ms? 27.641 ms

after hop six everything is the same except the time. Line 4 
uses a different comcast server, but everything seems to go 
through the same domains.


-- 
Jim Kelly-Rand
jbk at kjkelra.com