Windows Forum

Ask something
Discussion Locked

DHCP

0 helpful
7 replies

by yadavshashi

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

This is the situation, AD with external DNS(Bind) internal DNS(AD integrated)which will have BIND as a forwarder. All clients will resolve via internal DNS and which is not published to out side world. DHCP Server on existing NT Server Park. Which has configured scopes (VLANs). The new AD has to use existing scopes. The Scopes setting says DNS server is BIND. If I use these scopes all the clients see BIND as DNS and that is not what I want. I do not have separate scope in existing DHCP server plus if I put new DHCP on one of the new DC than there is firewall and it won't work either.
Any suggestions?

Shashi

7 replies

by bfilmfan

The DHCP scopes have to resolve to AD's DNS. Just for the record, LDAP and DNS are INTEGRAL parts of AD.

The better ideas is to set the NT member servers into the AD forest and let them point to the AD DNS.

Have the AD server have a forwarder to the Unix server.

by beermonster

As you are unable to use an alternative dhcp server, and (presumably) any change - even at the scope level - will effect other clients, then about all you have left is a static DNS IP on the clients (or a hosts file but that would be a world of pain). Depending on the clients (win2k up) you may be able to script this using netsh ( type netsh on the command line of a client for details).

In your position though I would be agitating for some changes to the network layout. A VLAN dedicated to your clients alone would allow you to create a fresh scope and set the dns entry on that scope alone to point to your internal DNS servers.

by yadavshashi

Poster rated this answer.

What if I let AD use BIND DNS we are running version 8.2.2. What I need on BIND to support AD?

by cg it

your NT server should be patched up to the latest. What really needs to be done is create your domain with W2K/W2003 move what you need to more to over using the ADMT then dcpromo the NT to a secondary DC in an Active Directory environment.

Not all will go well either. Personally, I wouldnt muck around cuz migration from NT over to AD is fraught with problems. If your only concerned with DHCP, setup your W2K/W2003 AD domain with DHCP and configure it from scratch with the scopes you want for the VLANs you got.

Your comment of the new AD has to use the existing scopes is like "Well, ok but lot less hassel to..."

This discussion is closed to new replies.