|
|
|
|
||||||
![]() |
|
|
LinkBack | Outils de la discussion |
|
|
#1 |
|
Messages: n/a
Hébergeur: |
Hi
Just recently started a new job and the company I am working at has 2 DC's for robustness but only one has DNS running. We have no other DNS server on site so my question is what do I need to configure DNS on the second DC and is there a resource that can walk me through this? Cheers for any replies GD |
|
|
|
#2 |
|
Messages: n/a
Hébergeur: |
Check that the first DC has an active-directory integrated zone.
Check that each DC is using the first DC as its primary DNS, and the second DC as its secondary DNS. Install DNS on the second DC. Configure your forwarder to your ISP, same as on the first. The integrated zone will create itself in the forward lookup zones. Anthony "Sean" <sean@ghostydog.com> wrote in message news:uoR4OzBzGHA.2300@TK2MSFTNGP05.phx.gbl... > Hi > > Just recently started a new job and the company I am working at has 2 DC's > for robustness but only one has DNS running. We have no other DNS server > on site so my question is what do I need to configure DNS on the second DC > and is there a resource that can walk me through this? > > Cheers for any replies > > GD > |
|
|
|
#3 |
|
Messages: n/a
Hébergeur: |
Great stuff,
Just what I wanted, thanks for that Anthony. )Sean "Anthony" <anthony.spam@spammedout.com> wrote in message news:e1UxgVCzGHA.996@TK2MSFTNGP03.phx.gbl... > Check that the first DC has an active-directory integrated zone. > Check that each DC is using the first DC as its primary DNS, and the > second DC as its secondary DNS. > Install DNS on the second DC. Configure your forwarder to your ISP, same > as on the first. > The integrated zone will create itself in the forward lookup zones. > Anthony > > > > > "Sean" <sean@ghostydog.com> wrote in message > news:uoR4OzBzGHA.2300@TK2MSFTNGP05.phx.gbl... >> Hi >> >> Just recently started a new job and the company I am working at has 2 >> DC's for robustness but only one has DNS running. We have no other DNS >> server on site so my question is what do I need to configure DNS on the >> second DC and is there a resource that can walk me through this? >> >> Cheers for any replies >> >> GD >> > > |
|
|
|
#4 |
|
Messages: n/a
Hébergeur: |
None for continued performance, but fine for protecting
the important AD info. <grin> "Sean" <sean@ghostydog.com> wrote in message news:uoR4OzBzGHA.2300@TK2MSFTNGP05.phx.gbl... > Hi > > Just recently started a new job and the company I am working at has 2 DC's > for robustness but only one has DNS running. We have no other DNS server > on site so my question is what do I need to configure DNS on the second DC > and is there a resource that can walk me through this? Yes.... If the first DNS server is a "standard Primary" make it an AD Integrated DNS server first. (Check replication with DCDiag before proceeding.) Just install the DNS service on the second DC. The zone should appear automatically since you have AD integrated DNS and full replication. Change all of your clients to use the second DNS server as either "Alternate" (or even some of them as "Preferred" if you have enough to care about load balancing.) Might as well make the second a GC also. (Global Catalog Server in Sites and Services.) > Cheers for any replies Below are my general thoughts that I usually send to people who are having DNS problems -- some of this might you too.... DNS for AD 1) Dynamic for the zone supporting AD 2) All internal DNS clients NIC\IP properties must specify SOLELY that internal, dynamic DNS server (set.) 3) DCs and even DNS servers are DNS clients too -- see #2 4) If you have more than one Domain, every DNS server must be able to resolve ALL domains (either directly or indirectly) netdiag /fix ....or maybe: dcdiag /fix (Win2003 can do this from Support tools): nltest /dsregdns /server C-ServerNameGoesHerehttp://support.microsoft.com/kb/q260371/ Ensure that DNS zones/domains are fully replicated to all DNS servers for that (internal) zone/domain. Also useful may be running DCDiag on each DC, sending the output to a text file, and searching for FAIL, ERROR, WARN. Single Label domain zone names are a problem Google: [ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ] -- Herb Martin, MCSE, MVP Accelerated MCSE http://www.LearnQuick.Com [phone number on web site] |
|
|
|
#5 |
|
Messages: n/a
Hébergeur: |
Its a pleasure, glad to ,
Anthony "Sean" <sean@ghostydog.com> wrote in message news:eMBsTfDzGHA.4092@TK2MSFTNGP04.phx.gbl... > Great stuff, > > Just what I wanted, thanks for that Anthony. > > )> > Sean > > "Anthony" <anthony.spam@spammedout.com> wrote in message > news:e1UxgVCzGHA.996@TK2MSFTNGP03.phx.gbl... >> Check that the first DC has an active-directory integrated zone. >> Check that each DC is using the first DC as its primary DNS, and the >> second DC as its secondary DNS. >> Install DNS on the second DC. Configure your forwarder to your ISP, same >> as on the first. >> The integrated zone will create itself in the forward lookup zones. >> Anthony >> >> >> >> >> "Sean" <sean@ghostydog.com> wrote in message >> news:uoR4OzBzGHA.2300@TK2MSFTNGP05.phx.gbl... >>> Hi >>> >>> Just recently started a new job and the company I am working at has 2 >>> DC's for robustness but only one has DNS running. We have no other DNS >>> server on site so my question is what do I need to configure DNS on the >>> second DC and is there a resource that can walk me through this? >>> >>> Cheers for any replies >>> >>> GD >>> >> >> > > |
|
![]() |
| Outils de la discussion | |
|
|