DHCP "no answer" on CentOS 6.4

Posted by Kev on Server Fault See other posts from Server Fault or by Kev
Published on 2013-10-24T23:03:56Z Indexed on 2013/10/25 3:58 UTC
Read the original article Hit count: 731

Filed under:
|
|
|

I installed a DHCP server (yum install dhcp) and this is my conf:

# create new
# specify domain name
option domain-name "mydomain.name";

# specify DNS's hostname or IP address
option domain-name-servers 10.0.1.1, 10.0.1.2;
option ntp-servers 10.0.1.1, 10.0.1.2;

allow unknown-clients;

# default lease time
default-lease-time 2628000;

# max lease time
max-lease-time 2628000; # about a month

# this DHCP server to be declared valid
authoritative;

# specify network address and subnet mask
subnet 10.0.0.0 netmask 255.0.0.0 {

        # specify the range of lease IP address
        range dynamic-bootp 10.0.2.1 10.0.2.50;

        # specify broadcast address
        option broadcast-address 10.255.255.255;

        # specify default gateway
        option routers 10.0.0.1;

        allow unknown-clients;

}

service dhcp start reports [ OK ]. Yet, if I disable my other DHCP server (Win2k3) and get a client to try renewing its IP lease, it times out.

So I installed dhcping. No matter what options I try, including directing dhcping at my server, adding a client address in the range, adding my hardware address, it replies 'no answer'. I'm also trying -i since that seems to be more akin to what a WinXP client would try to do, based on /var/log/messages. It logs the attempts (from dhcping here) as:

Oct 24 18:55:13 newdc dhcpd: DHCPINFORM from 10.0.2.15 via eth0:4
Oct 24 18:55:13 newdc dhcpd: DHCPACK to 10.0.2.15 (00:11:25:66:4e:7f) via eth0:4
Oct 24 18:55:13 newdc dhcpd: DHCPINFORM from 10.0.2.15 via eth0:3
Oct 24 18:55:13 newdc dhcpd: DHCPACK to 10.0.2.15 (00:11:25:66:4e:7f) via eth0:3
Oct 24 18:55:13 newdc dhcpd: DHCPINFORM from 10.0.2.15 via eth0
Oct 24 18:55:13 newdc dhcpd: DHCPACK to 10.0.2.15 (00:11:25:66:4e:7f) via eth0

The :3 and :4 are because I have a few extra Host(A) records for this server so it responds on more than one IP for our intranet app.

No answer? It sounds like it should be getting three answers...no? (And if that's the problem, how do I limit the DHCP service to replying from eth0?)

© Server Fault or respective owner

Related posts about centos

Related posts about centos6