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

[jbk]

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
  6  be-1003-pe02.onesummer.ma.ibone.comcast.net 
(68.86.90.173) 25.230 ms  24.667 ms  23.913 ms
  7  as174.onesummer.ma.ibone.comcast.net (50.242.149.54)  
26.246 ms  13.853 ms  16.856 ms
  8  be3600.ccr22.alb02.atlas.cogentco.com (154.54.0.221)  
20.005 ms  18.970 ms  23.706 ms
  9  be2879.ccr22.cle04.atlas.cogentco.com (154.54.29.173)  
30.878 ms  34.674 ms  35.542 ms
10  be2718.ccr42.ord01.atlas.cogentco.com (154.54.7.129)  
41.697 ms  42.995 ms  42.352 ms
11  be2832.ccr22.mci01.atlas.cogentco.com (154.54.44.169)  
58.312 ms  58.747 ms  57.608 ms
12  be2433.ccr32.dfw01.atlas.cogentco.com (154.54.3.213)  
106.073 ms  105.104 ms  108.844 ms
13  be2561.rcr21.b010621-0.dfw01.atlas.cogentco.com 
(154.54.6.74) 98.955 ms  95.923 ms  95.734 ms
14  38.32.13.210 (38.32.13.210)  96.656 ms  100.994 ms  
100.297 ms
15  * * *

This without any options to the trace. I'm thinking of 
asking comcast to change my modem ip. I've had the same one 
for over a year.

-- 
Jim Kelly-Rand
jbk at kjkelra.com