20320 and 20317 DHCP Issues.

Question

_{Friday, August 23, 2019 2:54 AM}

Hi all.

I was wondering if anyone can give me some solid advice how to fix a major issue. We just bought brand spankin new servers and installed Windows Server 2019 Standard on it. We joined it to our Domain (2 Server 2008R2 and 1 Server 2016 Standard servers). One of the 2008R2 servers was the “primary” server.  The DHCP information was backed up from the 2008R2 server and imported into DHCP server on the new 2019 servers once the 2008’s were demoted and taken off the domain.

Right off the bat we had dns issues. Figured out there was no forwards set so I set them to 8.8.8.8

Worked great, but the next day we had computers getting booted off the network,

What we figured that once a client requested a DHCP lease renewal, that would work, but something in the DNS was not update. So the computer basically got booted form the internet and could not access domain resources. We “fixed” the issue by clearing out the records in the DHCP, and that seemed to solve the problem. A week later weird stuff started happening again.

Our Kyocera copier can no longer send faxes and scans to shared folders on the server (SMB)

Can’t Ping the first server but can remote into it

Can Ping the second server but can’t remote into it

Hyper V machine on first server can not access shared folders on first server but can on second. (This used to work)

Here are some Event log errors.

Event Id 20320  Source DHCP Server

PTR record registration for IPv4 address [[192.168.2.245]] and FQDN StrattonPC.pennview.local failed with error SERV_FAIL. This is likely to be because the reverse lookup zone for this record does not exist on the DNS server.

Event Id 20317  Source DHCP Server

Forward record registration for IPv4 address [[192.168.2.102]] and FQDN Galaxy-S9 failed with error SERV_FAIL. This is likely to be because the forward lookup zone for this record does not exist on the DNS server.

Event Id 20321  Source DHCP Server

PTR record registration for IPv4 address [[192.168.1.34]] and FQDN Frank.pennview.local failed with error TIMEOUT.

Event Id 30322  Source DHCP Server

PTR record registration for IPv4 address [[192.168.1.34]] and FQDN Frank.pennview.local failed with error 9005 (DNS operation refused.

).

Now I can’t log into the second server either by name or by ip address so I cant show logs on the first server.

The server 2016 server is off site and does not show these types of errors.

If anyone can point me in the right direction how to fix this issue that would be great.

Thanks

Doug

(Updated with event 30321)

All replies (3)

_{Friday, August 23, 2019 8:31 AM}

Hi,

Thanks for posting in this forum.

Error based on event ID, please confirm if there is a reverse lookup zone corresponding to the record.

Based on my knowledge, dynamic DNS updates are attempts to update PTR records, which is usually done with host A record updates. In order to send a PTR update, an SOA query is first performed against the host's reverse record to see who has the authority to accept the update. If the DNS server does not have a reverse lookup zone, the error sent back to the DHCP server will be interpreted as a general update failure.

Best regards,

Abby

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

_{Tuesday, August 27, 2019 9:57 AM}

Hi,

I'm writing to see if the reply is helpful to you.

If you need further assistance, please feel free to post back.

Best regards,

Abby

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

_{Monday, September 2, 2019 9:20 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 no, please reply and tell us the current situation in order to provide further help.

Best Regards,

Abby

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