Re: No PTR Records Dynamically

Thanks for your help Herb.

"Herb Martin" wrote:

"Stu Mayhem" <StuMayhem@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6F606A53-06E4-4151-ACBA-F7194D40AA4A@xxxxxxxxxxxxxxxx
" None of my reverse zones have any extra 0's on the front
as you show so if you have those then remove them.
0.1.10.in-addr.arpa should be merely: 1.10.in-addr.arpa"

That is the question I have, do I create new zones and delete the old
ones,
or is there a way to change or rename the existing ones?

I do not believe there is any way to rename these in
the GUI.

You could do this perhaps by editing the registry but that
would be vastly complicated (and more dangerous) for AD
integrated zones.

You probably have to recreate them and add any manual
registrations yourself.

Automatic registration can be obtained with "ipconfig /registerdns"
on ordinary machines and by either stopping & starting the NetLogon
service or using "NetDiag /fix"or "DCDiag /fix" for DCs.

Rebooting also works for all machines, but that is overkill.

Consider this is not that bad for reverse zones however since
those records are seldom really needed ANYWAY.

There is actually very little purpose for internal (off the Inet)
reverse records anyway, except perhaps occasional admin
convenience.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]


"Herb Martin" wrote:

"Stu Mayhem" <StuMayhem@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8833C3CD-9294-4490-9E02-C169F3BD840C@xxxxxxxxxxxxxxxx
Sorry, I should have noticed this before, the Reverse Zone is
0.1.10.in-addr.arpa, however it should be 1.10.in-addr-arpa, or 10.1.x.
Is
there anyway to rename it it, or do I need to create a new zone?


We need to be careful about that name and Microsoft's MMC's
attempt to be "helpful".

The name of that zone should BE 1.10.in-addr.arpa
but when ADDING the reverse zone you have a choice
between adding it by NAME (as above) or by "network
id" in natural order: 10.1

None of my reverse zones have any extra 0's on the front
as you show so if you have those then remove them.

0.1.10.in-addr.arpa should be merely: 1.10.in-addr.arpa

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

"Stu Mayhem" wrote:

OK, thanks but I am still at the same place. We do not have any PTR
Records
being added Dynamically in DNS, the A records
are being added. DHCP is running on a DC. I have tried specifying
user
credentials for Dynamic Updates but it did not work. I am seeing
Error
31
Dyanmic Update failed in the DHCP logs.


"Herb Martin" wrote:

"Stu Mayhem" <StuMayhem@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BABFF122-AB12-4071-9838-C08060790204@xxxxxxxxxxxxxxxx
In the DHCP Log I see 31 Dynamic Update Failed. Like I said I
attempted
to
use credentials already, but just to be sure, what groups does the
user I
use
need to be a member of? I am guessing DNSUpdateProxy, anything
else?

Generally nothing special.

Definitely not DNSUpdateProxy which is an ALTERNATIVE
(and less secure) than specific credentials.

A regualar account should be perfectly usuable and is only
an issue if you have multiple DHCP servers which would
otherwise fight over ownership fo the DNS records when
using Secure updates.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]


"Herb Martin" wrote:

"Stu Mayhem" <StuMayhem@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:5E59E262-A88A-40DA-8FC1-2C757A986649@xxxxxxxxxxxxxxxx
"Then likely you have trouble with your (possibly missing)
REVERSE zone." - The reverse Zones are present and set
correctly.
We
have
multiple Reverse zones: 0.0.10.in-addr.arpa,
0.1.10.in-addr.arpa,
0.100.10.in-addr.arpa, etc.

Can we assume you use 10.100.0.0 or 10.100.1.0 addresses?

"The DNS server for your clients must either HOLD the reverse
zone OR be able to find the (master) DNS server which does --
same rule as for forward zones." - This is on the primary DNS
Server.

I did not create the reverse zone, I do not know who did, I am
inheritting
it. It is set to Dynamic Updates Nonsecure and Secure. A
strange
thing,
we
have around 400 clients, there are PTR records for Clients that
are not
DHCP
(Mostly servers), DHCP clients do not have a PTR record.

