Lookup on Local Domain Name Returns Nothing

Richard Petty repettyBOGUS at austin.rr.com
Sun Dec 12 22:24:21 UTC 2004


I'm running BIND9 on White Box Enterprise Linux 3 at my home. I'm using 
dyndns.org for my Internet presence, behind a run-of-the-mill NAT-based 
cable router.

Until recently, I used a bogus private domain name ("something.bogus") 
for my home LAN. I've decided to set up an email server and I changed 
the private domain name of my LAN to match the dyndns-based domain name 
that the outside world sees: "mynet.mine.nu"

BIND9 is working fine, correctly returning information for sites on the 
Internet and on my home LAN. If I do a "host slashdot.org" I get 
"slashdot.org has address 66.35.250.150" and if I do a "host printer" I 
get "printer.mynet.mine.nu has address 192.168.0.199".

I have a couple dyndns subdomains pointed at me, so that "host 
test.mine.nu" returns "test.mine.nu has address 29.112.192.3"... my 
current ISP-assigned IP number.

However, doing "host mynet.mine.nu" (the main name pointed at my home) 
fails. No error is produced; it simply returns an empty line. This 
happens whether the lookup command is executed on my LAN DNS server or 
on any client on my LAN that uses my DNS server.

Dig on a LAN client returns this (edited for privacy):

; <<>> DiG 9.2.2 <<>> mynet.mine.nu
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21293
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;mynet.mine.nu.              IN      A

;; AUTHORITY SECTION:
mynet.mine.nu.       86400   IN      SOA     kayak.mynet.mine.nu. 
admin.mynet.mine.nu. 27 28800 14400 3600000 86400

;; Query time: 19 msec
;; SERVER: 192.168.0.5#53(192.168.0.5)
;; WHEN: Sun Dec 12 01:08:42 2004
;; MSG SIZE  rcvd: 87



Doing dig on another dyndns.org domain name that points to my LAN 
includes entries for many dyndns nameservers, as expected.

And, of course, all this interferes with network servers that do 
hostname() type lookups.

I'm sure it's a very, very simple mistake I've made but, after weeks, I 
cannot detect it. Any theories?

--Richard

Austin, Texas



Listings below contain bogus names and external IP numbers.
"kayak" is my home DNS and mail server:


File: resolv.conf
-----------------------------------------
domain mynet.mine.nu
search mynet.mine.nu
nameserver localhost




File: named.conf
-----------------------------------------
options {
        directory "/var/named";
        forward first;
        forwarders { 29.26.193.63; 29.93.40.68; 29.93.40.70; };
};
controls {
        inet 127.0.0.1 allow { localhost; } keys { rndckey; };
};
zone "." {
        type hint;
        file "named.ca";
};
zone "localhost" {
        allow-update { none; };
        type master;
        file "localhost.zone";
};
zone "0.0.127.in-addr.arpa" {
        allow-update { none; };
        type master;
        file "127.0.0";
};
zone "mynet.mine.nu" {
        type master;
        file "mynet.mine.nu.zone";
};
zone "0.168.192.in-addr.arpa" {
        type master;
        notify no;
        file "192.168.0";
};

include  "/etc/rndc.key";



File: 127.0.0
-----------------------------------------
$TTL 86400
@       IN      SOA     kayak.mynet.mine.nu. admin.mynet.mine.nu.     (
                                1997022717 ; serial
                                28800 ; refresh
                                14400 ; retry
                                3600000 ; expire
                                86400 ; ttl
                                )
;
        NS      localhost.
1       PTR     localhost.



File: 192.168.0
-----------------------------------------
$TTL 86400
@       IN      SOA     kayak.mynet.mine.nu. admin.mynet.mine.nu.     (
                                1997022720 ; serial
                                28800 ; refresh
                                14400 ; retry
                                3600000 ; expire
                                86400 ; ttl
                                )
;
        NS      kayak.mynet.mine.nu.

1       PTR     router.mynet.mine.nu.
2       PTR     lombard.mynet.mine.nu.
5       PTR     kayak.mynet.mine.nu.
6       PTR     g4.mynet.mine.nu.
30      PTR     bridge.mynet.mine.nu.
199     PTR     printer.mynet.mine.nu.



File: mynet.mine.nu.zone
-----------------------------------------
$TTL 86400
@       IN      SOA     kayak.mynet.mine.nu. admin.mynet.mine.nu.  (
                                27 ; serial
                                28800 ; refresh
                                14400 ; retry
                                3600000 ; expire
                                86400 ; ttl
                                )
;
                NS      kayak.mynet.mine.nu. ;Inet Address of name server

localhost       A       127.0.0.1
router          A       192.168.0.1
lombard         A       192.168.0.2
kayak           A       192.168.0.5
g4              A       192.168.0.6
bridge          A       192.168.0.30
printer         A       192.168.0.199



More information about the bind-users mailing list