named appears to be "broken" -- (was: really whacky issues)

[Mark (Help Desk Specialist)]

*This message was transferred with a trial version of CommuniGate(tm) Pro*
i noted a few glitches in my sloppy cut & paste of NAMED.CONF in my 
last email.  I do have the semi-colons at the end of the "options" 
statement where they belong.

It should also be noted that everything which requires name resolution 
appears to be "broken".  Dig, Squid, even "Ping fqdn" -- its the 
resolution which isn't working, as opposed to some internal thing with 
these programs.

I'm baffled, and things are getting out of hand here.

Mark.

On Jan 18, 2004, at 7:20 PM, Edvard Tuinder wrote:

> *This message was transferred with a trial version of CommuniGate(tm) 
> Pro*
> According to Mark:
>> *This message was transferred with a trial version of CommuniGate(tm) 
>> Pro*
>> I have, as I said before, enabled recursion via the options in
>> named.conf
>>
>> when I run nslookup, it responds with the authoritative nameservers 
>> for
>> mydomain.name, regardless of the domain name i request.  the "Name"
>> output is domain.name.requested.mydomain.name -- indicating to me that
>> mydomain.name is being appended to requests.
>>
>> Whenever i run whois the output is "whois: com.whois-servers.net: No
>> address associated with hostname".
>>
>> So, just for the hell of it, I tried setting my hostname to null ("" 
>> --
>> empty quotes), even though it could possibly foul up other services.
>> The results were the same.
>>
>> Any help would be appreciated.
>
> nslookup is the wrong tool to diagnose DNS. It does not use the right 
> library
> calls to be reliable.
>
> In your case, the appending of your local domain name, comes from the 
> fact
> that nslookup uses your /etc/resolv.conf search path. And apparantely 
> your
> zone has a wildcard which causes any query with nslookup to match.
>
> Try using dig for testing, or add a final . to your query (so query for
> domain.com. instead of domain.com).
>
> It'll probably show you that dns resolution itself works correctly.
> If it doesn't, post the real configuration and the addresses of the
> nameservers so we can test it ourselves. Do not edit the configuration,
> only omit any auth-keys for rndc and such.
>
>
> -Ed
>