Dynamic DNS Server Updates

[Ryan Davis]

Greetings:

Been reading through the list for about a week and don't seem to see an
answer to this, but I have a BIND 9.3.1 server running on Solaris 10 x86
with a fake domain (internal network) and can't seem to get my DHCP clients
to update their records to it.  The DHCP addresses to my clients are
provided by a router and I don't want to run an additional DHCP server as
the router works fine.  Is there a way to get my clients to update to the
DDNS server or have the server update these records when it tries to
register itself with the DNS server?  Nothing seems to be showing up in my
Windows Event log about not being able to register DNS so I'm assuming it's
on the BIND side.  Connectivity seems fine as I can see the clients talking
to the server through a "snoop" command.

Any help is appreciated.  

Respectfully,

Ryan Davis

=========================================================
My config files

bash-3.00# named -v
BIND 9.3.1
bash-3.00# cat /etc/named.conf
options {
        directory "/var/named";
        pid-file "/var/run/named.pid";
        query-source port *;
        allow-query { any; };
        allow-recursion { any; };
        listen-on { any; };
        dump-file "named_dump.db";
        statistics-file "named.stats";
};

logging {
        channel sec_file {
                file "log/bind_security.log";
#                severity dynamic;
                severity debug 3;
                print-time yes;
                print-category yes;
                print-severity yes;
        };

        category default  { sec_file; };
        category general  { sec_file; };
        category client   { sec_file;  };
        category config   { sec_file;  };
        category database { sec_file; };
        category dnssec   { sec_file;  };
        category lame-servers { sec_file; };
        category network  { sec_file; };
        category notify   { sec_file; };
        category queries  { sec_file;  };
        category resolver { sec_file;  };
        category security { sec_file;  };
        category update   { sec_file; };
        category xfer-in  { sec_file; };
        category xfer-out { sec_file;  };

};

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

zone "localhost" IN {
  type master;
  file "localhost.zone";
};

zone "0.0.127.in-addr.arpa" IN {
  type master;
  file "127.0.0.zone";
};

zone "fake.lan" IN {
        type master;
        file "zone/clients.db";
        allow-update{ 192.168.0/24; };
};

zone "0.168.192.in-addr.arpa" IN {
        type master;
        file "zone/clients.rev";
        allow-update { 192.168.0/24; };
};

=================================================

bash-3.00# cat clients.db
$ORIGIN .
$TTL 86400      ; 1 day
fake.lan                IN SOA  amd1800.fake.lan. root.amd1800.fake.lan. (
                                2005052521 ; serial
                                21600      ; refresh (6 hours)
                                3600       ; retry (1 hour)
                                69120      ; expire (19 hours 12 minutes)
                                86400      ; minimum (1 day)
                                )
                        NS      amd1800.fake.lan.
$ORIGIN fake.lan.
amd1800                 A       192.168.0.150
localhost               A       127.0.0.1

====================================================

bash-3.00# cat clients.rev
$ORIGIN .
$TTL 86400      ; 1 day
0.168.192.in-addr.arpa  IN SOA  amd1800.fake.lan. root.fake.lan. (
                                2005052521 ; serial
                                21600      ; refresh (6 hours)
                                3600       ; retry (1 hour)
                                69100      ; expire (19 hours 11 minutes 40
seconds)
                                86400      ; minimum (1 day)
                                )
                        NS      amd1800.fake.lan.
$ORIGIN 0.168.192.in-addr.arpa.
150                     PTR     amd1800.fake.lan.