How to update reverse DNS entries after changing lan address

W

wjr

Changed a Windows 2000 Server IP Address from 10.10.10.48 to 192.168.1.9
because our internal network changed. The domain is the same, but I was
looking at the DNS settings. We are NOT using DHCP and will not use it.

I have a test box, newsystem, which was at 10.10.10.80 but is now at
192.168.1.20. When changing DNS entry and checking the Update the
associated pointer (PTR) record box the following error occurred.

Warning: The associated pointer (PTR) record cannot be created,
probably because the referrenced reverse lookup zone cannot be found.
In the reverse zone, there is a 10.10.10.in-addr.arpa but not a
192.1691.in-addr.arpa.

What is the best approach to correcting this? Delete the existing zone
and create a new one? Or something else?
 
P

Phillip Windell

You have to create the Reverse Lookup Zone.
Doesn't matter if you are using DHCP or not.
If the old Zone is no lonager needed then delete it.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
 
P

Phillip Windell

No problem :)

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Reverse DNS Issue 4
reverse dns 3
how to change FQDN of a reverse-zone 2
Reverse dns ptr/mx records not working.. Getting stuck in loop. 0
Reverse Lookup problem (Duplicate zone found) 3
Reverse DNS entries for MX records 1
Reverse lookup zone entries that won't delete 1
Dynamic DNS not working after Subnet change. 3

Top