You just replaced a computer; the old computer is off the network and had held the DHCP IP address of 192.168.0.10.You bring the new computer online and it obtains a DHCP lease for the same IP address. However, when you try to resolve the name of the new computer, the old computer's name still comes up. Here's how we'll start the troubleshooting process: 1.(Obtained as is from: The steps in this post shows how to configure the DHCP server to automatically update the DNS records when giving out a new lease to a client computer.Before continuing These steps assumes that you already have a working copy of dhcp3-server and bind9 installed.
The term is used to describe two different concepts.
option domain-name "home.lan"; option domain-name-servers lan; default-lease-time 600; max-lease-time 7200; # If this DHCP server is the official DHCP server for the local # network, the authoritative directive should be uncommented. Some people have mentioned that they think that bind messes up these files so that they are impossible to maintain.
authoritative; # Use this to send dhcp log messages to a different log file (you also # have to hack to complete the redirection). I don’t think that they are that bad and personally I don’t have any problem editing them after that bind has rewritten them.
The first is "dynamic DNS updating" which refers to systems that are used to update traditional DNS records without manual editing.
These mechanisms are explained in RFC 2136, and use the TSIG mechanism to provide security.