Multiple DNS suffixes in DHCP!!!

[TheMisio]

Ladies and Gents,

Quick question. IS it possible to distribute more than one DNS suffix via DHCP?
I am dealing with multidomain environment. I have set up DNS servers to host secondary zones of the other domains etc.
The problem I have is that if I log on to mydomain.local via DHCP I will get DNS suffix for mydomain.local (which is correct). But I want to be able to resolve hosts in other domains for which we host secondary zones without having to FQDNs. I know I can add the suffixes to my TCP/IP settings and it will work just fine. However, it’s not really possible in a big office. I know that In DHCP scope and / or server options I can set up the DNS suffix, but there is option for only one.

Any suggestions much appreciated.

Regards,

Michael

 

[lhuegele]

This is done with Global Policy, not DHCP. You'll put your primary DNS name under DHCP, but you'll need to use Global Policy to add the other DNS suffixes to your machines TCP/IP settings.

Good luck,

 

[chipk]

The DNS suffix in TCP/IP settings is for the current connection. What you're referring to is suffix search order, which you can push out using GPO in 2003, but you haven't stated what version of Windows you have:

http://support.microsoft.com/kb/294785.

 

[chipk]

Suffix search order is not available if he has Windows 2000.

http://support.microsoft.com/kb/275553

Although the above article says it can't be done using scripts, you can use regini or vbscript to modify the registry directly.

 

[TheMisio]

Cool.

So not really possible to do it via DHCP then?

Thanks a lot for the info.

Regards,

Michael

 

[chipk]

Well, you still haven't said what version of servers you have. There are various work-arounds, such as in the first link I posted.

 

[TheMisio]

chipk,

Currently we use Windows 2000 for DHCP. But nothing is stopping me to upgrade it to 2003.

Most of our infrastructure is 2003.

Regards,

Michael

 

[chipk]

In 2003, there are still workarounds, but there's supposed to be some configurable option, but you've still got to do some custom stuff. I'd say if there's nothing else driving an upgrade to 2003, don't make this your reason.

 

[wchull]

I beg to differ in regard to the DSSO not working in a Windows 2000 environment as I know for a fact that it does. Perhaps I have misunderstood the question but with a DSSO list applied through a group policy users can use the short name and the order in which domain are added to the DSSO will determine how addresses are reslolved. Note that you can run into problems if you have like names in two different domains.

 

[chipk]

wchull - using GPO to push out suffix search lists was pointed out in the first few responses. The question was about DHCP Server Options, which are not available without custom APIs and hacks on both workstation and server.