bind-users Digest V10 #168
James DeLoach
jasdel49 at tx.rr.com
Fri Jun 27 19:59:03 UTC 2008
Please remove me from this mailing list and others that I may be subscribed
to. Due to a disk crash, I don't have any of the originial messages from
when I subscribed to the lists.
Thanks,
James
----- Original Message -----
From: "BIND Users Mailing List" <bind-users at isc.org>
To: "bind-users digest users" <ecartis at isc.org>
Sent: Saturday, June 21, 2008 19:13
Subject: bind-users Digest V10 #168
> bind-users Digest Sat, 21 Jun 2008 Volume: 10 Issue: 168
>
> In This Issue:
> why does dig +trace change outcome?
> Re: why does dig +trace change outcome?
> Re: why does dig +trace change outcome?
> Re: why does dig +trace change outcome?
>
> ----------------------------------------------------------------------
>
> Date: Sat, 21 Jun 2008 11:53:11 -0400 (EDT)
> From: Hal Brooks <hal at uga.edu>
> Subject: why does dig +trace change outcome?
>
>
> Some name servers, but not all, are unable to resolve
> krensavage.com
>
> But even those which are ordinarily unable to resolve
> krensavage.com seem to be able to get answers with dig if
> the +trace option is used.
>
> For example, this web site:
>
> http://www.kloth.net/services/dig.php
>
> offers a browser interface to dig. If you use their
> localhost as the server and query for an A record, but
> don't specify "trace", then the unhappy result is
> "connection timed out; no servers could be reached", but if
> you do specify "trace" then you get 6 answers.
>
> Similarly from the command line:
>
> dig @dns1.uga.edu krensavage.com # times out
> dig @dns1.uga.edu krensavage.com +trace # OK
>
> But other name servers handle it fine (and dig works
> even without +trace):
>
> dig @ns1.usg.edu krensavage.com # OK
> dig @ns1.usg.edu krensavage.com # also OK
>
> The only shortcoming I see with the krensavage.com setup is
> that the whois record only has 1 name server
> (yns1.yahoo.com) listed.
>
> For comparison, olivebarn.com, has similar characteristics
> (though the whois record lists both yns1.yahoo.com and
> yns2.yahoo.com), but it doesn't result in the same failures
> I'm seeing for krensavage.com.
>
> Any and all help appreciated.
>
> -hal
>
> ------------------------------
>
> Date: Sat, 21 Jun 2008 23:52:39 +0200
> From: "Genco Yilmaz" <gencoyilmaz at gmail.com>
> Subject: Re: why does dig +trace change outcome?
>
> On Sat, Jun 21, 2008 at 5:53 PM, Hal Brooks <hal at uga.edu> wrote:
>>
>> Some name servers, but not all, are unable to resolve
>> krensavage.com
>>
>> But even those which are ordinarily unable to resolve
>> krensavage.com seem to be able to get answers with dig if
>> the +trace option is used.
>>
>> For example, this web site:
>>
>> http://www.kloth.net/services/dig.php
>>
>> offers a browser interface to dig. If you use their
>> localhost as the server and query for an A record, but
>> don't specify "trace", then the unhappy result is
>> "connection timed out; no servers could be reached", but if
>> you do specify "trace" then you get 6 answers.
>>
>> Similarly from the command line:
>>
>> dig @dns1.uga.edu krensavage.com # times out
>> dig @dns1.uga.edu krensavage.com +trace # OK
>>
>> But other name servers handle it fine (and dig works
>> even without +trace):
>>
>> dig @ns1.usg.edu krensavage.com # OK
>> dig @ns1.usg.edu krensavage.com # also OK
>>
>> The only shortcoming I see with the krensavage.com setup is
>> that the whois record only has 1 name server
>> (yns1.yahoo.com) listed.
>>
>> For comparison, olivebarn.com, has similar characteristics
>> (though the whois record lists both yns1.yahoo.com and
>> yns2.yahoo.com), but it doesn't result in the same failures
>> I'm seeing for krensavage.com.
>>
>> Any and all help appreciated.
>>
>> -hal
>>
> Hello Hal,
> This domain has been delegated to only 1 NS server at root servers.
>
> #dig +short +norec ns krensavage.com @a.gtld-servers.net
> yns1.yahoo.com.
>
> Whereas, authoritative server lists 3 other servers;
>
> #dig +short +norec ns krensavage.com @yns1.yahoo.com
> ns8.san.yahoo.com.
> yns2.yahoo.com.
> yns1.yahoo.com.
> ns9.san.yahoo.com.
>
> I suppose, it is better to fix this mismatch first. Because trace option
> causes dig to make iterative queries,
> you don't see the response from the cache.
>
>
>
> ------------------------------
>
> Subject: Re: why does dig +trace change outcome?
> From: Paul Vixie <Paul_Vixie at isc.org>
> Date: 21 Jun 2008 23:11:25 +0000
>
> "Genco Yilmaz" <gencoyilmaz at gmail.com> writes:
>
>> This domain has been delegated to only 1 NS server at root servers.
>
> you mean "at the TLD servers". the root servers delegate to COM in this
> case.
>
>> #dig +short +norec ns krensavage.com @a.gtld-servers.net
>> yns1.yahoo.com.
>>
>> Whereas, authoritative server lists 3 other servers;
>>
>> #dig +short +norec ns krensavage.com @yns1.yahoo.com
>> ns8.san.yahoo.com.
>> yns2.yahoo.com.
>> yns1.yahoo.com.
>> ns9.san.yahoo.com.
>>
>> I suppose, it is better to fix this mismatch first.
>
> always.
> --
> Paul Vixie
>
> ------------------------------
>
> Date: Sat, 21 Jun 2008 19:14:02 -0400 (EDT)
> From: Hal Brooks <hal at uga.edu>
> Subject: Re: why does dig +trace change outcome?
>
>
>
> On Sat, 21 Jun 2008, Genco Yilmaz wrote:
>
>> On Sat, Jun 21, 2008 at 5:53 PM, Hal Brooks <hal at uga.edu> wrote:
>>>
>>> Some name servers, but not all, are unable to resolve
>>> krensavage.com
>>>
>>> But even those which are ordinarily unable to resolve
>>> krensavage.com seem to be able to get answers with dig if
>>> the +trace option is used.
>>>
>>> For example, this web site:
>>>
>>> http://www.kloth.net/services/dig.php
>>>
>>> offers a browser interface to dig. If you use their
>>> localhost as the server and query for an A record, but
>>> don't specify "trace", then the unhappy result is
>>> "connection timed out; no servers could be reached", but if
>>> you do specify "trace" then you get 6 answers.
>>>
>>> Similarly from the command line:
>>>
>>> dig @dns1.uga.edu krensavage.com # times out
>>> dig @dns1.uga.edu krensavage.com +trace # OK
>>>
>>> But other name servers handle it fine (and dig works
>>> even without +trace):
>>>
>>> dig @ns1.usg.edu krensavage.com # OK
>>> dig @ns1.usg.edu krensavage.com # also OK
>>>
>>> The only shortcoming I see with the krensavage.com setup is
>>> that the whois record only has 1 name server
>>> (yns1.yahoo.com) listed.
>>>
>>> For comparison, olivebarn.com, has similar characteristics
>>> (though the whois record lists both yns1.yahoo.com and
>>> yns2.yahoo.com), but it doesn't result in the same failures
>>> I'm seeing for krensavage.com.
>>>
>>> Any and all help appreciated.
>>>
>>> -hal
>>>
>> Hello Hal,
>> This domain has been delegated to only 1 NS server at root servers.
>>
>> #dig +short +norec ns krensavage.com @a.gtld-servers.net
>> yns1.yahoo.com.
>>
>> Whereas, authoritative server lists 3 other servers;
>>
>> #dig +short +norec ns krensavage.com @yns1.yahoo.com
>> ns8.san.yahoo.com.
>> yns2.yahoo.com.
>> yns1.yahoo.com.
>> ns9.san.yahoo.com.
>>
>> I suppose, it is better to fix this mismatch first. Because trace option
>> causes dig to make iterative queries,
>> you don't see the response from the cache.
>>
>
> Thanks, I'll try to get the RP to do that. But
> krensavage.com isn't my domain. I'm just trying to get the
> uga.edu NS to be able to see it. And since some others can
> get it, it's difficult for me to say that the problem is
> with their config and not mine.
>
> -hal
>
> ------------------------------
>
> End of bind-users Digest V10 #168
> *********************************
>
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Scanned with Copfilter Version 0.84beta3a (P3Scan 2.2.1)
> AntiSpam: SpamAssassin 3.2.3
> AntiVirus: ClamAV 0.91.2/7530 - Sat Jun 21 17:30:34 2008
> AntiVirus: AVG 7.5.51, engine 442 270.4.1/1512 2008-06-21
> AntiVirus: F-PROT 4.6.8 Engine version: 3.16.16
> SIGN.DEF 16 Jun08 - SIGN2.DEF 17 Jun08 - MACRO.DEF 16 Jun08
> by Markus Madlener @ http://www.copfilter.org
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Scanned with Copfilter Version 0.84beta3a (ProxSMTP 1.6)
AntiVirus: ClamAV 0.91.2/7578 - Fri Jun 27 12:38:15 2008
AntiVirus: AVG 7.5.51, engine 442 270.4.1/1522 2008-06-27
AntiVirus: F-PROT 4.6.8 Engine version: 3.16.16
SIGN.DEF 25 Jun08 - SIGN2.DEF 25 Jun08 - MACRO.DEF 25 Jun08
by Markus Madlener @ http://www.copfilter.org
More information about the bind-users
mailing list