BIND v9.1.3: PC Client with no Domain settings

[Kevin Darcy]

dgoogle wrote:

> Can can anyone please advise on the following scenario:
>
> 1. Client (say NT) has no domain setting in its configuration.
> 1.1 In another case the Client may have an incorrect domain setting.
> 2. ISP uses DHCP to provide client with IP, etc., but no domain setting.
>
> 3. BIND v9 is configured with views, matching the client IP pools. Based
> on IP match, specific zone files are available to the client.
>    For examplex, this may be the case when DNS is servicing multiple
> domains for different ISPs in a wholesale model.
>
> Question:
> If the client has no default domain definition, is there a way to
> configure the view in BIND v9 to associate a default domain with a
> lookup of a hostname.
> Otherwise, if there is no default domain then none of the zone files
> will be searched.

No, appending "default domain"s is *not* the function of the nameserver.
The nameserver just resolves the names which are queried from it. Appending
"default domain"s or search lists is the function of the stub resolver, if
it is implemented at all.

Generally speaking, you should be using fully-qualified names for
everything anyway. That's the most efficient and least ambiguous way to do
DNS resolution. Using shortnames, while convenient, is a nasty, impolite
habit in DNS infrastructure terms.


- Kevin