4,659 questions
As a general rule windows member servers / application servers have their addressing (and DNS settings) set up statically.
--please don't forget to Accept as answer if the reply is helpful--
do you make all servers DNS records static?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(214.4, 7.000000000000001%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJJ%3C/text%3E%3C/svg%3E)
John JY
221
Reputation points
Hi,
Do you make your server DNS static? We get proposal to make all servers DNS static in order to enable scavenging.
Can you share?
Thank you!
Windows for business | Windows Client for IT Pros | Networking | Network connectivity and file sharing
Accepted answer
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous2021-01-12T20:20:54.973+00:00 -
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(252.8, 6%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBL%3C/text%3E%3C/svg%3E)
Ben Langers 1 Reputation point2023-08-28T12:43:53.9866667+00:00 While that is sort of true, it does not answer the question. Seems like a rather classic mixup between static IP configuration and static vs dynamic DNS records...
While you could indeed configure all hosts running servers statically, there is no valid reason to use static DNS records for anything but devices not supporting dynamic DNS. Even then it is better to have DHCP register those records dynamically than use static records in my personal opinion.
Sign in to comment -
3 additional answers
Sort by: Most helpful
-
Gloria Gu 3,941 Reputation points2021-01-13T01:52:20.307+00:00 @John JY Hi,
Thank you for posting in Q&A!
The difference between static and dynamic DNS records are: dynamic DNS records will aged/scavenged according to the time stamp, but static records are never scavenged.
What are the advantages? That really depends on your environment. Scavenging will not remove a static DNS entry. It will stay forever unless someone removes it. You will always have that entry available in the future.
For more details, please refer to:
https://community.spiceworks.com/topic/2221058-dis-advantages-of-static-dns-recordsHope you have a nice day : )
Gloria============================================
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.
https://learn.microsoft.com/en-us/answers/articles/67444/email-notifications.html -
John JY 221 Reputation points
2021-01-14T17:04:33.967+00:00 Thank you for your help.
For a safe side, is it better to turn every member server dynamic DNS record to static? thanks
-
Gloria Gu 3,941 Reputation points
2021-01-15T01:36:23.917+00:00 Yes, usually we will configure the member server DNS records to be static.
Sign in to comment -
-
Ben Langers 1 Reputation point
2023-08-28T12:41:21.78+00:00 My 2 sats...
DNS records should only be made static for devices that do not support dynamic DNS registrations. Windows servers joined to AD and using Microsoft DNS services are able to refresh their DNS records so changing those to static makes no sense as you would have to manually manage them as of them.
Not a big deal as such, but with anything but the smallest DNS zones, you will soon be looking at bunches of DNS registration for devices that no longer exist on the network.
The only 'risk' is that you have to make sure your DNS setup is working correctly, but that is IMHO a hard requirement for any environment...