BIND9: Great Except for Local Domain
Richard Petty
repettyBOGUS at austin.rr.com
Sat Dec 11 21:22:12 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 70.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 if the lookup
command is executed either on my LAN DNS server or on any client on my LAN
pointed at my DNS server.
Of course, this hoses network servers that do a hostname() type lookup.
I'm sure it's a very, very simply 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