Re: Force update of reverse lookups on AD DNS?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Dominik - thank you for your reply.

would you provide us with a basic info about the IP subnet(s) on your
network(s) and name(s) of you reverse look-up zone(s), where you face the
problems?

We have a forward lookup zone (unfortunately I need to obfuscate, I
apologize):

domain.com

There are quite a few subnets on which we have XP boxes. One of them is
10.206.80.0/22 (so 10.206.80.0 - 10.206.83.255). I couldn't find a way
to do supersets of reverse lookups without including all of 10.206.X.X,
so I have seperate reverse lookups for each /24.

One of the DHCP ranges assigned IPs in 10.206.82.X.

There is, for example, a PC named eng-chrisk-hp at 10.206.82.185 (an XP
SP2 box).

There is a reverse lookup zone 82.206.10.in-addr.arpa.

Both forward and reverse zones are configured to be AD integrated and
to allow both secure and nonsecure updates.

The box registered fine in the forward lookup as
eng-chrisk-hp.domain.com.

However, there is no entry in the reverse lookup for this PC. I have
run ipconfig /registerdns on the PC itself and the reverse lookup is
not created.

*Some* reverse lookups in that zone were created properly... about a
dozen. Otherwise it is empty.

There are several ways you can register PTR records: One of them is "Group
Policy" described in this article http://support.microsoft.com/kb/294785/
or here http://support.microsoft.com/kb/300684/

Thanks for the pointer.

I did create a GPO and applied it to all workstations with the
following settings:

Computer Configuration ->
Administrative Templates->
Network/DNS Client->
- Dynamic Update = Enabled
- Register PTR Records = Enabled
-- Register PTR Records = Register
- Registration Refresh Interval = Enabled
-- Seconds = 1800

Group policy modeling indicates that these settings should be set for
his PC, eng-chrisk-hp. However, in the few days these settings have
been active, his PC still has not registered the PTR record.

. Another one is usage of
Windows based DHCP server with option "... register PTR records ... "
enabled. But, at first, I'd check the names of the reverse look-up zones,
cose if the PCs successfully register the A record, it should based on own
IP address automatically attempt to register PTR record in the corresponding
zone .

Well, we currently use a UNIX DHCP server. I'm hoping that can
continue, but if DNS won't work without it, then maybe we'll have to
migrate.

Any other suggestions?

thanks

.

Relevant Pages

  • 1-800 ...,
    ... 1-800 pet meds ... reverse 1-800 lookup ... 1-800 reverse directory ... 1-800 flowers coupons ...
    (de.rec.sport.fussball)
  • Re: Senden unter einer anderen Domaene
    ... Fakt ist dass wir definitiv bei manchen Empfängern ... da diese Reverse Lookup benutzten und das ... IP des Servers auf die Domäne ...
    (microsoft.public.de.german.exchange2000.general)
  • Re: Reverse Lookup (PTR Record) Problem
    ... you can change TTL on the records in reverse ... lookup zone temporarily, to keep it clean. ... PTR records are not being updated/removed correctly. ... Dynamically update DNS A and PTR records for DHCP clients that do not ...
    (microsoft.public.windows.server.dns)
  • Maintaining AD-Integrated Reverse Zone With No DHCP Server on Domain Controller
    ... We had the DHCP server running on the domain controller, ... Apparently the DHCP and DNS applications cooperate with each ... running DHCP on the domain controller, the AD integrated reverse lookup ... domain controller IPs are not appearing in the reverse zone (I had to ...
    (microsoft.public.windows.server.dns)
  • Re: Warning message
    ... The only parts of the zone that are Active ... There are no reverse zones on the Windows DNS ... alone the static BIND server. ... >> has a static bind server running but my dc's actually ...
    (microsoft.public.windows.server.dns)