Re: Adding Reverse Lookup Zones
- From: "dave Admin" <dmackler@xxxxxxxxxxxxx>
- Date: Thu, 2 Mar 2006 07:06:08 -0700
Ace,
That is interesting and apparently not the issue I had. Finally solved the
ID ten T ( idiot) award. On a tech support site I posted the same issue and
it was suggested that while I had setup the forward zones as AD Integrated
perhaps I had not setup the reverse zones as AD Integrated. I had not, I
had assumed (that's where the idiot comes in) that DNS was either AD
Integrated or not, I now know that is not true. Once I changed the Reverse
zone to AD Integrated and waited overnight for replication, both my problems
disappeared, the Reverse Zones are properly replicating to all DNS servers
and the dynamic updates are no longer "pending" in the DNS tab of DHCP for
the DNS servers that had no reverse zones.
Thanks for all the input, I've learned much
dave Admin
"Ace Fekay [MVP]"
<PleaseSubstituteMyActualFirstName&LastNameHere@xxxxxxxxxxx> wrote in
message news:uwQSdiOPGHA.1460@xxxxxxxxxxxxxxxxxxxxxxx
In news:uy8CM6HPGHA.812@xxxxxxxxxxxxxxxxxxxx,
dave Admin <dmackler@xxxxxxxxxxxxx> stated, which I commented on below:
Ace.
This is interesting. The article relates to an event ID in the DNS
server log. The DNS server log on the server with this issue is
empty, there are no entries. I double-checked the properties and DNS
is setup to record a log for ALL events. There are also no error
events in the DNS Event Viewer.
dave
Hmm, I wouldn't necessarily go with whether a log entry is recorded or not
if there are dupes in the zone. Matter of fact, one time I saw the error
popup on the screen when I attempted to change the replication scope of a
zone for a person who needed hel with this. The error showed up as "Name
you are attempting on the network interface it too long". (Close if not
exact). I just stared at that trying to make heads or tails out of it. I
looked in the Event viewer and it showed nothing regarding this thing. I
then looked into ADSIEdit for the DomainNC, DomainDnsZones and
ForestDnsZones application partition, and that's when I saw there were
dupes and a bunch of CNFs. I simply change the zone to non-AD integrated,
forced all DCs to replicate, then deleted ALL the CNFs I found, then reset
it to AD integrated and set the scope I wanted and it worked.
I thought this may be the issue you are seeing and is why I suggested to
use ADSI Edit to at least double check it.
Ace
.
- Follow-Ups:
- Re: Adding Reverse Lookup Zones
- From: Ace Fekay [MVP]
- Re: Adding Reverse Lookup Zones
- References:
- Re: Adding Reverse Lookup Zones
- From: Ace Fekay [MVP]
- Re: Adding Reverse Lookup Zones
- Prev by Date: Re: SPF Records
- Next by Date: Re: Windows 2000 and Windows 2003 DNS
- Previous by thread: Re: Adding Reverse Lookup Zones
- Next by thread: Re: Adding Reverse Lookup Zones
- Index(es):
Relevant Pages
|