The bit you are interested in here is the Listen Addresses, the image above is from a site where I have corrected this issue already.When I joined the company, I noted that a lot of name lookups were failing or pointing at the wrong machines.This user account only needs limited privileges, it must be a member of DNSAdmins, DNSUpdate Proxy, DHCP Users and DHCP Administrators.While you are on this tab, its worth setting the conflict resolution attempts to 3 or 4 which gives DHCP the opportunity to resolve any issues itself.Also ensure that reverse lookups are in place, and that permissions are correct on these too.
what i basically want to put you in perspective, is to have all the pc's in my home network (desktops and laptops) regardless of any other settings, to send their computer name (hstname basically) to the dhcpd (during the handshake)...
I also noted a staggering amount of old, outdated DNS records.
Scavenging appeared to be configured, but not actually working.
i take it that during handshake, the laptop will send its hostname (i don't know what that will be for win XP and win7 dhcp clients, but i presume it will send the output of command 'hostname' for linux clients - or at least thats what i would like it to send....)"nass-notebook" Then the server will append "" and it will update the DNS with an entry looking like "nass-notebook." corresponding to some ip address... for example my dhcpd.leases file contains these entries: the 1st (192.168.0.109) is definitely a fedora laptop.. it seems that since the dhcp server can get "nasslaptop" to work as i have in mind... it also feels that differences in dhcp client configurations causes all this fuss (? is it possible to just get the server to arrange fqdn's for the clients, by just getting the hostname out of the clients and doing the rest of the work , server-side?? i have attached my for your reference: authoritative; server-name "stardust.nebula.org"; option domain-name "nebula.org"; option domain-name-servers 192.168.0.19, 192.168.0.6; option routers 192.168.0.19; option netbios-name-servers 192.168.0.6; #WINS option netbios-dd-server 192.168.0.6; #SMB option netbios-scope ""; option netbios-node-type 8; default-lease-time 21600; max-lease-time 43200; include "/etc/rndc.key"; ddns-update-style interim; ddns-domainname "nebula.org"; ddns-hostname = pick(option fqdn.fqdn,option fqdn.hostname,option host-name,concat ("dhcp-",binary-to-ascii(10, 8, "-", leased-address))); allow client-updates; zone subnet 192.168.0.0 netmask 255.255.255.0 groupdhcp and bind are separate animals.
and as i see it has got a client-hostname entry as "fedorahost.";... i mean the hostname of the fedora laptop is "fedorahost".... dhcp is for assigning dynamic ip addresses bind is for binding domain names to static ip addresses.