Problem w/ 8.2.1 ( was: possible problem w/ 8.2.1)

Jim Reid jim at mpn.cp.philips.com
Fri Jul 2 09:08:09 UTC 1999


>>>>> "Kevin" == Martin, Kevin <kevinm at crt.com> writes:

    Kevin> My real issue is not w/ nslookup, dig, or host.  It's with
    Kevin> the fact that the 8.2.1 version of Bind is apparently
    Kevin> ignoring the search directive in the resolv.conf file.  It
    Kevin> never parses the rest of the domains in the directive after
    Kevin> the first one.  I just proved that fact by starting Bind
    Kevin> 8.2.1, changing my client resolv.conf to put nb.com as my
    Kevin> FIRST domain in the search directive, and doing "nslookup
    Kevin> host.nc" on my client.  Low and behold, the answer came
    Kevin> back with the correct information.  I then changed my
    Kevin> resolv.conf back to being "search il.nb.com nb.com" and did
    Kevin> the "nslookup host.nc" and received the error
    Kevin> "dns1.il.nb.com can't find host.nc: Server failed".  I will
    Kevin> play w/ the host command as you show above but I still
    Kevin> maintain that the problem is not w/ the tool but with the
    Kevin> server.

This is bizarre. If the reply code is SERVFAIL instead of an expected
NXDOMAIN, then that suggests the name server is faulty. Changing
resolv.conf shouldn't make any difference to the way the name server
behaves or influence how it answers queries.


More information about the bind-users mailing list