Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
This works with no problems. I'm not going to go into too much detail on how to set this up because Google can point you to some detailed info. But the highlights are:
In /etc/dhcpd.conf, you will need ddns-updates on and ddns-domainname
In /etc/named.conf, you will need allow-update.
In both files you will need to setup a key for security purposes.
One other thing to note. I recall that when I had a Linux (RH9) DHCP client things didn't work properly. That was because the client did not send its hostname to the server. There is a configuration option to fix that, but I don't know it offhand.
i never managed to get ddns working correctly, the keys were annoying me for motnsh and i gave up. if you're after a much much lower level approach that's really easy to configure, try dnsmasq, which is a small dns server which can monitor changes in your dhcpd.leases file and server dns queries based directly on the contents (as well as external dns queries etc...) worth a go if you don;t need to full scale assault of bind,
as long as you can run it local to your dhcpd server, or have similar suitable access to the lease file yeah. I know that i should be spending even more time getting bind nailed down so hard, but i have a 4 client netowrk, and no need at all for anythign more than what dnsmasq can set up in minutes.
setup DHCP so that each computer gets the same ip each time it requests one. that way you leave out ddns altogether.
this would involve getting the MAC address from each machine which leaves some room for error but it may be a little more straight forward.