Dhcp not updating dns records
You should specify a regular Active Directory user with no special privileges, but the password should be set to never expire (or you should have a really good process to update it periodically! You would then specify this configuration on all DHCP servers so that all DHCP servers use the same account to perform DNS updates.This means all DNS records registered by the DHCP servers would be owned by the specified account that is common to all DHCP servers. Note that registered members see fewer ads, and Content Link is completely disabled once you log in. Visit the following links: Site Howto | Site FAQ | Sitemap | Register Now If you have any problems with the registration process or your account login, please contact us. This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter. Please visit this page to clear all LQ-related cookies.
nass: from what I read it seems that dhcpd is adding A and PTR records for some of the hosts and not others.Just admit you were wrong and you didn't know what you were talking about.The ability to write dynamic dns records to bind is a feature of dhcpd.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.