LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Server (http://www.linuxquestions.org/questions/linux-server-73/)
-   -   dhcpd can't do dns lookups? (http://www.linuxquestions.org/questions/linux-server-73/dhcpd-cant-do-dns-lookups-942173/)

dafydd2277 04-27-2012 06:42 PM

dhcpd can't do dns lookups?
 
Here's an odd one...

First, for those who don't know, dhcpd.conf has a keyword called "fixed-address" that allows administrators to assign specific IP addresses to specific MAC addresses. With this, we don't have to configure address pools. Along with other keywords (including "host," here), all hostname and network information can be kept in a central location for pickup by the individual hosts via DHCP. In Enterprise-sized networks, this is a huge time saver. Also, according to the dhcpd.conf man page, "[e]ach address in the fixed-address declaration should be either an IP address or a domain name that resolves to one or more IP addresses."

So, what I have is a bunch of entries like this:
Code:

host wrkstn01.q.d.n {hardware ethernet 01:02:03:04:05:ff; fixed-address workstn01.q.d.n;}
and I can do forward and reverse "host" and "nslookup" commands against workstn01.q.d.n and its IP address all day long.

However, dhcpd appears to be unable to resolve the hostname. So, I'll get
Code:

dhcpd: DHCPDISCOVER from 01:02:03:04:05:ff via eth0: network 192.168.15/24: no free leases
If I substitute, say, 192.168.15.1 in the "fixed-address" statement, dhcpd will serve the information up just fine.

Weird, huh? I've verified spelling in dhcpd.conf and in the zone files. As I mentioned, I can do command-line lookups all day long. The only problem appears to be that dhcpd can't resolve the host name.

What'm I missing?

dafydd


All times are GMT -5. The time now is 06:32 AM.