In message <3EC7BD29.1080301@unassemble.co.uk>, Lee W writes:
>Steven M. Bellovin wrote:
>
>  > You could always run your own nameserver -- there's a lot to be said
>> for that.
>> 
>> But make sure you have a line like this in your dhclient.conf file:
>> 
>> 	request subnet-mask, broadcast-address, routers, domain-name, domain-na
>me-servers;
>> 
>> 
>> You could even say
>> 
>> 	require domain-name-servers;
>> 
>> to make it abort if it doesn't get any.
>> 
>
>In a larger environment setting up my own DNS server would be a good 
>suggestion unfortunately I am only setting this up a home.

So?  That's not a reason not to run one; I often do even on my laptop.
>
>I had another look at the dhclient.conf man page and it says that no 
>options "should" be required, a blank file will do.
>
>Also the dhclient.leases file contains all the correct information (i.e. 
>name server ip's) it just appears as though the script is ignoring them 
>or forgetting to configure resolv.conf.
>
Hmm -- no suggestions on that one.

		--Steve Bellovin, http://www.research.att.com/~smb (me)
		http://www.wilyhacker.com (2nd edition of "Firewalls" book)