Configuring a Traffic Management Policy
Full-Access Members Only
Sorry, this lesson is only available to Server Academy Full-Access members. Become a Full-Access member now and get instant access to this and many more premium courses. Click the button below and get instant access now.
Instructions
Q&A (0)
Notes (0)
Resources (0)
Saving Progress...
Resources
There are no resources for this lesson.
Notes can be saved and accessed anywhere in the course. They also double as bookmarks so you can quickly review important lesson material.
Scenario
There is a company called Server Academy, that markets online IT courses.
The company has two locations one in Canada and one in the US.
Corporate in the US has asked that customers coming in from the US would be directed to the US site, and customers coming in from Canada would be directed to the Canadian site.
How would you implement this?
Please note: This is an example of policy creation that is based upon the settings in this example. Your settings will be different and based upon your infrastructure.
Here an example of DNS Name Resolution
A user called US client tries to access the site www.sa.com.
This results in a DNS name resolution request sent to the Local DNS server.
This local server doesn’t know about www.sa.com, so the local DNS server forwards the query to the server that is Authoritative for www.sa.com.
The sa.com server responds back to the Local DNS server with the A record for
www.sa.com, which then caches the response, then sends the A record to the US client Computer.
Because the DNS server that is authoritative for sa.com has been configured using a Network Traffic Management Policy based upon location.
This results in US Clients being directed to the US Data Center and the Canadian
customers being directed to the Canadian data center.
We’ll Follow these four Steps when creating our Traffic Management Policy
- Step #1, DNS Client Subnets - A client subnet is an object that represents an IPv4 or IPv6 subnet.
You will configure one client subnet for each location.
- Step #2, Zone Scopes - A Zone Scope is a method of partitioning or dividing a DNS zone. You will configure two Zone scopes, one for each location.
- Step #3, Add resource Records – We will be adding A- host records to each Zone Scope
- Step #4, Create DNS Policies – In this example, we will create two Query Resolution Policies. Which determines how DNS queries are handled by the criteria that you specify in the policy.
Now Let’s jump over to our DNS server and open server manager. Click Tools, then DNS manager. What I wanted to show you was for the server ITFDC01, there hasn’t been a forward lookup zone created yet. So, that’s the first thing we are going to do using Powershell.
Let’s go ahead and open PowerShell and create our policy.
As we discussed in our example, there are four steps we’ll need to complete to create our
policy. So, I have created a script with all the commands to create our Traffic Management policy
What we have here is our four steps.
- Step 1 This command creates our client subnets
- Step 2 This command creates the zonescopes
- Step 3 This command will add our A records to each zonescope
- Step 4 This command will create the policies.
As we talked about before we need to create a primary zone called sa.com
- Add-DnsServerPrimaryZone -Name sa.com -ZoneFile sa.com.dns
- Which is located on the DNS server in windows DNS server in C:\windows\system32\dns
Step 1 Creating DNS Client Subnets
This command creates the client subnet’s for the US subnet.
- Add-DnsServerClientSubnet – Name “USSubnet” – Ipv4Subnet “192.168.3.0/24”
Now we’ll create a client subnet for the Canadian subnet
To create the client subnet’s for the Canadian subnet, use this command
- Add-DnsServerClientSubnet – Name “CASubnet” – Ipv4Subnet “192.168.17.0/24”
Step 2 This command creates the Zone Scope’s for the US side.
Server Academy Members Only
Sorry, this lesson is only available to Server Academy Full Access members. Become a Full-Access Member now and you’ll get instant access to all of our courses.
