• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

comcast blocking DNS?

R

roberttran

[H]ard|Gawd
Joined
Aug 15, 2002
Messages
1,471
Hey,
I've been on cable modem for awhile now. I have a domain name registered and use my registrar's DNS servers to resolve the domain to my comcast IP. Today my domain name all of a sudden stopped working inside my network. I can't ping to it or anything. I tried the nslookup to see if there was a record for my domain and it wasn't there. I had some friends who are not using comcast try my domain name and it resolves properly to my IP. I haven't found anyone else who also uses comcast to check. I tried to use another DNS server with my comcast connection but I couldn't get out.
Is comcast doing this on purpose to prevent people from running servers? Or is this just something else?

Thanks
Robert
 
Anyone get the answer to this?

I have names hosted by Network solutions and it appears that some of the country can access my site via their NS99 and NS100 DNS servers. But other areas cannot and get weird tracerts:

Tracing route to 216.158.228.52 over a maximum of 30 hops

1 49 ms 51 ms 49 ms X.X.151.236
2 56 ms 71 ms 51 ms X.X.151.193
3 66 ms 66 ms 66 ms sl-gw27-stk-4-1-TS24.sprintlink.net X.X.56.
105]
4 66 ms 68 ms 67 ms sl-bb21-stk-9-0.sprintlink.net [144.232.4.245]
5 69 ms 71 ms 72 ms sl-bb24-sj-9-0.sprintlink.net [144.232.20.181]
6 70 ms 70 ms 76 ms sl-bb21-sj-12-0.sprintlink.net [144.232.3.201]
7 69 ms 68 ms 70 ms sl-st21-sj-13-0.sprintlink.net [144.232.20.59]
8 69 ms 69 ms 69 ms 144.232.19.22
9 70 ms 70 ms 70 ms p64-0-0-0.r20.mlpsca01.us.bb.verio.net [129.250.
5.2]
10 79 ms 80 ms 80 ms p16-2-0-0.r21.lsanca01.us.bb.verio.net [129.250.
5.121]
11 84 ms 79 ms 80 ms ge-1-1.a00.lsanca17.us.ra.verio.net [129.250.29.
132]
12 81 ms 78 ms 79 ms fa-4-1.a00.lsanca17.us.ce.verio.net [204.1.254.1
62]
13 79 ms 79 ms 81 ms 216.158.230.130
14 80 ms 79 ms 80 ms 216.158.230.129
15 79 ms 81 ms 79 ms 216.158.230.130
16 79 ms 79 ms 80 ms 216.158.230.129
17 81 ms 94 ms 82 ms 216.158.230.130
18 80 ms 79 ms 79 ms 216.158.230.129
19 83 ms 79 ms 114 ms 216.158.230.130
20 80 ms 79 ms 82 ms 216.158.230.129
21 80 ms 81 ms 82 ms 216.158.230.130
22 80 ms 81 ms 80 ms 216.158.230.129
23 80 ms 80 ms 81 ms 216.158.230.130
24 80 ms 80 ms 79 ms 216.158.230.129
25 80 ms 80 ms 85 ms 216.158.230.130
26 95 ms 83 ms 81 ms 216.158.230.129
27 81 ms 84 ms 81 ms 216.158.230.130
28 96 ms 85 ms 80 ms 216.158.230.129
29 91 ms 80 ms 82 ms 216.158.230.130
30 81 ms 80 ms 81 ms 216.158.230.129

Obviously something funky is going on.
 
Loneregister said:
Obviously something funky is going on.
Click to expand...

Yeah, looks like there's definately a routing loop there. Nothing that u'll be able to do to fix that really.

As for comcast and DNS servers, I run multiple domains at home on my comcast connection, including BIND for DNS and it works fine. I've had zero probs. Just RD'd into a server at work to test again and I was able to point nslookup at my server and get responses to queries.

I'm half asleep and about to go to bed now, but I'll re-read this thread tomorrow and see if I can think of anything that I cant think of now.
 
You must log in or register to reply here.
Back
Top