DHCP server that supports Dynamic Updates

[Kevin Darcy]

thomas at shurflo.com wrote:

> "Mike Roest" <bind at blahz.ab.ca> wrote in message news:<ajg965$8d9s$1 at isrv4.isc.org>...
> > The ISC dhcpd supports dynamic updates.  I'm using 3.0p1.  The dynamic
> > updates work great, the reason you didn't see any reference to nsupdate
> > is because the dhcp server sends the updates directly to the DNS.  It
> > doesn't use a intermediate utility.
> >
> > --Mike
>
> I downloaded it and installed it.  Both Bind and Dhcp work fine
> separately, but updates are not occurring. I get the following error
> message:
>
> Aug 15 08:48:29 TRIP dhcpd: if IN A JANET-TEMP.testsrv.com rrset
> doesn't exist add 21600 IN A JANET-TEMP.testsrv.com 192.168.4.53:
> timed out.
>
> Apparently a "time-out" is occurring during the DNS update from DHCP,
> but neither Google group searches nor man pages offer any clues as to
> why.
>
> Anyone familiar with this error? I've posted the named.conf and the
> dhcpd.conf files for reference.
>
> I tried to use "nsupdate" to manually update DNS, but I keep getting
> the error message "REFUSED" when I try(debug mode) - but I don't
> really know how to use it.
>
> I changed the IP network and domain for this example to hide company
> info.  I may have made a typo or 2 in conversion.
>
> (Thanks Mike for the pointer).
>
> # ******************
> # *** DHCPD.CONF ***
> # ******************
>
> authoritative;
>
> subnet 192.168.10.0 netmask 255.255.248.0 {
>         option ntp-servers eagle.testsrv.com;
>         option netbios-name-servers 192.168.10.45;
>         option domain-name-servers 192.168.10.90;
>         option broadcast-address 192.168.7.255;
>         option subnet-mask 255.255.248.0;
>         option routers 192.168.3.122;
>         option domain-name "testsrv.com";
>         range 192.168.4.50 192.168.4.250;
>         ddns-domainname "testsrv.com";
>         }
> ?
>         ddns-update-style ad-hoc;
>
> # ******************
> # *** NAMED.CONF ***
> # ******************
>
> // generated by named-bootconf.pl
>
> options {
>         listen-on { 192.168.0/21; };
>         directory "/var/named";
>         forward first;
>
>         /*
>          * If there is a firewall between you and nameservers you want
>          * to talk to, you might need to uncomment the query-source
>          * directive below.  Previous versions of BIND always asked
>          * questions using port 53, but BIND 8.1 uses an unprivileged
>          * port by default.
>          */
>         // query-source address * port 53;
> };
>
> //
> // a caching only nameserver config
> //
>
> zone "." {
>         TYPE hint;
>         file "named.ca";
> };
>
> zone "0.0.127.in-addr.arpa" in {
>         type master;
>         file "named.local";
> };
>
> zone "testsrv.com" in {
>         type master;
>         file "db.testsrv";
> };
>
> zone "0.168.192.in-addr.arpa" in {
>         type master;
>         file "db.192.168.10";
> };
>
> zone "1.168.192.in-addr.arpa" in {
>         type master;
>         file "db.192.168.1";
> };
>
> zone "2.168.192.in-addr.arpa" in {
>         type master;
>         file "db.192.168.2";
> };
>
> zone "3.168.192.in-addr.arpa" in {
>         type master;
>         file "db.192.168.3";
> };
>
> zone "4.168.192.in-addr.arpa" in {
>         type master;
>         file "db.192.168.4";
>         allow-update { 192.168.10.90; };
> };
>
> zone "5.168.192.in-addr.arpa" in {
>         type master;
>         file "db.192.168.5";
> };
>
> zone "6.168.192.in-addr.arpa" in {
>         type master;
>         file "db.192.168.6";
>         allow-update { 192.168.10.90; };
> };
>
> zone "7.168.192.in-addr.arpa" in {
>         notify no;
>         type master;
>         file "db.192.168.7";
> };
>
> zone "11.168.192.in-addr.arpa" in {
>         notify no;
>         type master;
>         file "db.192.168.11";
> };
>
> zone "12.168.192.in-addr.arpa" in {
>         type master;
>         file "db.192.168.12";
> };

I think you're on the right track attempting to use "nsupdate" to isolate the problem.
I'd recommend reading up on the documentation so you learn how to use it properly. If
you're still having problems, report back to the list.


- Kevin