DNS Scavanging Advice for Windows 2008 R2 Domain
hey everyone,
we've been having dns issues our dhcp managed clients several years now, , new product we're putting in (package management) needs correct dns info work correctly. have domain of 250 computers, 40 or servers. servers naturally have statically assigned ips, , few exceptions (mostly machines), else dhcp. rebuild our user computer pretty (every 1-1.5 years), gives lot of oportunity junk records build up. our environment consists of 1 large home office our server , half of our client machine, several smaller branch offices on 1.5-4.5 mbps mpls links, , many mobile , home users connect using vpn client on aircards , personal connections. particularly vpn users, ips apt change frequently, , optimal performance of package management software, need have up-to-date dns information available it.
the dhcp lease time for home office , branch offices 8 days. far know, there no lease on vpn , asa gives them ip when connect , opens reassignment when disconnect. of our mobile reps connect , discoonnect multiple times day.
when our dns zone, see records computers haven't existed 3 years, , timestamps reflect (the worst being 2010 yet). have spent several hours researching issue , seems dns scavenging @ least part of solution, since clean out old records hostnames (including 3 year old ones) , let new , updated 1 populate , used effectively. run plan people understand better though, since change affect our entire domain, , i'm not keen on breaking things.
what i've read indicates me dns scanvenging timeframe should less dhcp lease timeframe, have no trouble doing. understand reason no-refresh interval prevent unecessary record updates , replication, though since have a small domain , don't have secondary domain controllers on opposite ends of slower mpls links mentioned before, i'm not concerned that.
given vpn situation, think aggressive scavenging configuration best. configure no-refresh interval nothing, , refresh interval not more. thinking 1 hour , 4 hours respectively. configure scavanging period 12 hours. thinking should keep things fresh, , said, i'm not anticipating performance problems due small size of domain.
if read through , offer feedback, appreciated. tried cover relevant making decision here, may have missed things, please ask if need know.
i started looking stuff , did find people advocated against short intervals (hours) unless way can in situation.
this starting point me: http://blogs.technet.com/b/networking/archive/2008/03/19/don-t-be-afraid-of-dns-scavenging-just-be-patient.aspx
Windows Server > Network Infrastructure Servers
Comments
Post a Comment