Re: dns suffix search list
From: Nathan Spear (nathan.spear_at_iovation.com)
Date: 11/04/04
- Next message: Lee: "Re: joining a W2k Pro system to a W2k Server domain"
- Previous message: diveman75: "Re: joining a W2k Pro system to a W2k Server domain"
- Next in thread: Nathan Spear: "Re: dns suffix search list"
- Reply: Nathan Spear: "Re: dns suffix search list"
- Messages sorted by: [ date ] [ thread ]
Date: 4 Nov 2004 15:36:17 -0800
Looks like I don't have a solution yet. Using the Group Policy works
great for the Windows clients. Problem is with the Linux clients
every time a machine gets a new 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
nathan.spear@iovation.com (Nathan Spear) wrote in message news:<af24b459.0410211033.7e9e9dc0@posting.google.com>...
> Lee,
>
> My solution is to use group policy for the Windows clients and we will
> have to edit resolve.conf on the linux workstations.
>
> -Nathan
>
> "Lee" <leweb2000@hotmail.com> wrote in message news:<ughOzkxtEHA.3200@TK2MSFTNGP14.phx.gbl>...
> > I just found something by accident. If DHCP is issuing the domain name AND
> > append primary and connection specific dns suffixes is selected in the NIC
> > properties AND connection specific dns is set it has the effect of adding
> > two domains to the dns searchlist. The connection specific domain and the
> > dhcp domain issued are merged to create the searchlist. I guess this is how
> > your clients had dual domains in the searchlist.
> >
> > Lee
> >
> > "Nathan Spear" <nathan.spear@iovation.com> wrote in message
> > news:af24b459.0410171959.852ff9b@posting.google.com...
> > > Before I brought up two new domain controllers and removed the two old
> > > domain controllers my cleints had 3 suffixes listed in their ipconfig
> > > /all output.
> > >
> > > I have read all over the web that this can not be done by the DHCP
> > > server, but I think that is not true. I recall a conversation that
> > > adding an option 119 to the DHCP sever serves this purpose, however it
> > > no longer works.
> > >
> > > My question is how did my network have these 3 domain suffixes served
> > > up? What other services or devices could do it? How is this done is
> > > a hetrogenous environment (windows and linux)? (the solution can't be
> > > group policy since linux hosts don't listen to that)
> > >
> > > I found a post about option 135 but haven't found more info to lead me
> > > down that path. Perhaps there is another DHCP option I can use.
> > >
> > > thanks for your thoughts.
> > >
> > > Nathan Spear
> > > Network Administrator
> > > iovation, Inc.
> > > nathan.spear@iovation.com
- Next message: Lee: "Re: joining a W2k Pro system to a W2k Server domain"
- Previous message: diveman75: "Re: joining a W2k Pro system to a W2k Server domain"
- Next in thread: Nathan Spear: "Re: dns suffix search list"
- Reply: Nathan Spear: "Re: dns suffix search list"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|