Dynamic updating help
Kevin Darcy
kcd at daimlerchrysler.com
Tue Sep 11 02:08:09 UTC 2001
"arpa", not "apra"...
- Kevin
David Reid wrote:
> Folks,
>
> I'm trying to get this working on a small private home network. Basically I
> have some static but also have a few computers that come in via a wireless
> connection using DHCP. I'd like to be able to have both forward and reverse
> lookup available for every host on the network at any time, which means
> getting dynamic updating working correctly.
>
> So far it works for hostnames but the reverse doesn't work. The log shows
>
> Sep 10 23:03:59 cube dhcpd: if IN A MITHRIL.dyn.home.net. domain doesn't
> exist add 3000
> IN A MITHRIL.dyn.home.net. 192.168.0.123 add 3000 IN TXT
> MITHRIL.dyn.home.net. "31bf34cb
> 99ef1a1f4c4de4ddf0c875fcf0": success.
> Sep 10 23:03:59 cube named[967]: zone dyn.home.net/IN: sending notifies
> (serial 120)
> Sep 10 23:04:17 cube dhcpd: delete IN PTR
> 123.0.168.192.100-130.0.168.192.in-addr.apra.
> add 3000 IN PTR 123.0.168.192.100-130.0.168.192.in-addr.apra.
> MITHRIL.dyn.home.net.: tim
> ed out.
>
> I know I can't mix dynamic and static in the same file, so I've split
> them... Here are the files...
>
> (I've omitted the key information :-) )
>
> named.conf
>
> options {
> directory "/var/named";
> };
>
> zone "." {
> type hint;
> file "root.hints";
> };
>
> zone "0.0.127.in-addr.arpa" {
> type master;
> file "zones/127.0.0.rev";
> };
>
> zone "home.net" {
> type master;
> file "zones/home.net";
> };
>
> zone "0.168.192.in-addr.arpa" {
> type master;
> file "zones/192.168.0.rev";
> };
>
> zone "dyn.home.net" {
> type master;
> file "zones/dyn.home.net";
> allow-update {
> key DHCP_UPDATER;
> };
> };
>
> zone "100-130.0.168.192.dyn.in-addr.arpa" {
> type master;
> file "zones/192.168.0.dyn.rev";
> allow-update {
> key DHCP_UPDATER;
> };
> };
>
> dhcpd.conf
>
> subnet 192.168.0.0 netmask 255.255.255.0 {
> range 192.168.0.100 192.168.0.130;
> option routers 192.168.0.1;
> ddns-domainname "dyn.home.net.";
> ddns-rev-domainname "100-130.0.168.192.in-addr.apra.";
> }
>
> dyn.home.net
>
> $ORIGIN .
> $TTL 60 ; 1 minute
> dyn.home.net IN SOA ns.dyn.home.net. root.home.net. (
> 120 ; serial
> 300 ; refresh (5 minutes)
> 120 ; retry (2 minutes)
> 21600 ; expire (6 hours)
> 60 ; minimum (1 minute)
> )
> NS ns.dyn.home.net.
> NS ns.home.net.
> $ORIGIN dyn.home.net.
> 100 CNAME 100.100-130.0.168.192.in-addr.arpa.
> 101 CNAME 101.100-130.0.168.192.in-addr.arpa.
> 102 CNAME 102.100-130.0.168.192.in-addr.arpa.
> 103 CNAME 103.100-130.0.168.192.in-addr.arpa.
> 104 CNAME 104.100-130.0.168.192.in-addr.arpa.
> 105 CNAME 105.100-130.0.168.192.in-addr.arpa.
> 106 CNAME 106.100-130.0.168.192.in-addr.arpa.
> 107 CNAME 107.100-130.0.168.192.in-addr.arpa.
> 108 CNAME 108.100-130.0.168.192.in-addr.arpa.
> 109 CNAME 109.100-130.0.168.192.in-addr.arpa.
> 110 CNAME 110.100-130.0.168.192.in-addr.arpa.
> 111 CNAME 111.100-130.0.168.192.in-addr.arpa.
> 112 CNAME 112.100-130.0.168.192.in-addr.arpa.
> 113 CNAME 113.100-130.0.168.192.in-addr.arpa.
> 114 CNAME 114.100-130.0.168.192.in-addr.arpa.
> 115 CNAME 115.100-130.0.168.192.in-addr.arpa.
> 116 CNAME 116.100-130.0.168.192.in-addr.arpa.
> 117 CNAME 117.100-130.0.168.192.in-addr.arpa.
> 118 CNAME 118.100-130.0.168.192.in-addr.arpa.
> 119 CNAME 119.100-130.0.168.192.in-addr.arpa.
> 120 CNAME 120.100-130.0.168.192.in-addr.arpa.
> 121 CNAME 121.100-130.0.168.192.in-addr.arpa.
> 122 CNAME 122.100-130.0.168.192.in-addr.arpa.
> 123 CNAME 123.100-130.0.168.192.in-addr.arpa.
> 124 CNAME 124.100-130.0.168.192.in-addr.arpa.
> 125 CNAME 125.100-130.0.168.192.in-addr.arpa.
> 126 CNAME 126.100-130.0.168.192.in-addr.arpa.
> 127 CNAME 127.100-130.0.168.192.in-addr.arpa.
> 128 CNAME 128.100-130.0.168.192.in-addr.arpa.
> 129 CNAME 129.100-130.0.168.192.in-addr.arpa.
> 130 CNAME 130.100-130.0.168.192.in-addr.arpa.
> $TTL 3000 ; 50 minutes
> MITHRIL A 192.168.0.123
> TXT "31bf34cb99ef1a1f4c4de4ddf0c875fcf0"
>
> 192.168.0.dyn.rev
>
> ;
> ; dynamic home.net domain
> $TTL 1m
> ;
> @ 1m SOA ns.dyn.home.net. root.home.net. (
> 1;
> 5m;
> 2m;
> 6h;
> 1m;
> )
>
> 1m NS ns.dyn.home.net.
> 1m NS ns.home.net.
>
> Apologies for the size of the post, but anyone got any ideas? Thanks for
> all who try to help :)
>
> david
More information about the bind-users
mailing list