The better option would be to move the DHCP server role to a windows server. As a work-around you might try lengthening the lease time in router setup.
--please don't forget to Accept as answer if the reply is helpful--
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi,
Our network running with multiple VLAN's obtaining IP's from the Router acting as DHCP server. Problem facing is, sometimes, workstation are unable to ping with the host name though they are on network, checked the DNS server and found multiple DNS records for that workstation available with the different timestamp sometime Forward lookup zone is correct but reverse lookup zone having different IP than the actual. Also checked the DNS Scavenge stale resource records is already selected and Set the No-refresh interval and Refresh interval to be 1 day and that particular IP is not statically assigned but issue seems to be the same kindly advise.
The better option would be to move the DHCP server role to a windows server. As a work-around you might try lengthening the lease time in router setup.
--please don't forget to Accept as answer if the reply is helpful--
Hi,
Thanks for posting in Q&A platform.
Based on your description, my understanding is that the issue is workstation are unable to ping with host name although they are on network. Please correct me if my understanding is wrong.
Before we go further, I would like to confirm the following information with you.
Best Regards,
Sunny
----------
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi SunnyQi-MSFT
Not all the workstation but random PC's and sometimes ping successful with the IP but not hostname to verify checked the reverse lookup zone and found out reverse lookup zone having different IP resulting only with IP works not with the host. so manually I should delete the reverse lookup zone record and update manually in order to ping via hostname.
Not all the workstations but random PC's and ping successful with the IP but not with the host during the investigation found out that reverse lookup zone is not updating with the current login resulting unable to ping with the host so manually i should remove the reverse lookup zone record and update manually to get this done. Most of such issues are happening because of reverse lookup zone record not update. Kindly advice what is extra to be done to update the both FWD and Reverse zone to be updated as actual.
You can try recreating it. In DNS console you can right-click on Reverse Lookup Zones and choose New Zone and follow the prompts
--please don't forget to Accept as answer if the reply is helpful--