DNS - Not updating forward lookup zone?

Question

Windows 2000 server as PDC, with AD, DNS & DHCP operating. Secondary DC is currently server 2003 R2 with AD & DNS. AD is operating in 2000 Native mode. Dynamic updates are active for the zones.
DHCP updates reverse DNS fine. But the forward lookup, fails to update? No error in the error log?
The original PDC roles were seized due to major hardware failure, and transferred to what is now the PDC.

Any advise greatly appreciated.

Answer 1

I only know Novell DNS/DHCP, but do you need to designate an authoratative server for each zone - maybe it's not set correctly for the forward-lookup zones?

Try creating a new forward-lookup zone for a new subnet and see if dynamic DHCP updates work on that.

Have you restarted the DNS/DHCP services recently ... if possible it's always worth doing to save yourself a lot of headache. Check the logs immediately after doing so.

Answer 2

1

Answer 3

Reverse Phone Number Look Up Services

Answer 4

Off the top of my head, I'm sure it has to do with 2003 treating DNS differently than 2000. Have you tried making the 2003 server do DHCP for you? And make sure there are no static DNS entries on PC's or old server.

Answer 5

reverse phone number search compiles hundreds of millions of phone book records to help locate the owner's name, location, time zone, email and other public information.



Use a reverse phone lookup to:

Get the identity of an unknown caller.

Identify an area code.

Recall the name of a person whose number you wrote down.

Identify an unfamiliar phone number that shows up on your bill.

https://tr.im/721a7

Answer 6

reverse phone number search compiles hundreds of millions of phone book records to help locate the owner's name, location, time zone, email and other public information.



Use a reverse phone lookup to:

Get the identity of an unknown caller.

Identify an area code.

Recall the name of a person whose number you wrote down.

Identify an unfamiliar phone number that shows up on your bill.

https://tr.im/1FuCM

Answer 7

did you update the serial number?

did you flush the dns on your client so it's actually hitting the DNS and not taking it from its local cache?

Answer 8

You need to flush the DNS. This is very easy, go to the command promt and type "DNS /flush" and then check the results.