none
DNS A host records not updating all the time RRS feed

  • Question

  • Hello,

    It seems our DNS isn't updating our users workstations all the time.  I think it's if there is an existing stale record there it will not remove it and update with the new one, not sure.  Scavenging is enabled, but not sure if it's working efficiently.  We see Event ID 8015 and 8018 on some workstations.

    Here are some screenshot of our settings can you see any issues?


    This it the workstations name, but seems it was used before in 2016 and still in there:

    Should I set to always update?


    • Edited by TB303 Thursday, February 8, 2018 11:04 AM
    Thursday, February 8, 2018 11:03 AM

All replies

  • Hi,

    You could enable scavenging.

    And please check it below :

    If you choose “always dynamically update DNS records”,

    you still need to configure Credentials and add the server to the DnsUpdateProxy group.

    There is a checklist for you:

    1 You should ONLY use the internal DNS servers on all machines. Any ISP's addresses will cause it to fail
    2 If any of the DCs are multihomed (multi NICs, multi IPs, and/or RRAS is installed, will more than likely fail, as well as cause other significant problems
    3 The Primary DNS Suffix MUST match the zonename in DNS
    4 The zone in DNS MUST be allowed updates
    5 If the zone updates are set to Secure Only, the machines MUST be joined to work, otherwise, the DHCP server must be configured with Credentials or the DHCP server object must be added to theDnsProxyUpdate group
    6 The AD DNS zone name cannot be a single label name ("DOMAIN" = bad, "domain.com" = good)
    More information about dynamic update DNS ,  please refer to the following article:

    https://blogs.msmvps.com/acefekay/2009/08/20/dhcp-dynamic-dns-updates-scavenging-static-entries-amp-timestamps-and-the-dnsproxyupdate-group/

     

    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

    dynamically update dns records only if requested by the dhcp client AND always dynamically update dns records

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/1f58fcb7-04a2-4f53-ba2f-ad8e3fad644e/dynamically-update-dns-records-only-if-requested-by-the-dhcp-client-or-always-dynamically-update-dns?forum=winserverNIS

    Best Regards,
    Frank


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Friday, February 9, 2018 9:41 AM
  • Hi,
    Just checking in to see if the information provided was helpful. Please let us know if you would like further assistance.

    Best Regards,

    Frank

    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Thursday, February 15, 2018 8:51 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,
    Frank

    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Monday, February 19, 2018 7:37 AM
  • Hello,

    Sorry I've been away.

    What do you mean by:

    "you still need to configure Credentials and add the server to the DnsUpdateProxy group."

    If I enable scavenge how may days should this be?  Should this normally be turned on?

    Monday, February 19, 2018 9:08 AM
  • Hi,

    Create a dedicated user account and configure the DHCP servers with its credentials under the following circumstances:

    The DHCP server is configured to perform DNS dynamic updates on behalf of DHCP clients.

    A domain controller is configured to function as a DHCP server. Without the dedicated user account, secure updates will not work.

    The DNS zones to be updated by the DHCP server are configured to allow only secure dynamic updates.

    More information about DnsUpdateProxy group,please refer to it below

    https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/dd334715(v=ws.10)

    >>If I enable scavenge how may days should this be?  Should this normally be turned on?

    As your configuration, it works 14 days at least. 

    More information about scavenging, refer to it 

    https://blogs.technet.microsoft.com/networking/2008/03/19/dont-be-afraid-of-dns-scavenging-just-be-patient/

    Best Regards,

    Frank


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Wednesday, February 21, 2018 2:46 AM
  • Hi,

    Just check the situation about your issue.

    Best Regards,
    Frank

    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Thursday, February 22, 2018 7:18 AM
  • Will try some of this tomorrow and feed back.

    Thanks

    Thursday, February 22, 2018 4:54 PM
  • 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,
    Frank

    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Friday, March 2, 2018 8:29 AM
  • It seems to still be there.  I did check the DHCP logs and this the kind of logs I see does it look normal:

    24,03/05/18,00:00:35,Database Cleanup Begin,,,,,0,6,,,,,,,,,0
    30,03/05/18,00:00:35,DNS Update Request,172.28.141.3,Workstation824.gb.vo.local,,,0,6,,,,,,,,,0
    30,03/05/18,00:00:35,DNS Update Request,172.28.141.4,Workstation726.gb.vo.local,,,0,6,,,,,,,,,0
    30,03/05/18,00:00:35,DNS Update Request,172.28.141.6,Workstation450.gb.vo.local,,,0,6,,,,,,,,,0
    30,03/05/18,00:00:35,DNS Update Request,172.28.141.7,Workstation965.gb.vo.local,,,0,6,,,,,,,,,0
    30,03/05/18,00:00:35,DNS Update Request,172.28.141.10,Workstation975.gb.vo.local,,,0,6,,,,,,,,,0
    30,03/05/18,00:00:35,DNS Update Request,172.28.141.11,Workstation371.gb.vo.local,,,0,6,,,,,,,,,0
    30,03/05/18,00:00:35,DNS Update Request,172.28.141.12,Workstation534.gb.vo.local,,,0,6,,,,,,,,,0
    30,03/05/18,00:00:35,DNS Update Request,172.28.141.13,Workstation004.gb.vo.local,,,0,6,,,,,,,,,0
    30,03/05/18,00:00:35,DNS Update Request,172.28.141.14,Workstation438.gb.vo.local,,,0,6,,,,,,,,,0
    30,03/05/18,00:00:35,DNS Update Request,172.28.141.16,Workstation115.gb.vo.local,,,0,6,,,,,,,,,0
    30,03/05/18,00:00:35,DNS Update Request,172.28.141.17,Workstation902.gb.vo.local,,,0,6,,,,,,,,,0
    30,03/05/18,00:00:35,DNS Update Request,172.28.141.19,Workstation541.gb.vo.local,,,0,6,,,,,,,,,0
    30,03/05/18,00:00:35,DNS Update Request,172.28.141.20,Workstation744.gb.vo.local,,,0,6,,,,,,,,,0
    30,03/05/18,00:00:35,DNS Update Request,172.28.141.68,Workstation275.gb.vo.local,,,0,6,,,,,,,,,0
    30,03/05/18,00:00:35,DNS Update Request,172.28.150.53,WINDOWS-LIVV6UH.gb.vo.local,,,0,6,,,,,,,,,0
    30,03/05/18,00:00:35,DNS Update Request,172.28.150.54,WOW-Vision.gb.vo.local,,,0,6,,,,,,,,,0
    30,03/05/18,00:00:35,DNS Update Request,172.28.150.55,WINDOWS-OLG2OLI.gb.vo.local,,,0,6,,,,,,,,,0
    30,03/05/18,00:00:35,DNS Update Request,172.28.150.57,WINDOWS-03PM43C.gb.vo.local,,,0,6,,,,,,,,,0
    30,03/05/18,00:00:35,DNS Update Request,172.28.150.58,WINDOWS-5VKPRD2.gb.vo.local,,,0,6,,,,,,,,,0
    30,03/05/18,00:00:35,DNS Update Request,172.28.150.59,WINDOWS-D2SO2PL.gb.vo.local,,,0,6,,,,,,,,,0
    25,03/05/18,00:00:35,0 leases expired and 0 leases deleted,,,,,0,6,,,,,,,,,0
    25,03/05/18,00:00:35,0 leases expired and 0 leases deleted,,,,,0,6,,,,,,,,,0
    31,03/05/18,00:00:35,DNS Update Failed,172.28.141.3,Workstation824.gb.vo.local,,,0,6,,,,,,,,,9009
    31,03/05/18,00:00:35,DNS Update Failed,172.28.141.4,Workstation726.gb.vo.local,,,0,6,,,,,,,,,9009
    31,03/05/18,00:00:35,DNS Update Failed,172.28.141.6,Workstation450.gb.vo.local,,,0,6,,,,,,,,,9009
    31,03/05/18,00:00:35,DNS Update Failed,172.28.141.7,Workstation965.gb.vo.local,,,0,6,,,,,,,,,9009
    31,03/05/18,00:00:35,DNS Update Failed,172.28.141.10,Workstation975.gb.vo.local,,,0,6,,,,,,,,,9009
    31,03/05/18,00:00:35,DNS Update Failed,172.28.141.11,Workstation371.gb.vo.local,,,0,6,,,,,,,,,9009
    31,03/05/18,00:00:35,DNS Update Failed,172.28.141.12,Workstation534.gb.vo.local,,,0,6,,,,,,,,,9009
    31,03/05/18,00:00:35,DNS Update Failed,172.28.141.13,Workstation004.gb.vo.local,,,0,6,,,,,,,,,9009
    31,03/05/18,00:00:35,DNS Update Failed,172.28.141.14,Workstation438.gb.vo.local,,,0,6,,,,,,,,,9009
    31,03/05/18,00:00:35,DNS Update Failed,172.28.141.16,Workstation115.gb.vo.local,,,0,6,,,,,,,,,9009
    31,03/05/18,00:00:35,DNS Update Failed,172.28.141.17,Workstation902.gb.vo.local,,,0,6,,,,,,,,,9009
    31,03/05/18,00:00:35,DNS Update Failed,172.28.141.19,Workstation541.gb.vo.local,,,0,6,,,,,,,,,9009
    31,03/05/18,00:00:35,DNS Update Failed,172.28.141.20,Workstation744.gb.vo.local,,,0,6,,,,,,,,,9009
    31,03/05/18,00:00:35,DNS Update Failed,172.28.141.68,Workstation275.gb.vo.local,,,0,6,,,,,,,,,9009
    31,03/05/18,00:00:35,DNS Update Failed,172.28.150.53,WINDOWS-LIVV6UH.gb.vo.local,,,0,6,,,,,,,,,9009
    31,03/05/18,00:00:35,DNS Update Failed,172.28.150.54,WOW-Vision.gb.vo.local,,,0,6,,,,,,,,,9009
    31,03/05/18,00:00:35,DNS Update Failed,172.28.150.55,WINDOWS-OLG2OLI.gb.vo.local,,,0,6,,,,,,,,,9009
    31,03/05/18,00:00:35,DNS Update Failed,172.28.150.57,WINDOWS-03PM43C.gb.vo.local,,,0,6,,,,,,,,,9009
    31,03/05/18,00:00:35,DNS Update Failed,172.28.150.58,WINDOWS-5VKPRD2.gb.vo.local,,,0,6,,,,,,,,,9009
    31,03/05/18,00:00:35,DNS Update Failed,172.28.150.59,WINDOWS-D2SO2PL.gb.vo.local,,,0,6,,,,,,,,,9009

    Tuesday, March 6, 2018 9:05 AM