New Zone

Mike

New to DNS. Would like to separate LAN (PC's and laptops) side from server
(servers, ilo devices, printers) side into two different Forward Lookup
zones. Currently running 2003 sp2 ADI DNS. Also running DDNS, but what
changes do I need to make so devices register their records in the new zone?

Mike

Danny Sanders

If I'm following you right this is not a good idea. AD Domain controllers
MUST register their SRV records in the same DNS zone the AD clients look to.
Creating another zone for the DNS records for your servers will cause long
login delays, Group policy won't work and all sorts of other problems.

Why not use the best practices for AD DNS servers? It does not mention
separating the servers and the clients into separate DNS zones. Not sure
what you are trying to accomplish but this is not the way to do it.

See:
Setting Up the Domain Name System for Active Directory

http://support.microsoft.com/default...b;en-us;237675
Best Practices for DNS Client settings in Windows 2000 server and in Windows
Server 2003

http://support.microsoft.com/default...b;en-us;825036

How to configure DNS for Internet access in Windows Server 2003

http://support.microsoft.com/default...b;en-us;323380





hth

DDS


"Mike" <Mike@discussions.microsoft.com> wrote in message
news:1D1056EA-E54E-42D3-883C-49D8F110CA60@microsoft.com...
> New to DNS. Would like to separate LAN (PC's and laptops) side from
> server
> (servers, ilo devices, printers) side into two different Forward Lookup
> zones. Currently running 2003 sp2 ADI DNS. Also running DDNS, but what
> changes do I need to make so devices register their records in the new
> zone?
>
> Mike
>
>

Mike

Herb,

Sorry, as I was not very clear on my original post. We have a single domain
(xyz.com). What we are trying to accomplish is to create a separate zone for
specific devices to register their A records, i.e: ilo.xyz.com or
VOIP.xyz.com, etc. I know this can be controlled from the client by
specifying the "DNS suffix for this connection". One of the goals was for
scavenging purposes. This way we can specify which zone to scavenge though I
recommended to management to configure the DHCP servers to handle DNS
registration instead of the client. Second goal was more for organizational
purposes, we know what zone is for pc's, ip phones, servers, etc. Not sure
if there is anything to gain by doing this.

Appreciate your comments,

Mike


"Herb Martin" wrote:

>
> "Mike" <Mike@discussions.microsoft.com> wrote in message
> news:1D1056EA-E54E-42D3-883C-49D8F110CA60@microsoft.com...
> > New to DNS. Would like to separate LAN (PC's and laptops) side from
> > server
> > (servers, ilo devices, printers) side into two different Forward Lookup
> > zones. Currently running 2003 sp2 ADI DNS. Also running DDNS, but what
> > changes do I need to make so devices register their records in the new
> > zone?
>
> If these machines are all in the same domain (and that is the only
> way your paragraph makes sense) then it would be either
> impossible to separate them or EXTREMELY unusual and
> weird.
>
> Don't do it.
>
> WHY do you wish to do this?
>
> Explain your REAL GOAL and we might be able to solve that
> real problem for you....
>
>
>

Danny Sanders

After further explanation, it's still not a good idea. You will be creating
a situation where you are not using best practices and the results will, at
least break, the way AD works.
I would suggest thinking about why you want to change this. There really is
nothing to gain.


hth
DDS

"Mike" <Mike@discussions.microsoft.com> wrote in message
news:2A6A325E-D1E2-4FCC-989D-2D8EE7E73A43@microsoft.com...
> Herb,
>
> Sorry, as I was not very clear on my original post. We have a single
> domain
> (xyz.com). What we are trying to accomplish is to create a separate zone
> for
> specific devices to register their A records, i.e: ilo.xyz.com or
> VOIP.xyz.com, etc. I know this can be controlled from the client by
> specifying the "DNS suffix for this connection". One of the goals was for
> scavenging purposes. This way we can specify which zone to scavenge
> though I
> recommended to management to configure the DHCP servers to handle DNS
> registration instead of the client. Second goal was more for
> organizational
> purposes, we know what zone is for pc's, ip phones, servers, etc. Not
> sure
> if there is anything to gain by doing this.
>
> Appreciate your comments,
>
> Mike
>
>
> "Herb Martin" wrote:
>
>>
>> "Mike" <Mike@discussions.microsoft.com> wrote in message
>> news:1D1056EA-E54E-42D3-883C-49D8F110CA60@microsoft.com...
>> > New to DNS. Would like to separate LAN (PC's and laptops) side from
>> > server
>> > (servers, ilo devices, printers) side into two different Forward Lookup
>> > zones. Currently running 2003 sp2 ADI DNS. Also running DDNS, but
>> > what
>> > changes do I need to make so devices register their records in the new
>> > zone?
>>
>> If these machines are all in the same domain (and that is the only
>> way your paragraph makes sense) then it would be either
>> impossible to separate them or EXTREMELY unusual and
>> weird.
>>
>> Don't do it.
>>
>> WHY do you wish to do this?
>>
>> Explain your REAL GOAL and we might be able to solve that
>> real problem for you....
>>
>>
>>