Re: dns error
From: Herb Martin (news_at_LearnQuick.com)
Date: 03/22/04
- Next message: William Stacey [MVP]: "Re: query DNS to find mx records ?"
- Previous message: William Stacey [MVP]: "Re: Transcender DNS Question"
- In reply to: rosie: "Re: dns error"
- Next in thread: Ace Fekay [MVP]: "Re: dns error"
- Reply: Ace Fekay [MVP]: "Re: dns error"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 22 Mar 2004 10:03:35 -0600
> Herb this is driving me insane. If I take my firewall off
> I could get online to my comcast homepage. I don't know
> why it keeps doing this. Any more ideas or advice? please
It is very common for firewalls to block ICMP (ping and tracert);
it is less common to block one but not both. It is also fairly
common for someone to use a firewall and be frustratged by
losing functionality.
A common 'solution' (and wrong) is to just disable the firewall
so completely that there is little point in having it there.
> Default Gateway.....: 68.45.101.1
> DNS Servers.....: 68.46.144.6
> c:\>ping 68.45.101.1
> Pinging 68.45.101.1 with 32 bytes of data:
> Request timed out.
Unless you default gateway is just configured to ignore
"ping" (uncommon but possible) then this is serious and there
would be little point in continuing the trouble shooting until
this part is solved. (Not the "unless" though)
> c:\>tracert 68.45.101.1
> Tracing route to 68.45.101.1 over a maximum of 30 hops
> 1 * * * Request timed out. same line repeated to # 8
> 9 <10 ms 10 ms 10 ms cdnt02 a
> rtr.trnrsv01.nj.comcast.net [68.45.101.1]
Ok, this is very odd. 1) It worked when ping failed 2) it
is ONE HOP away yet didn't work until the 9th hop.
Where did you issue this tracert? ON the gateway or an
internal machine? If on an internal machine if is YOUR
problem perhaps.
This looks like some kind of problem with your ISPs
routing but it so goofy that this is difficult to say for certain.
I would ask the ISP about this at the least.
> c:\>tracert 68.46.144.6
> Tracing route to ns02.trnrsv01.nj.comcast.net [68.46.144.6]
> 6 * 10 ms 10 ms ns02.trnrsv01.nj.comcast.net [ 68.46.144.6]
Tracing to the DNS server seems to work fine which is somewhat
surprising given the behavior above.
BTW, this is NOT a DNS issue -- DNS is working fine. It might
be a "ping" (ICMP) only problem except that you were having
trouble to start with.
When you get the problem (original problem you posted) in IE,
you might try using the IP address, e.g.,
http://www.LearnQuick.Com can also be reached at:
http://161.58.177.171 (you can get these numbers using NSLookup.)
Note: SOME websites won't work this way because they are really
"multiple sites" on a single IP-machine but most of the big companies,
e.g., MS, yahoo, dell, etc, probably will and many small companies,
like mine too.
If the DNS name fails and the IP works, then THAT is prima facie
evidence of a DNS resolution problem -- but if you can use NSLookup
that is evidence it is NOT DNS and so implies some sort of weird,
or intermittent routing or (directly) a router problem.
-- Herb Martin > C:\>nslookup www.learnquick.com 68.46.144.6 > Name: www.learnquick.com > Address: 161.58.177.171 > > C:\>nslookup www.learnquick.com 68.46.144.5 > Name: www.learnquick.com > Address: 161.58.177.171
- Next message: William Stacey [MVP]: "Re: query DNS to find mx records ?"
- Previous message: William Stacey [MVP]: "Re: Transcender DNS Question"
- In reply to: rosie: "Re: dns error"
- Next in thread: Ace Fekay [MVP]: "Re: dns error"
- Reply: Ace Fekay [MVP]: "Re: dns error"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
