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

*This message was transferred with a trial version of CommuniGate(tm) Pro*
NAMED.CONF
// $FreeBSD: src/etc/namedb/named.conf,v 1.13 2002/11/26 07:55:44 ume
Exp $
//
// Refer to the named.conf(5) and named(8) man pages for details. If
// you are ever going to setup a primary server, make sure you've
// understood the hairy details of how DNS is working. Even with
// simple mistakes, you can break connectivity for affected parties,
// or cause huge amount of useless Internet traffic.

options {
directory "/etc/namedb";
pid-file "/var/run/named/pid";

forwarders {
205.201.1.10;
};

recursion yes
}

zone "." {
type hint;
file "named.root";
};

zone "0.0.127.IN-ADDR.ARPA" {
type master;
file "localhost.rev";
};

// RFC 3152
zone
"1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0 .0.0.0.0.0.0.0.IP6.ARP
A"
{
type master;
file "localhost-v6.rev";
};

// RFC 1886 -- deprecated
zone
"1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0 .0.0.0.0.0.0.0.IP6.INT
" {
type master;
file "localhost-v6.rev";
};

zone "marknernberg.com" {
type master;
file "/etc/namedb/marknernberg.com.db";
};

RESOLV.CONF
nameserver 66.70.83.244
nameserver 80.249.99.30
nameserver 205.201.1.20


My hosts address is 151.201.141.231, the hostname is
"router.downtownhelpdesk.ath.cx"

Mark Nernberg


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
>