Changing Reverse Zone to AD Integrated

[Frank Anthony]

Hi,
I using W2K Adv.Servers with W2k WS. and a few NT
Workstations. I did not setup the servers but I noticed
the DNS servers didn't use reverse lookup zones.

So I setup reverse lookup. A few months after I noticed
all 3 DNS servers had the forward lookup setup as AD
Integrated and the reverse lookup was setup as primary
servers.

I want to change the reverse lookup to AD integrated, but
I am not sure if this would cause problems or downtime.
Can I just change the reverse lookup to AD Integrated
during working hours or should I wait until the weekend?

 

[Kevin D. Goodknecht [MVP]]

In

Hi,
I using W2K Adv.Servers with W2k WS. and a few NT
Workstations. I did not setup the servers but I noticed
the DNS servers didn't use reverse lookup zones.

So I setup reverse lookup. A few months after I noticed
all 3 DNS servers had the forward lookup setup as AD
Integrated and the reverse lookup was setup as primary
servers.

I want to change the reverse lookup to AD integrated, but
I am not sure if this would cause problems or downtime.
Can I just change the reverse lookup to AD Integrated
during working hours or should I wait until the weekend?

It should cause any downtime unless you have an application that requires a
reverse lookup. Usually, only public SMTP servers care anything about
reverse lookups anyway. You could delete the reverse lookup zone completely
and for the most part only nslookup would notice.
So with that being said, if all three servers have Primary reverse lookup
zones and all are on the same subnet and all are Domain Controllers, delete
the reverse lookup zone on two of the DCs and on the third server change it
to AD integrated, allow dynamic updates, that zone will get replicated to
the other DCs, with no further action on your part. Depending on the size of
the zone and how well replication works, it takes about fifteen minutes to
an hour.

 

[Danny Slye - [MSFT}]

It shouldn't cause a problem, not many applications make use of reverse
lookups. Once you you delete the primary zones from 2 of the servers, you
can convent the zone to AD-Integrated and then force replication to push
the zone data to all of the DCs running DNS. For a backup plan, just save
the zone files. You can always use them to recreate a primary zone.

198437 How to Convert DNS Primary Server to Active Directory Integrated
http://support.microsoft.com/?id=198437
--------------------

Hi,
I using W2K Adv.Servers with W2k WS. and a few NT
Workstations. I did not setup the servers but I noticed
the DNS servers didn't use reverse lookup zones.

So I setup reverse lookup. A few months after I noticed
all 3 DNS servers had the forward lookup setup as AD
Integrated and the reverse lookup was setup as primary
servers.

I want to change the reverse lookup to AD integrated, but
I am not sure if this would cause problems or downtime.
Can I just change the reverse lookup to AD Integrated
during working hours or should I wait until the weekend?

__
Danny Slye
Microsoft Support Professional
MCSE

This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit. Thanks!

 

[Frank Anthony]

Thanks for the replies!

Frank

 

[Dave Baldridge]

Hi Frank,

Changing the zone type from primary to AD integrated can be done at any time
usually without interruption to your clients. The only difference is where
the records are stored, ie. in a file (winnt\system32\dns) or in the active
directory database. It is really not necessary to make such a change during
production, however, to avoid any unforseen problems, make the change after
hours to err on the side of safety.

Thanks and have a great day.

Dave Baldridge MCSE 2000
MPS Protocols Support Professional