Sunday, November 9, 2014

MCSE Studying - Week 24

Overview
Week 24 of my MCSE studies has been quite busy. I enrolled in, and attended three Live Learning courses from KnowledgeNet, finished another chapter in the 70-411 Training Guide, and listened to two episodes of the PowerScripting Podcast. I am quite tired, but I've have had a great week!

Cool Stuff
The coolest thing was not chosen because of it's wonderful new features, it's flashy new GUI, or even it's new wonderfully feature-rich command line tools. In fact, it has none of those things. It was chosen, because I finally understand how it works after more than a decade of searching for a clear answer. What did I learn? How the No-refresh Interval and the Refresh Interval affect DNS Aging and Scavenging.

In a nutshell, here's the grossly simplified explanation of how I now understand it works:

  1. The DNS client registers it's name with the DNS server, which adds it to the DNS zone and time stamps the record.
  2. During the No-Refresh Interval (7 days by default), the DNS server will not allow the client to refresh it's time stamp if there aren't any changes, but it will allow the client to update the record and the time stamp if there are changes.
  3. The Refresh Interval (7 days by default) starts as soon as the No-Refresh Interval expires. During this period, the client can refresh it's DNS record, and resets the time stamp.
  4. During the next scavenging interval, the DNS server compares the current time with (Time stamp+No-Refresh Interval+Refresh Interval). If the value of the calculation is less than the current time, the record is removed from the zone.
This is the link to the TechNet article that made everything clear for me:
Understanding Aging and Scavenging

If you find any errors in my understanding, by all means, feel free to correct me before I write this transaction to the database of my long-term memory.

PowerShell cmdlet of the Week
This week I think I'll choose a pair of useful cmdlets that are related to DNS Scavenging.

Get-DNSServerScavenging

This cmdlet, when run by itself, will get the current DNS server's scavenging settings, including NoRefreshInterval, RefreshInterval, ScavengingInterval, ScavengingState, and LastScavengeTime. You can add the -ComputerName parameter to run it against a remote DNS Server.

Set-DNSServerScavenging

This cmdlet will allow you to set the properties for aging and scavenging on the local, or a remote DNS server. Say for example, you wanted to turn on aging and scavenging on a DNS server named titan-dc01 for all zones hosted on that server, with a scavenging interval of 1 day.

Set-DNSServerScavenging -ComputerName titan-dc01 -ScavengingState $true -ScavengingInterval 1.00:00:00 -ApplyOnAllZones

Easy!

Stats
Total time studying: 24 hrs. 35 min.
  • PowerShell: 2 hrs. 45 min.
  • 70-411: 10 hrs. 20 min.
  • 70-413: 5 hrs. 30 min.
  • 70-341: 6 hrs.
Resources used:


In Closing
It has been a fantastic week for studying! I have had a great time, and learned a lot. I did tire myself out, but it was totally worth it.

I decided to take a couple of extra courses this month. The first being for exam 70-341, Core Solutions of Microsoft Exchange Server 2013. I decided to take this one, since I have absolutely no knowledge of Exchange Server. This was due to the fact that I have spent the last 14 years in a Lotus Notes/Lotus Domino Server environment.

The second course is one I will need for my MCSE, and that is the 70-413: Designing and Implementing a Server 2012 R2 Infrastructure. This is a course that is heavy on design and sometimes tests the limits of my understanding of Windows Server. I did have a fun experience with this course on Tuesday; I was the only student in class. I did enjoy this, but I am glad a few more students were there on the Thursday class, so there was a little more discussion and interaction.

I am looking forward to next week's studies, and the chance to get back into the field. I have a small job to do over the next couple of weeks, and I am looking forward to getting out of the house and doing some work in a production environment vs. a lab.

Have a great week everyone!

No comments: