Acutally, I asked the wrong question. I do want my Microsoft DHCP
server to overwrite the resolv.conf, but with the 3 dns suffixes, not
just one. Right now it is only writing a single domain on the search
line which requires editting by the user every day.

Here is the desired resov.conf;
[root@lt-dpc1 etc]# more resolv.conf
; generated by /sbin/dhclient-script
search foo.bar.com next.domain.com another.domain.com
nameserver 192.168.12.60
nameserver 192.168.12.62

Here is what the DHCP server is writing to the Linux clients;
[root@lt-dpc1 etc]# more resolv.conf
; generated by /sbin/dhclient-script
search foo.bar.com
nameserver 192.168.12.60
nameserver 192.168.12.62

Does anyone know how to pass the right search string to the Linux host
with a Microsoft DHCP server (Windows Server 2003)

-Nathan



unruh@string.physics.ubc.ca (Bill Unruh) wrote in message news:<cmeu0q$c11$1@nntp.itservices.ubc.ca>...
> nathan.spear@iovation.com (Nathan Spear) writes:
>
> ]I am managing a network consisting of Windows and Linux clients. We
> ]have three dns suffixes that need to be used during name resolution.
> ]For the Microsoft clients using Group Policy works great. The problem
> ]I am having is with the Linux clients. Every time a machine gets a
> ]new DHCP lease the resolve.conf gets clobbered, requiring the user to
> ]edit the file again to add the proper dns suffixes.
>
> ]Does anyone know a way around this? Is there a way to prevent a
> ]Microsoft DHCP server from overwriting a Linux resolve.conf file?
>
> A) Put the correct resolver in the DHCP servers so they deliver the right
> addresses.
> b) Tell linux not to request or honour resolvers.
>
> Either or both of the above would solve your problem.
>
> Eg, for B
> man dhcpcd
> -R Prevents dhcpcd from replacing existing /etc/resolv.conf file.