dhcpd assigns address, but DNS resolvers and ping fail

[Lowell Gilbert]

David Benfell <benfell at parts-unknown.org> writes:

> Another in my mysterious problems list...
>
> pf.conf is set up to allow icmp anywhere.  And dhcpd offers a
> plausible IP address and gateway that the client (tested under
> both Linux and Windows) accepts.
>
> The client doesn't get the DNS resolver information and can't
> ping anywhere, even by raw IP address, even to the router.  The
> router also fails to ping the client.
>
> This is FreeBSD stable, updated about a week ago.  dhcpd.conf
> and pf.conf files are attached.
>
> Any ideas?  Thanks!
> -- 
> David Benfell, LCP
> benfell at parts-unknown.org
> ---
> Resume available at http://www.parts-unknown.org/
> NOTE: I sign all messages with GnuPG (0DD1D1E3).
>
>
> #	$OpenBSD: dhcpd.conf,v 1.1 1998/08/19 04:25:45 form Exp $
> #
> # DHCP server options.
> # See dhcpd.conf(5) and dhcpd(8) for more information.
> #
>
> # Network:		192.168.20.0/255.255.255.0
> # Domain name:		cybernude.org
> # Name servers:		192.168.19.4
> # Default router:	192.168.17.1
> # Addresses:		192.168.20.2 - 192.168.20.254
> #
> shared-network LOCAL-NET {
> 	option  domain-name "cybernude.org";
> 	option  domain-name-servers 192.168.18.31, 192.168.19.130, 64.81.79.2, 216.231.41.2;
>
> 	subnet 192.168.17.0 netmask 255.255.255.0 {
> 		option routers 192.168.17.1;
> 	}
> 	subnet 192.168.20.0 netmask 255.255.255.0 {
> 		option routers 192.168.20.1;
> 		range 192.168.20.2 192.168.20.254;
> 	}
> }
>
> #domain cybernude.org
> #nameserver 192.168.19.130
> #nameserver 192.168.18.31
> #nameserver 64.81.79.2
> #nameserver 216.231.41.2
>
> #shared-network LUPIN {
> 	#option  domain-name "cybernude.org";
> 	#option  domain-name-servers 192.168.18.31;
>
> 	#subnet 192.168.100.0 netmask 255.255.255.0 {
> 		#option routers 192.168.100.1;
> 		#range 192.168.100.100 192.168.100.200;
> 	#}
> #}
> ddns-update-style ad-hoc;
>

Yeah, offhand it looks like it *should* work. 
Fairly complicated setup; make sure you really need those
shared-networks if you're using them.
Have you tried putting the domain-name-servers entries
at the subnet or global scope?