Strange DNS question
This is not a major issue but just bugging me as I cannot find out why.
We have scavenging setup in DNS to remove stale records after 12hours however has I believe by default Windows requests it’s a record updated every 24 hours. This then leads to the A record existing for 12 hours, not existing for 12 hours, existing for 12 hours……..and so on.
DHCP is set to dynamically update DNS A records only if requested by the DHCP client.
The below registry key will reduce the refresh time and 4 hours works and keeps the A record alive in DNS well but my question is below
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters]
Create DWORD = RegistrationRefreshInterval = time in seconds e.g. 14400
If the A record doesn’t exist in DNS, as its been scavenged, why is the name being resolved on its LAN but not on other sites over the WAN? Is some sort of broadcast being used?
This is not a major issue but just bugging me as I cannot find out why.
We have scavenging setup in DNS to remove stale records after 12hours however has I believe by default Windows requests it’s a record updated every 24 hours. This then leads to the A record existing for 12 hours, not existing for 12 hours, existing for 12 hours……..and so on.
DHCP is set to dynamically update DNS A records only if requested by the DHCP client.
The below registry key will reduce the refresh time and 4 hours works and keeps the A record alive in DNS well but my question is below
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters]
Create DWORD = RegistrationRefreshInterval = time in seconds e.g. 14400
If the A record doesn’t exist in DNS, as its been scavenged, why is the name being resolved on its LAN but not on other sites over the WAN? Is some sort of broadcast being used?
