Resolve names with DNS Private Resolver
- Make stlogs01.blob.core.windows.net resolve to 10.0.3.4 from vm-spoke1
- Make app.corp.contoso.com resolve to 192.168.10.5 from vm-spoke1
The hub has an Azure DNS Private Resolver, dnspr-hub, with an inbound endpoint at 10.0.5.4 and a ruleset, rs-onprem, linked to the hub. Use it for two things: private endpoint names for vm-spoke1, like stlogs01 at 10.0.3.4, and the on-premises zone corp.contoso.com, which lives on dns-onprem at 192.168.10.10. app.corp.contoso.com is srv-onprem.
See the inbound endpoint and its IP.
az dns-resolver inbound-endpoint list -g rg-lab --dns-resolver-name dnspr-hub -o tableWhat's this?
Shows a DNS Private Resolver's inbound endpoints and their IP addresses.
-gthe resource group the resources live in
Use it as vnet-spoke1's DNS server.
az network vnet update -g rg-lab --name vnet-spoke1 --dns-servers 10.0.5.4What's this?
Changes a virtual network, such as its address space or the DNS servers its VMs use.
-gthe resource group the resources live in--namethe name of the thing to look at or change
Add a rule that sends corp.contoso.com to the on-premises DNS server.
az dns-resolver forwarding-rule create -g rg-lab --ruleset-name rs-onprem --name corp --domain-name corp.contoso.com. --target-dns-servers "[{ip-address:192.168.10.10,port:53}]"What's this?
Works with a forwarding rule: queries for one domain go to the DNS servers you name. It applies in networks linked to the rule's ruleset. If two rules match, the longer domain wins.
-gthe resource group the resources live in--namethe name of the thing to look at or change
--domain-name corp.contoso.com.note the trailing dot--target-dns-serverswhere matching queries go
Connect to vm-spoke1.
ssh vm-spoke1What's this?
Opens a shell on vm-spoke1, so the next commands run on that VM. In this lab it's a shortcut. In real Azure you'd connect through something like Azure Bastion, or SSH to an address you can reach.
Look up the private endpoint name.
nslookup stlogs01.blob.core.windows.netWhat's this?
Asks the VM's DNS server what IP address a name points to. Run it on the VM that has the problem, because each VM can get a different answer.
Look up the on-premises name. Type exit when done.
nslookup app.corp.contoso.comWhat's this?
Asks the VM's DNS server what IP address a name points to. Run it on the VM that has the problem, because each VM can get a different answer.
Answer the question below.
Sources on Microsoft Learn (2)
?
- Resource group, the outer dashed frame
- Virtual network, with its address space top right
- Subnet, with range and usable IPs (5 reserved)
- Network security group. A small shield on a VM's NIC means the NIC has one too
- Route table on the subnet
- VM Appliance Private endpoint
- Peering Connected Initiated or access off
- Goal working Goal broken, X marks where it stops
- Private DNS zone, dotted lines go to linked VNets
- Orange pulse: what your last command changed. Drag to pan, Ctrl and scroll to zoom.
vm-spoke1 → app.corp.contoso.com:443should work: not working