PTR Record Registration Failed With Error 9004

Question

_{Friday, August 17, 2018 4:10 PM}

PTR record registration for IPv4 address [[192.***.3.**]] and FQDN DV-**-17.****.com failed with error 9004 (DNS request not supported by name server)

Task Category: Name Registration.

Asterisks are mine.

Hey guys, I need some help figuring out why my DHCP Error log is being spammed with this error. I 've had 70ish in the last hour, but I am not hearing about anyone having issues or noticing anything weird going on. I just noticed this was sitting in the error logs.

I have the server to check to see if an IP has been rented twice instead of just once. Could that throw these errors?

All replies (4)

_{Tuesday, August 21, 2018 7:47 AM ✅Answered | 1 vote}

Hi,

Thanks for your reply.

You can manually create a reverse lookup zone for the forward lookup zone.

When you register A records in a forward lookup zone, you need a reverse lookup zone for PTR records.

It is always good to create reverse lookup zones for IP to hostname resolution. 

Please refer to the links below:

https://www.server-world.info/en/note?os=Windows_Server_2016&p=dns&f=3 

Best regards,

Travis

Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]

_{Monday, August 20, 2018 3:25 AM}

Hi,

Thanks for your question.

Have you created a reverse lookup zone for [192.***.3.**] ? 

Checking if the IP has been rented twice will not throw these errors.

Best regards,

Travis

Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]

_{Monday, August 20, 2018 8:13 PM}

Hi, everything is default off a fresh install of Windows Server 2016 Standard. When I made the AD it created the DNS server automatically and hasn't been touched since. We are not linked to another site's DC. We are the PDC for ourselves so to speak.

I have not manually created a reverse lookup zone for the server or any users.

The 192.***.3.** address is an IP assigned by the DHCP service for a user on our network (onsite).

No VM ware involved. One server is handling this.

The 60 to 70 errors are a culmination of most of the IP addresses on our network, but everything is working fine, but I know we shouldn't be getting that many DHCP errors. There's something I didn't do and I don't know what it is.

_{Thursday, August 23, 2018 7:03 AM}

Hi,

Was your issue resolved?

If you resolved it using our solution, please "mark it as answer" to help other community members find the helpful reply quickly.

If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions.

If no, please reply and tell us the current situation in order to provide further help.

Best Regards,

Travis

Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]