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.
I have been using a RedHat 9 machine as both the DHCP server and name server (named) for my home network. I had 5 Windows machines and the one Redhat machine on the network with names such as: Neumyer001, Neumyer002, Neumyer003, etc. They all worked fine, and were available for lookup in the nameserver as:
I can refer to them as neumyer001 or neumyer001.neumyer.com and everything works fine.
Now... I have recently installed Fedora Core 2 on Neumyer003 (it was formerly one of the windows machines). Now it successfully acquires an IP address from the DHCP server, *but* it ends up being listed in the nameserver like this:
If I try to ping neumyer003 or neumyer003.neumyer.com, it fails.
If I ping neumyer003.neumyer.com.neumyer.com, it is successful.
I have temporarily worked around this problem by giving Neumyer003 a static IP, and manually updating my zone files. However, I'd really prefer to have it use a dynamic IP via dhcp
Any dhcpd and/or named gurus out there that know what the problem is/was?
Distribution: SuSE Linux Open/Enterprise, Red Hat, Ubuntu
Make sure that it is set to get an automatic IP address. Sometimes when im using FC2 on my network it tells me that it recieved it DHCP information successfully when it boots but im not able to ping anything. (I get my host name,IP address,etc.) Try that first and post if you can't solve the problem.
while not being a 'guru' of much of anything I recognize that problem as having to do with a missing '.' from the end of a FQDN somewhere in your configuration. Try setting the hostname for the FC2 client machine to just neumyer003 with nothing after it (couldn't you come up with some sort of cutesy nicknames for your hosts instead?)
Now, can you tell me how you got dhcpd to update DNS? I can't make that work for the life of me...