Dhcp not updating dns server

These are now limited to our own internal network, LAN.The forwarders section, where your DNS server asks to lookup IP addrerss for hosts it does not know. I’m using 10.1.200.1 which in the one on my lab-router.It will point out where you missed off those pesky full stops. The NIC on the DNS server should be setup to look only at localhost, 127.0.0.1.

Not sure why the guys in China are so interested in hacking my servers.

You can now use the name internals in the three sections for allow-query, allow-recursion and allow-transfer.

Now boot up another machine which will use the DHCP service we have created.

As it boots the output in syslog should look similar to the following: You should see, in order, DHCPDISCOVER, DHCPOFFER followed by a line saying it is “updating zone ‘dragon…” and then some lines with DHCPREQUEST, DHCPACK and “Added new forward map” If you do, you are all done! I Bet you are glad you grabbed that swift coffee right at the beginning.

Say we have a machine called desktop1 which has an IP address of 10.1.200.20 we can use the following: /var/lib/bind/zone We should be able to start or restart our DNS server now.

Remember to check the error/warning output in your /var/log/syslog.

Add your changes to the files which are included or to those included further down the branches. // This is the primary configuration file for the BIND DNS server named. for information on the // structure of BIND configuration files in Debian, *BEFORE* you customize // this configuration file.

// // If you are just adding zones, please do that in /etc/bind/local include "/etc/bind/options"; include "/etc/bind/local"; include "/etc/bind/default-zones"; Add the section for “acl internals ”, and update the commented out section for forwarders. It will stop the scum bags in China using your DNS.

Remember we used the Google DNS or Open DNS in the local file as our forwarder so your lab-dns-dhcp server will look there if it cannot find an answer from bind.

The man pages for all of them are a good source of information and their command line switches.

Try using dig to find the IP of your dhcp enabled machine and then do a reverse lookup on that IP. If not you missed something out, I found it was usually missing semicolons or permissions not being set correctly or a pesky missing full stop. 🙂 If you are setting up a DNS and DHCP server you will also need a NTP server to synchronise the clocks on the PC’s connected to your LAN.

Comments are closed.