Server 2016 And 2012 R2 – DNS TTL Cache Time Change (Improve_Network Performance) VIDEO TUTORIAL

Server 2016 And 2012 R2 - DNS TTL Cache Time Change (Improve_Network Performance) VIDEO TUTORIAL

  In a network environment the DNS server is responsible for ensuring computers can communicate with each other. If the cache is old then the ip addresses that are in the cache will be wrong. At the same time if the cache is refreshed very frequently then they will be a hit on the network and the server. This video shows how to modify TTL to improve network performance.  
Transcript (machine generated so it contains errors)
1. 00:00:00:00 / 00:00:03:65 - hello in this video we're gonna have a
2. 00:00:02:37 / 00:00:08:63 - look
3. 00:00:03:65 / 00:00:13:46 - DNS TTL time-to-live settings okay and
4. 00:00:08:63 / 00:00:15:83 - how we can affect basically client
5. 00:00:13:46 / 00:00:18:66 - computers connected to our server and
6. 00:00:15:83 / 00:00:21:35 - how our server also might behave okay
7. 00:00:18:66 / 00:00:24:32 - very simply okay how do we get there
8. 00:00:21:35 / 00:00:28:50 - okay let's start off by going to server
9. 00:00:24:32 / 00:00:31:50 - manager we go there in Server 2016 and
10. 00:00:28:50 / 00:00:34:55 - click on All Apps it brings up server
11. 00:00:31:50 / 00:00:38:10 - manager or in Server 2012 it's in the
12. 00:00:34:55 / 00:00:41:96 - start or end here okay once we open it
13. 00:00:38:10 / 00:00:45:57 - we have our DNS click on DNS right click
14. 00:00:41:96 / 00:00:49:23 - on our DNS server wait for a DNS manager
15. 00:00:45:57 / 00:00:51:62 - ok and basically we might have lots and
16. 00:00:49:22 / 00:00:55:28 - lots of zones choose a zone that you
17. 00:00:51:62 / 00:00:59:90 - want to have an impact and right click
18. 00:00:55:28 / 00:01:03:71 - properties sort of authority and we get
19. 00:00:59:90 / 00:01:06:65 - there ok if you are constantly shall we
20. 00:01:03:71 / 00:01:08:87 - say changing computers and IP addresses
21. 00:01:06:65 / 00:01:11:43 - are constantly being released and new IP
22. 00:01:08:87 / 00:01:14:28 - addresses are being given on a very very
23. 00:01:11:43 / 00:01:17:43 - rapid basis you might want to change
24. 00:01:14:28 / 00:01:19:92 - this from one hour to five minutes ten
25. 00:01:17:43 / 00:01:22:58 - minutes a few seconds depending on how
26. 00:01:19:92 / 00:01:25:76 - rapid your environment changes okay
27. 00:01:22:57 / 00:01:29:00 - however it does increase the amount of
28. 00:01:25:76 / 00:01:31:93 - DNS traffic going on which can take a
29. 00:01:29:00 / 00:01:33:71 - big hit if you are having a big
30. 00:01:31:93 / 00:01:35:75 - organization with lots and lots of
31. 00:01:33:71 / 00:01:41:06 - computers doing lots and lots of DNS
32. 00:01:35:75 / 00:01:44:90 - traffic at the same time okay if we
33. 00:01:41:06 / 00:01:47:27 - don't have too much changes taking place
34. 00:01:44:90 / 00:01:50:04 - in our environment if most of our
35. 00:01:47:28 / 00:01:54:11 - computers are already set up and their
36. 00:01:50:04 / 00:01:58:71 - IP addresses basically are gonna be
37. 00:01:54:11 / 00:02:02:54 - shall we say almost static okay for a
38. 00:01:58:70 / 00:02:04:34 - day two days half a day those are the
39. 00:02:02:54 / 00:02:06:81 - things you might want to increase this
40. 00:02:04:34 / 00:02:09:29 - number okay
41. 00:02:06:81 / 00:02:14:78 - and by changing it by shall we say
42. 00:02:09:30 / 00:02:17:01 - making it one day okay or five hours you
43. 00:02:14:78 / 00:02:21:59 - reduce the amount of DNS traffic and
44. 00:02:17:00 / 00:02:24:78 - this can improve the general overall
45. 00:02:21:59 / 00:02:26:66 - flow of things in certain environments
46. 00:02:24:78 / 00:02:28:37 - so it's definitely worth kind of like
47. 00:02:26:66 / 00:02:33:53 - I'm playing around with this a bit
48. 00:02:28:37 / 00:02:37:07 - the default is one hour okay so give it
49. 00:02:33:53 / 00:02:39:37 - a shot hopefully it helps thank you for
50. 00:02:37:08 / 00:02:39:38 - watching
Visit our YouTube channel: https://www.youtube.com/channel/UCFj1BHYIUYfPWPb1Xn5qFIg