RE: design help

Tech-Archive recommends: Fix windows errors by optimizing your registry

Ryan,
Thanks for the reply.
I have set up the sites and the subnets.
I think I may have messed something up though.
I installed and configured DNS on the first machine, then promoted it to a DC.
Next I set up the second subnet and got a little confused about the DNS. So,
rather than setting the primary DNS server to AD integrated, I set the
machine in the second subnet to a secondary DNS server then promoted to a DC.
Now, I think I want to run integrated, so what are my options?
Do I demote the second DC, uninstall DNS, set the primary DNS server to
integrated, then re-promote the second subnet's DC then install DNS on it?
Or can I simply set both the primary and secondary DNS server to integrated
and be good?

Thanks,
David

"Ryan Hanisco" wrote:

Hi DWL,

This sounds like a fine plan. You generally only want to have additional
domains if you have a really good reason to introduce the additional overhead
and maintenance burden. It doesn't sound like you need more than one. Other
than that, make sure you have declared all of your subnets and mapped them to
sites and you should be good. You'll also want to be sure to have a GC in
each site, but with the size of your domain, I don't see a reason not to make
all of them GCs.

Cheers,
--
Ryan Hanisco
MCSE, MCTS: SQL 2005, Project+
http://www.techsterity.com
Chicago, IL

Remember: Marking helpful answers helps everyone find the info they need
quickly.


"DWL" wrote:

Hi all,
I have a small environment with 2 locations. Location 1, call it
headquarters (HQ) and location 2, call it production (prod).
In HQ, I plan to have 2 DC's and member servers running Exchange, IIS, etc.
In prod, I plan to also have 2 DC's and member servers running Exchange,
IIS, SQL, etc.
I wish to have all 4 DC's running DNS, and 1 DC at each site also running
DHCP.

I wish to have only 1 AD domain, MyCompany. I do not want to have subdomains
for HQ or Prod. HQ and prod will have different subnets.
I assume that I can set up different sites and subnets in AD Sites and
Domains.

First of all, is this a reasonable plan? Are there any problems with not
having sub-domains? Advantaegs? Disadvantages?
Assuming this is an OK plan, how does one go about setting up the DNS for
this?
I have the first DC (for HQ) set up and running DNS and DHCP. I wish to set
up the first DC at the Prod site right now. Do I configure it's DNS server as
a secondary zone administrator, then install AD?

Thanks,
David



.

Relevant Pages

  • Re: No browsing No domain?
    ... One of our genius admins decided to study DNS by building a DNS server on ... You need NetBIOS resolution for Browsing to work correctly ... Because you have two subnets; Network Places uses the Computer Browser ...
    (microsoft.public.windows.server.dns)
  • Re: slow login problems at branch office
    ... Make Sure that each Dns server only points to itself under Nic properties. ... If your between subnets, and you use NetBIOS resolution (for example to ... SP4 machines and based in the main site. ...
    (microsoft.public.win2000.active_directory)
  • Re: Yet another multisite VPN DNS question!
    ... Just create each site and determine which subnets are associated with the ... Both DC have their IP's properly listed in DNS. ... When running netdiag on both servers, ... Are all the clients using only the DC's as their DNS Server? ...
    (microsoft.public.windows.server.dns)
  • Re: GPO Loosing Settings
    ... Then i will asked the other way around, where is this DNS server coming from 192.168.2.8? ... I am a bit confused about the subnets you are using on the 2 machines ...
    (microsoft.public.windows.server.active_directory)
  • Re: dns issues
    ... >> DNS is still on the other DC. ... > both DCs and AD replication will handle the zone data. ... > instead of the FQDN across your subnets. ... > Microsoft Windows MVP - Active Directory ...
    (microsoft.public.win2000.dns)