DNS servers wont resolve certain DNS names

[Barry Margolin]

In article <bn3ufm$9ca$1 at sf1.isc.org>, Mike Hale <mhale at TOUA.net> wrote:
>>> -----Original Message-----
>>> From: Barry Margolin [mailto:barry.margolin at level3.com]=20
>>> Sent: Tuesday, October 21, 2003 9:46 AM
>>>To: comp-protocols-dns-bind at isc.org
>>> Subject: Re: DNS servers wont resolve certain DNS names
>>>=20
>>>=20
>>> In article <bn3n3s$13m$1 at sf1.isc.org>, Mike Hale=20
>>> <mhale at TOUA.net> wrote:
>>> >Thanks for the help so far. I'm still working through this problem=20
>>> >without much success. The results you got below are typical=20
>>> of what I'm=20
>>> >getting here except for what I mention below. Just this one=20
>>> site times=20
>>> >out resolving through our servers. Other sites resolve just=20
>>> fine. I'd=20
>>> >like to chaulk it up to what Peter Hkanson said about=20
>>www.hardocp.com=20
>>>having errors but others servers seem to be able to resolve it.
>
>>What happens when you try to ping or traceroute to ns.itotf.com?
>
>[root at toua root]# ping ns.itotf.com
>PING ns.itotf.com (69.56.175.249) from 64.25.64.32 : 56(84) bytes of
>data.
>
>--- ns.itotf.com ping statistics ---
>102 packets transmitted, 0 received, 100% loss, time 101020ms
>
>[root at toua root]# traceroute ns.itotf.com
>traceroute to ns.itotf.com (69.56.175.249), 30 hops max, 38 byte packets
> 1  bdrrtr1-co-eth0.toua.net (64.25.64.1)  17.082 ms  3.208 ms  1.778 ms
> 2  * * *
>[...]
>30  * * *
>
>Resolves, fine but sure doesn't like to answer pings.

It does for me.  Like I said earlier, this indicates that there's a
communications problem between your site and theirs.  Most likely a packet
filter or a routing issue.  And it seems to be on the ISP router that your
border router connects to.

-- 
Barry Margolin, barry.margolin at level3.com
Level(3), Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.