Azure DNS versus bringing your own DNS into Azure will be discussed including use cases to help you determine which option to choose from. Configured DNS in a virtual network will also be demonstrated.
- [Speaker] DNS. The telephone book of the internet. DNS matches the computer name to the IP address. In Azure, we have three DNS options. First is Azure DNS. And here, I'm referring to name resolution. Not the Azure domain name system. The hosting service. We'll touch on that in a moment. Azure DNS is a service that provides naming for your virtual machines to communicate. It is built into Azure. You do not have to configure it. Azure DNS is incredibly easy to use.
It's already there and configured for you. You don't really have to do anything. It is highly available. And you never have to worry about DNS servers. And fully qualified domain names, or FQDN, are not required in ARM. But there are a few things you need to be aware of if you're going to use Azure DNS. First of all, your DNS suffix cannot be modified. It is what it is. And you can't change it. WINS and NetBIOS are not supported in Azure DNS. And you cannot manually register records at all.
I find Azure DNS tends to be a great option for testing dev, or for proof of concept. But if that's not enough for you. You can definitely bring your own DNS. And typically you'd bring your own DNS when you're looking at a hybrid connectivity. Whether that's connecting Azure virtual machines to your on-premise environment, or Azure virtual machines in different networks. If you need to authenticate to a DC, you're going to need to bring your own DNS. Or if you need to have reverse lookup of internal IPs, bringing your own DNS is your only option.
But there are a few things you need to be aware of. First of all, you have to turn off scavenging. Because of the long leases that are assigned to Azure virtual machines. You must enable DNS recursion. And this DNS server must be available on port 53 for all your clients who are connecting in. You have to provide the host name resolution. And finally, just as we do on premise, you need to secure it. And finally, our Azure DNS hosting. This is out of scope for this course. But just to give you heads up on what it is.
Azure DNS hosting became generally available in 2015. And here, you can host DNS domains. The DNS hosting provides name resolution using the Microsoft global servers. And you must already own the domain. So if you do not want to use one of the typical registers for your DNS hosting. You can definitely do an Azure. But you will need to purchase that domain name, through that register. Now that we've covered the basics of DNS. Let's take a look at it. I'm back in a virtual network's resource group.
And to set up a DNS server is really simple to do. But you have to add the IP address of the DNS server into the virtual network. So within our production virtual network, I want to notate the IP address of my DC, which is hosting my DNS. So I'm at one nine two one six eight dot zero dot 68. Next, I'm simply going to click DNS servers. And choose custom. And now I'm just going to add that DNS server. I believe it was 68. You can have up to 12 DNS servers within your virtual network.
And you'll want to input them in the order that they will be referenced. I like to point out this warning up at the top: virtual machines within this network must be restarted to utilize the updated DNS server settings. Remember the word planning? This is again where it comes into play. If you go ahead and create your virtual network, build out all your VNs and then add in your DNS server. You are going to have to reboot every one of those virtual machines. My suggestion is configure your DNS server.
Add the DNS server into your virtual network. And then start provisioning all your virtual machines. At that point, they will grab the DNS server number for you. One further caution, back in the day of our on-premise servers, we go into the network settings and add in the DNS IP address. You can do that here but it's not recommended. If a network interface changes, those settings will be lost. So it's just good habit, just not to do it. And there you have it. DNS servers for Azure.
You can use the Azure DNS that's provided to you. You can bring your own Azure DNS. Or you can leverage the Azure DNS hosting service.
- Creating an Azure virtual network
- Creating a virtual network using PowerShell
- Deploying a VM into a virtual network
- Modifying IP addresses
- Working with Azure DNS
- Configuring NSGs
- Setting up load balancers
- Configuring Azure load balancers
- Creating an application gateway
- Setting up on-premises connectivity
- Adding gateway VPNs
- Validating VPN devices
- Configuring VNet
- Creating site connections