Bind 8.4.4

[Kevin Darcy]

Blankenship, George wrote:

>i have a slave box i just built with the lastest patch's and all with bind
>8.4.4 that local network users can't reslove named from the box with the
>default name unless i force the full server name. Then when i goto another
>segment and force the nslookup server to the same box without the full
>server name it won't work,  but will with the full server name.  now on all
>the other box's which are running bind 8.4.4 i can connect there there local
>segment servers via just the server name with out any problems.   But if i
>go and force the server to one of the other slaves via nslookup it will
>resolve names just fine either way.   anyone have a clue to what could be
>wrong with this one box?
>
I assume by "full name", you mean a name with the domain appended to it, 
and by "just the server name", you mean the server name with no domain 
appended to it. Right?

If so, then please be aware that the appendage of the domain to a lookup 
string is a resolver function and has nothing to do with the nameserver 
_per_se_, even if a nameserver instance happens to be running on the box 
from which you are issuing the lookup. Check the /etc/resolv.conf files 
on your clients (if Unix/Linux) or the "winipcfg" or "ipconfig" command, 
if they are Wintel boxes...

                                                                         
                           - Kevin