Odd search order and delegation problem

[Adam Augustine]

Ack! That would be the problem then. Guess we are going to have to go =
with
fully qualified domain names.

Thanks for the help,
	Adam Augustine

-----Original Message-----
From: Barry Margolin [mailto:barmar at genuity.net]
Sent: Wednesday, December 20, 2000 3:58 PM
To: comp-protocols-dns-bind at moderators.isc.org
Subject: Re: Odd search order and delegation problem


In article <91rc8n$3ep at pub3.rc.vix.com>,
Chicken Man <chicknmon at hotmail.com> wrote:
>Both of which behave as expected given the resolv.conf. But...
>
>[root at kando named]# ping multi.de
>PING multi.de (194.195.64.35) from 10.1.6.1 : 56(84) bytes of data.
>From router.example.com (10.1.1.1): Destination Host Unreachable
>From router.example.com (10.1.1.1): Destination Host Unreachable
>From router.example.com (10.1.1.1): Destination Host Unreachable
>From router.example.com (10.1.1.1): Destination Host Unreachable
>=F2
>--- mail.de ping statistics ---
>4 packets transmitted, 0 packets received, +4 errors, 100% packet loss
>[root at kando named]#
>
>Which is the Internet multi.de address rather than =
multi.de.example.com,
not=20
>what one would expect with the resolv.conf as shown above.

If a name contains any dots, it's tried as a fully qualified name =
before
trying to append the domains in resolv.conf's "search" or "domain"
directives.  RFC 1535 says:

   Further, in any event where a "." exists in a specified name it
   should be assumed to be a fully qualified domain name (FQDN) and
   SHOULD be tried as a rooted name first.

--=20
Barry Margolin, barmar at genuity.net
Genuity, Burlington, 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.