2 dhcpd config files only one works corectly

rbees · 06-30-2009, 10:37 AM

Ladies & Gents,

Below are two dhcpd.conf files. Both work fine with Linux and xp. With vista and xbox's on the other hand it is a different story.

File named "working" works normally with vista. The file named "Bad" however does not work with vista.

The "working" file:

Quote:

ddns-update-style interim;
ignore client-updates;
default-lease-time 21600;
max-lease-time 43200;
log-facility local7;

subnet 192.168.7.0 netmask 255.255.255.224 {
range 192.168.7.20 192.168.7.31;
option routers 192.168.7.1;
option domain-name-servers 192.168.7.1, 24.247.15.53, 24.247.24.53;
option ip-forwarding off;
}

# static addresses
host Netgear-wireless {
.
.

The "Bad" file:

Quote:

server-identifier bamod-aish;
authoritative;
ddns-update-style interim;
#include "/etc/bind/rndc.key";

zone Torah-disiple.local. {
primary 192.168.7.1;
# key "rndc-key";
}

option domain-name "Torah-disiple.local";
option domain-name-servers 192.168.7.1, 24.247.15.53, 24.247.24.53;
default-lease-time 21600;
max-lease-time 43200;
log-facility local7;

subnet 192.168.7.0 netmask 255.255.255.224 {
range 192.168.7.20 192.168.7.31;
option routers 192.168.7.1;
option ip-forwarding off;
zone 7.168.192.in-addr.arpa. {
primary bamod-aish.Torah-disiple.local;
# key "rndc-key";
}
zone Torah-disiple.local. {
primary bamod-aish.Torah-disiple.local;
# key "rndc-key";
}
}

# static addresses
host Netgear-wireless {
.
.
.

The symptoms when using the Bad file:

1 vista & xbox's do not pick up the ip assigned by the server. The log file shows repeated requests for an ip and repeated ip offers but they are not accepted or acknowledged.

2 linux & xp seam to work fine.

3 if vista & xbox are set to a static ip in the correct range they seam to work fine.

Server & network info:

server is a base install of Debian Lenny no gui & fully up-to-date and has been harden to the best of my current ability with a reasonable complement of intrusion detection software installed. It is using Arno's firewall script.

network is cable-modem > server > various switches & wireless access point > computers (wireless & cat5)

The server has been moved from my testing network to it's current position as my main dhcp/firewall/nat/dns server. Before the migration the main network was working correctly.

Using webmin reports no problems with the "Bad" config file.

There is a secondary issue in that local name resolution is not working. But I think I need to get the dhcp issue fixed first. I have corrected a domain name spelling issue in one of the zone declarations (reflected above) that may have fixed the resolution issue but it has not been tested yet.

What could be causing this problem?

Thanks for any insight you can give me.

rbees · 07-02-2009, 04:15 PM

After spendig some time reading the man page and examining my file I made a few changes to it. I am not sure what I changed that made the difference but the file below is working.

It would sure be nice if someone could enlighten me as to why this one works with vista and the other one in my previous post dosen't.

I precieve that the most important change I made is moving the static host declarations into the subnet.

Code:

server-name bamod-aish;
authoritative;
ddns-update-style interim;
option domain-name "Torah-disiple.local";
option domain-name-servers 192.168.7.1, 24.247.15.53, 24.247.24.53;
default-lease-time 21600;
max-lease-time 43200;
log-facility local7;

zone Torah-disiple.local. {
	primary 127.0.0.1;
}

subnet 192.168.7.0 netmask 255.255.255.224 {
	range 192.168.7.20 192.168.7.31;
	option routers 192.168.7.1;
	option ip-forwarding off;
	zone 7.168.192.in-addr.arpa. {
		primary bamod-aish.Torah-disiple.local;
	}
	zone	Torah-disiple.local. {
		primary bamod-aish.Torah-disiple.local;
	}

# static addresses
	host Netgear-wireless {
.
.
.

Thanks and I hope someone is helped by this info.