Ok, then you have the Reverse Zone, it's on the same server
the clients are using (and thus reachable), and it is dynamic.

After that there is no likely reason the DHCP server cannot
register the clients SINCE it is already registering the Forward
records.

You might double check that the DHCP server is set to make
the registrations but surely you have done that by now since
you were knowledgeable enough to know of the existence of
"credentials"

BTW, those credentials are only needed for SECURE updates
but are a good idea for that.


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]


"Herb Martin" wrote:

"Stu Mayhem" <StuMayhem@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:83F82BAD-A0AE-4614-A009-4CFF663BB500@xxxxxxxxxxxxxxxx
Herb,
I do not understand the questions.

Then likely you have trouble with your (possibly missing)
REVERSE zone.

Did you create the reverse zone?
The zones are set on the DNS server.

You have a zone for the FORWARD (name zone) such as
yourDomain.com but did you create the REVERSE zone
that maps IP to names?

This would look like "168.192.in-addr.arpa" depending on
the actual IP range.

Is the reverse zone set to be dynamic?

If you have that reverse zone, it is TOTALLY unrelated to
the forward zone so you have to use the REVERSE zones
properties to make it DYNAMIC just as you would a forward
zone.

Is the reverse zone discoverable by the DNS server
the clients and DHCP server are using?

The DNS server for your clients must either HOLD the reverse
zone OR be able to find the (master) DNS server which does --
same rule as for forward zones.

If the answers to the above are all yes (or fixing them
doesn't solve the problem) then please describe how
your REVERSE zones are set (where, which DNS server,
how the DHCP is related to them, etc.)

You wrote "the zones are setup" -- Which zones, give all of
the names and tell us which DNS holds them, and whether they
are DYNAMIC (in properties.)

DHCP is set to dynamically update. For each of my clients
DHCP
is
creating
an A record in the forward lookup zone however it is not
creating a
PTR
record in the reverse lookup zone.

So did YOU create the REVERSE ZONE? Is the reverse zone
dynamic?

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]


"Herb Martin" wrote:

"Stu Mayhem" <Stu Mayhem@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in
message
news:E81EA049-F940-4788-8A42-248C11150DEE@xxxxxxxxxxxxxxxx
We do not have any PTR Records being added Dynamically in
DNS,
the A
records
are being added. DHCP is running on a DC. I have tried
specifying
user
credentials for Dynamic Updates but it did not work.

Did you create the reverse zone?

Is the reverse zone set to be dynamic?

Is the reverse zone discoverable by the DNS server
the clients and DHCP server are using?

If the answers to the above are all yes (or fixing them
doesn't solve the problem) then please describe how
your REVERSE zones are set (where, which DNS server,
how the DHCP is related to them, etc.)


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]


















.

Relevant Pages

  • Re: DDNS from NW6.5 to W2K
    ... > Option 15 doesn't appear to exist on the NetWare DHCP server. ... >>> DNS server. ... Each zone has ...
    (microsoft.public.windows.server.dns)
  • Re: DNS PROBLEMS !
    ... I'm having the same problem with stale records even when they are set to ... DC is also my DHCP server. ... My DHCP server is configred to update DNS. ... >> Lookup zone, but will not appear in the Forward Lookup zone. ...
    (microsoft.public.windows.server.dns)
  • Re: Maintaining AD-Integrated Reverse Zone With No DHCP Server on Domain Controller
    ... DHCP server runs on a member server. ... No. AD Integrated zones are only available on DCs that are DNS servers. ... DC I'm having to use a secondary zone grabbed from the Windows 2003 ...
    (microsoft.public.windows.server.dns)
  • Re: Moving DNS to New Server
    ... DHCP already migrated. ... Paul recommends installing DNS before promoting the DC. ... but I'm still seeing my Zone. ... I've set up a new server as a DC. ...
    (microsoft.public.win2000.dns)
  • Re: primary/secondary server names
    ... > You mean you want to use this server as a nameserver for a public domain? ... > to be delegated from the ISP's DNS to your DNS, ... > takes that IP and looks in your reverse zone for the name. ...
    (microsoft.public.win2000.dns)