dns suffix search list

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

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

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

AFAIK, option 119 is not available in W2K DHCP.

This KB might be helpful to you.

How to Configure a Domain Suffix Search List on the Domain Name System Clients
http://support.microsoft.com/default.aspx?scid=275553

BR,
Denis

"Nathan Spear" wrote:

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

 

[lee]

Archived from groups: microsoft.public.win2000.dns (More info?)

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

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

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

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

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

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

Let me try and ask this question again, in a different way.

Currently my Microsoft DHCP server is overwriting the resolv.conf file
on the Linux hosts, but with only one dns suffix, not the three my
environment requires.

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

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

In news:af24b459.0411091327.4e6b6ee7@posting.google.com,
Nathan Spear <nathan.spear@iovation.com> commented
Then Kevin replied below:
> Let me try and ask this question again, in a different
> way.
>
> Currently my Microsoft DHCP server is overwriting the
> resolv.conf file on the Linux hosts, but with only one
> dns suffix, not the three my environment requires.
>
> 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

DNS suffix search list are not included in Microsoft DCHP, currently MS DHCP
can only publish a Connection DNS suffix which is added to the DNS Suffix
search list.

--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
<p><br>
</p>
<blockquote type="cite"
cite="midaf24b459.0411091327.4e6b6ee7@posting.google.com">
<p>Currently my Microsoft DHCP server is overwriting the <code>resolv.conf</code>
file on the Linux hosts, </p>
</blockquote>
<p>False.  <em>The DHCP clients</em> on your Linuxen are overwriting
the <code>resolv.conf</code> files on those machines.  Understand
that, and the rest will follow.<br>
</p>
</body>
</html>