resolve.conf clobbered by DHCP

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?

-Nathan

On 4 Nov 2004 15:38:53 -0800, Nathan Spear wrote:
>
> Is there a way to prevent a
> Microsoft DHCP server from overwriting a Linux resolve.conf file?

Over 190+ linuxes.
Please read http://www.catb.org/~esr/faqs/smart-questions.html
Always provde distribution and release level when posting questions.
It could help you get better answers.

add PEERDNS=no to /etc/sysconfig/network-scripts/ifcfg-ethX if Mandrake
9.x or 10.x where ethX is you interface to lan.

Nathan Spear wrote:

> 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?

When setting up the NIC in Yast, there's an option to update name servers
etc., via dhcp. Is that turned off?

--

(This space intentionally left blank)

(E-Mail Removed) (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.

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



(E-Mail Removed) (Bill Unruh) wrote in message news:<cmeu0q$c11$(E-Mail Removed)>...
> (E-Mail Removed) (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.

(E-Mail Removed) (Nathan Spear) writes:

]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.

Why? All that search line does is be used if you hand it a single name.
ping bloggs
will put those three names after bloggs and go to the dns server to ask for those names. Now why do you want it to do that?


]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)

(E-Mail Removed) (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?
>
> -Nathan

Not putting the search string in from DHCP, but if hard coding it on
the linux box is acceptable then, on Fedora Core 2 in file
/etc/sysconfig/network-scripts/ifcfg-ethX (where X is your interface )
add at the end:
SEARCH="dns.suffix.one dns.suffix.two etc"

That file is read by /sbin/dhclient-script which generates /etc/resolv.conf

Then run:
/sbin/ifup eth0

to regenerate resolv.conf

--
Giles Chamberlin