Search Again:

Re: Problems resolving (my case is similar)

From: Jody McAlister
Date: Thursday, October 28, 2004
Time: 2:34:03 pm

This happened to me starting yesterday as well. I hit reload and it
almost always works immediately.

On Oct 28, 2004, at 2:06 PM, Nicholas Orr wrote:

> Funny this issue should come up now. I had the same thing happen to
> me yesterday on half a dozen or so sites. First lookup failed, second
> was fine. I didn't think anything of it until now, and this is the
> first time I've noticed it.
>
> nick
>
> On 28/10/2004, at 11:27 PM, Simon Wright wrote:
>
>> I and my OS X users and some Windows users are having this same
>> problem: first hit on a new host fails, second one succeeds. I'm
>> using Firefox so it's not just Safari.
>>
>> I hope that M&M are researching this - it's been happening on and off
>> for me for months/years. It seems to come and go with no discernible
>> pattern. Restarting clients or DNS does not seem to make a
>> difference. It feels like a timing issue: clients not being patient
>> enough for the response or the response is not completing in some
>> way. Right now it's very reproducible: try to go to any web site
>> we've not visited before and the first hit always fails. The second
>> hit almost always succeeds.
>>
>> I think I've found a short-term work around: enter your DNS twice in
>> your network preferences.
>>
>> Reply here if it seems to work for you.
>>
>> Simon
>>
>> On Oct 27, 2004, at 10:18 PM, Scott Haneda wrote:
>>
>>> on 10/27/04 5:15 PM, Scott Haneda at lists@newgeo.com wrote:
>>>
>>>> I am having the exact same issue, and it is driving me nuts. I
>>>> don't know
>>>> where to go to troubleshoot this either.
>>>
>>> Well, I have run the gamut of tests on this case and I am getting
>>> pretty
>>> stuck. Installed a demo copy of QDNS on a new machine on my same
>>> colo
>>> network and am still having no luck getting lookups to resolve on
>>> the first
>>> try in Safari.
>>>
>>> I am about to buy another copy of QDNS just to get the 30 days
>>> support on
>>> this issue, about to take this to the bind mailing list as well,
>>> hopefully
>>> they are nice to me :-)
>>>
>>> So far I have installed QDNS on a new machine, the problem persists,
>>> the
>>> problem also happens inside my colo network viewing over TB2. I
>>> don't seem
>>> to have any problems resolving local domains for which I am serving
>>> DNS on
>>> my colo network. I think I am working locally just fine, I think
>>> that
>>> getting out seems to be my problem.
>>>
>>> I only just learned about the +trace option for dig, and I sure hope
>>> this is
>>> promising, here is what I get when I look up a domain while ssh'd
>>> into a
>>> machine on the same subnet as my DNS machine: (several attempts,
>>> comments
>>> interspersed)
>>>
>>> crfg.org is a domain my DNS server has more than likely not seen
>>> before:
>>>
>>> dig crfg.org +trace
>>>
>>> ; <<>> DiG 9.2.2 <<>> crfg.org +trace
>>> ;; global options: printcmd
>>> .. 513866 IN NS D.ROOT-SERVERS.NET.
>>> .. 513866 IN NS E.ROOT-SERVERS.NET.
>>> .. 513866 IN NS F.ROOT-SERVERS.NET.
>>> .. 513866 IN NS G.ROOT-SERVERS.NET.
>>> .. 513866 IN NS H.ROOT-SERVERS.NET.
>>> .. 513866 IN NS I.ROOT-SERVERS.NET.
>>> .. 513866 IN NS J.ROOT-SERVERS.NET.
>>> .. 513866 IN NS K.ROOT-SERVERS.NET.
>>> .. 513866 IN NS L.ROOT-SERVERS.NET.
>>> .. 513866 IN NS M.ROOT-SERVERS.NET.
>>> .. 513866 IN NS A.ROOT-SERVERS.NET.
>>> .. 513866 IN NS B.ROOT-SERVERS.NET.
>>> .. 513866 IN NS C.ROOT-SERVERS.NET.
>>> ;; Received 244 bytes from 64.84.37.40#53(64.84.37.40) in 8 ms
>>>
>>> dig: Couldn't find server 'D.ROOT-SERVERS.NET': No address
>>> associated with
>>> nodename
>>>
>>>
>>> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> So there were 1 errors in that first one, something about the D root.
>>> Next try was equally bad:
>>> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>
>>> dig crfg.org +trace
>>>
>>> ; <<>> DiG 9.2.2 <<>> crfg.org +trace
>>> ;; global options: printcmd
>>> .. 513853 IN NS I.ROOT-SERVERS.NET.
>>> .. 513853 IN NS J.ROOT-SERVERS.NET.
>>> .. 513853 IN NS K.ROOT-SERVERS.NET.
>>> .. 513853 IN NS L.ROOT-SERVERS.NET.
>>> .. 513853 IN NS M.ROOT-SERVERS.NET.
>>> .. 513853 IN NS A.ROOT-SERVERS.NET.
>>> .. 513853 IN NS B.ROOT-SERVERS.NET.
>>> .. 513853 IN NS C.ROOT-SERVERS.NET.
>>> .. 513853 IN NS D.ROOT-SERVERS.NET.
>>> .. 513853 IN NS E.ROOT-SERVERS.NET.
>>> .. 513853 IN NS F.ROOT-SERVERS.NET.
>>> .. 513853 IN NS G.ROOT-SERVERS.NET.
>>> .. 513853 IN NS H.ROOT-SERVERS.NET.
>>> ;; Received 260 bytes from 64.84.37.40#53(64.84.37.40) in 3 ms
>>>
>>> org. 172800 IN NS TLD1.ULTRADNS.NET.
>>> org. 172800 IN NS TLD2.ULTRADNS.NET.
>>> ;; Received 108 bytes from 192.36.148.17#53(I.ROOT-SERVERS.NET) in
>>> 103 ms
>>>
>>> crfg.org. 86400 IN NS ns2.fastdns.net.
>>> crfg.org. 86400 IN NS ns1.fastdns.net.
>>> ;; Received 73 bytes from 204.74.112.1#53(TLD1.ULTRADNS.NET) in 6 ms
>>>
>>> dig: Couldn't find server 'ns2.fastdns.net': No address associated
>>> with
>>> nodename
>>>
>>> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> Now I find that I can not get to the fastdns.net server in the
>>> above, the
>>> below one seems to work:
>>> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>
>>> dig crfg.org +trace
>>>
>>> ; <<>> DiG 9.2.2 <<>> crfg.org +trace
>>> ;; global options: printcmd
>>> .. 513841 IN NS B.ROOT-SERVERS.NET.
>>> .. 513841 IN NS C.ROOT-SERVERS.NET.
>>> .. 513841 IN NS D.ROOT-SERVERS.NET.
>>> .. 513841 IN NS E.ROOT-SERVERS.NET.
>>> .. 513841 IN NS F.ROOT-SERVERS.NET.
>>> .. 513841 IN NS G.ROOT-SERVERS.NET.
>>> .. 513841 IN NS H.ROOT-SERVERS.NET.
>>> .. 513841 IN NS I.ROOT-SERVERS.NET.
>>> .. 513841 IN NS J.ROOT-SERVERS.NET.
>>> .. 513841 IN NS K.ROOT-SERVERS.NET.
>>> .. 513841 IN NS L.ROOT-SERVERS.NET.
>>> .. 513841 IN NS M.ROOT-SERVERS.NET.
>>> .. 513841 IN NS A.ROOT-SERVERS.NET.
>>> ;; Received 276 bytes from 64.84.37.40#53(64.84.37.40) in 4 ms
>>>
>>> org. 172800 IN NS TLD1.ULTRADNS.NET.
>>> org. 172800 IN NS TLD2.ULTRADNS.NET.
>>> ;; Received 108 bytes from 192.228.79.201#53(B.ROOT-SERVERS.NET) in
>>> 16 ms
>>>
>>> crfg.org. 86400 IN NS ns2.fastdns.net.
>>> crfg.org. 86400 IN NS ns1.fastdns.net.
>>> ;; Received 73 bytes from 204.74.112.1#53(TLD1.ULTRADNS.NET) in 5 ms
>>>
>>> crfg.org. 86400 IN A 66.70.253.166
>>> crfg.org. 86400 IN NS ns2.fastdns.net.
>>> crfg.org. 86400 IN NS ns1.fastdns.net.
>>> ;; Received 121 bytes from 64.33.120.76#53(ns2.fastdns.net) in 83 ms
>>>
>>>
>>> Can someone help me translate what this means and possibly offer some
>>> insight as to why it may be happening.
>>>
>>>
>>>
>>>
>>> --
>>> -------------------------------------------------------------
>>> Scott Haneda Tel: 415.898.2602
>>> <http://www.newgeo.com> Fax: 313.557.5052
>>> <scott@newgeo.com> Novato, CA U.S.A.
>>>
>>>
>>>
>>>
>>>
>> --
>> > Simon J Wright - Chief Systems Architect
>> >> Knowledge Sharing Systems, Inc.
>> > NCSU Centennial Campus
>> > 940 Main Campus Drive, Suite 150
>> > Raleigh, NC 27606
>> Tel: 919-790-9895x104 <> Fax: 919-850-0851
>> >>> http://www.knowledgesharing.com <<<
>>
>>
>
>
>
Jody McAlister
President
In-Site Communications
707-765-9993/800-998-1711


Messages In This Thread:


Return to Digital Point Solutions' Home Page

home
products
services
support
email lists
optigold isp
optigold isp news
home inspection
inspectrix
java companion
oracle
quickdns pro
search engine
veterinary
tips
employees
free tools
portfolio
jobs
contact

Sales:
888/4-DPOINT

Support:
858/452-3696


Search:
Add this to your site