Secondary DNS

  • Thread starter Thread starter J
  • Start date Start date
J

J

I currently have a win 2000 server w/ AD & AD integrated DNS zone. I
recently added a win 2003 server for webservices which I installed DNS on as
a secondary server to primary AD integrated zone to help speed up DNS
resolution.

1. Should I have both the DC's ip and the new secondary's servers ip listed
in the dns server tab on the new secondary DNS server?

2. I recieve a warning in my app log for ID 3000...logging numerous run time
events...once every day or other day on the new secondary server, is this
something to be concerned about? and if so how would I go about
troubleshooting this issue?

TIA
 
In
J said:
I currently have a win 2000 server w/ AD & AD integrated DNS zone. I
recently added a win 2003 server for webservices which I installed
DNS on as a secondary server to primary AD integrated zone to help
speed up DNS resolution.

1. Should I have both the DC's ip and the new secondary's servers ip
listed in the dns server tab on the new secondary DNS server?
Click to expand...

You mean in the nameservers tab? Yes. I would do it that way.
2. I recieve a warning in my app log for ID 3000...logging numerous
run time events...once every day or other day on the new secondary
server, is this something to be concerned about? and if so how would
I go about troubleshooting this issue?
Click to expand...

See if this helps
http://www.eventid.net/display.asp?eventid=3000&source=

TIA
Click to expand...



--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
In
J said:
I currently have a win 2000 server w/ AD & AD integrated DNS zone. I
recently added a win 2003 server for webservices which I installed
DNS on as a secondary server to primary AD integrated zone to help
speed up DNS resolution.

1. Should I have both the DC's ip and the new secondary's servers ip
listed in the dns server tab on the new secondary DNS server?

2. I recieve a warning in my app log for ID 3000...logging numerous
run time events...once every day or other day on the new secondary
server, is this something to be concerned about? and if so how would
I go about troubleshooting this issue?

TIA
Click to expand...

Ace if you don't mind, I've been there and done that, this is a pretty
common event on a secondary to an AD integrated zone. AD integrated zones
are updated several times an hour, incrementing the zone serial and this
causes many incremental zone transfers. It is all the zone transfers that
cause the 3000 events, you may also see 9999 events logged, too.
You can ignore the events.
 
Back
Top