Domain 4 of 5 · Chapter 3 of 3

Configure name resolution and load balancing

Unlock the complete study guide + 25 practice exams totaling 1,497 questions.

Bundled into the existing Microsoft Azure Administrator premium course — no separate purchase.

14-day refund guarantee on one-time purchases and your first subscription charge.

Included in this chapter:

  • Public DNS zones and delegation
  • Record sets: names, TTL and coexistence rules
  • Choosing a record type
  • Alias records
  • Moving a zone into Azure DNS
  • Tags and metadata
  • Etags: protection against concurrent changes
  • DNSSEC zone signing
  • Reverse DNS for your ranges and for Azure public IPs
  • Private DNS zones and virtual network links
  • Which DNS servers a virtual network uses
  • Azure DNS Private Resolver
  • Azure Load Balancer components
  • Load Balancer frontends: public or internal
  • Backend pools
  • Inbound rules: load-balancing, HA ports and inbound NAT
  • Settings on a load-balancing rule
  • Outbound rules and SNAT ports
  • Health probes: protocol, timing and source
  • When a backend fails its probe
  • Troubleshooting load balancing
  • Migrating from Basic Load Balancer

Azure Load Balancer rule types

Load-balancing ruleHA ports rule (a load-balancing rule on all ports)Inbound NAT ruleOutbound rule
Traffic directionInboundInboundInboundOutbound, started by backend instances
Where traffic goesAny healthy instance in the backend poolAny healthy instance, on every portOne specific VM or instanceFrom the backend pool out through the frontend public IPs
PortsOne frontend port to one backend portProtocol All, port 0One frontend port to that instance's portSNAT ports allocated per instance
Health probeRequiredRequired; one response must reflect the whole instanceNot requiredProbe failure does not affect outbound
Typical useA web tier across several VMsNetwork virtual appliances behind an internal load balancerRDP or SSH to one VMExplicit internet egress for backend VMs

Decision tree

Traffic started bya backend VM?YesOutboundruleNoOne frontend portto one specific VM?YesInbound NATruleNoAll ports for aninternal NVA pool?YesHA portsruleNoLoad-balancing rule

Cheat sheet

  • Public DNS hosting becomes authoritative through parent-zone delegation
  • A child zone is delegated by an NS record set in its parent
  • Records with the same name and type share one Azure DNS record set and TTL
  • A CNAME follows a hostname but cannot coexist with other records at that name
  • Azure DNS aliases follow supported Azure resources and avoid dangling resource references
  • DNS record types encode different addressing, mail, and service-discovery requirements
  • Zone-file import merges records and preserves Azure's assigned apex name servers
  • Wildcard DNS records cover unmatched names rather than overriding explicit names
  • Public DNS capacity and TXT text length impose different limits
  • DNSSEC signing needs parent delegation trust and a validating resolver to authenticate answers
  • CAA tags separate general certificate issuance, wildcard issuance, and incident reporting
  • DNS zones support ARM tags while record sets use separate metadata annotations
  • Azure-owned public IPv4 reverse mappings are configured on the public IP rather than in a customer reverse zone
  • DNS Etags protect concurrent edits by checking the retrieved resource version
  • Azure DNS protects apex authority records while leaving selected properties editable
  • Public and private zones can share a name while returning different answers
  • Private DNS links enable resolution without creating a network traffic path
  • A virtual network can resolve multiple private zones but autoregister in only one
  • Private DNS autoregistration maintains primary-NIC VM A records rather than all resource records
  • Custom DNS settings replace Azure's default resolver path and require client refresh
  • Private Resolver inbound and outbound endpoints serve opposite DNS directions
  • Private Resolver uses linked private zones before suffix-matched forwarding rules
  • Private Resolver endpoints require separate delegated subnets in the resolver's network
  • Private Link zone fallback retries public resolution only after a private NXDOMAIN answer
  • Public and internal Load Balancer frontends serve different client reachability requirements
  • A regional Load Balancer's backend pool groups eligible instances in one virtual network
  • Load-balancing rules distribute service traffic while inbound NAT rules select an instance
  • Load Balancer persistence changes which flow fields determine backend selection
  • HA ports load-balance many transport ports through one internal Standard rule
  • Floating IP enables backend-port reuse and requires matching guest configuration
  • An outbound rule explicitly shares public frontend addresses across backend egress flows
  • Manual SNAT allocation must fit the frontend port budget and backend growth
  • Load Balancer idle timeout and TCP reset are rule-specific connection controls
  • Load Balancer frontend zone resilience and backend zone distribution are configured independently
  • Basic Load Balancer migration requires a validated Standard rebuild and a planned one-way cutover
  • An internal Load Balancer frontend supports dynamic or selected static private addressing
  • Probe protocol determines whether health means a listening socket or a successful application response
  • Probe permission and application-client permission must both be verified
  • Probe failure stops new connections without automatically terminating established TCP flows
  • Probe intervals and thresholds control detection, with immediate HTTP status decisions
  • Data Path Availability and Health Probe Status diagnose different parts of availability
  • Default SNAT allocation shrinks as the backend pool grows
  • SNAT exhaustion can block one backend's new connections while other port capacity remains unused
  • Load Balancer hashes flows rather than guaranteeing equal requests or bytes per backend
  • Load Balancer tests must distinguish the frontend path from the backend listener

Unlock with Premium — includes all practice exams and the complete study guide.

References

  1. https://learn.microsoft.com/en-us/azure/dns/dns-zones-records
  2. https://learn.microsoft.com/en-us/azure/dns/dns-delegate-domain-azure-dns
  3. https://learn.microsoft.com/en-us/credentials/certifications/resources/study-guides/az-104
  4. https://learn.microsoft.com/en-us/azure/dns/delegate-subdomain
  5. https://learn.microsoft.com/en-us/azure/dns/dnssec
  6. https://learn.microsoft.com/en-us/azure/dns/dns-reverse-dns-for-azure-services
  7. https://learn.microsoft.com/en-us/azure/dns/dns-alias
  8. https://learn.microsoft.com/en-us/azure/dns/dns-import-export
  9. https://learn.microsoft.com/en-us/azure/dns/dnssec-how-to
  10. https://learn.microsoft.com/en-us/azure/virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances
  11. https://learn.microsoft.com/en-us/azure/dns/dns-reverse-dns-hosting
  12. https://learn.microsoft.com/en-us/azure/dns/private-dns-overview
  13. https://learn.microsoft.com/en-us/azure/dns/private-dns-virtual-network-links
  14. https://learn.microsoft.com/en-us/azure/dns/private-dns-autoregistration
  15. https://learn.microsoft.com/en-us/azure/dns/private-dns-fallback
  16. https://learn.microsoft.com/en-us/azure/dns/dns-private-resolver-overview
  17. https://learn.microsoft.com/en-us/azure/dns/private-resolver-endpoints-rulesets
  18. https://learn.microsoft.com/en-us/azure/load-balancer/load-balancer-overview
  19. https://learn.microsoft.com/en-us/azure/load-balancer/components
  20. https://learn.microsoft.com/en-us/azure/virtual-network/network-security-groups-overview
  21. https://learn.microsoft.com/en-us/powershell/module/az.network/add-azloadbalancerfrontendipconfig
  22. https://learn.microsoft.com/en-us/azure/reliability/reliability-load-balancer
  23. https://learn.microsoft.com/en-us/azure/load-balancer/load-balancer-custom-probe-overview
  24. https://learn.microsoft.com/en-us/azure/load-balancer/load-balancer-outbound-connections
  25. https://learn.microsoft.com/en-us/cli/azure/network/lb/rule
  26. https://learn.microsoft.com/en-us/azure/load-balancer/inbound-nat-rules
  27. https://learn.microsoft.com/en-us/azure/load-balancer/outbound-rules
  28. https://learn.microsoft.com/en-us/azure/load-balancer/distribution-mode-concepts
  29. https://learn.microsoft.com/en-us/azure/load-balancer/load-balancer-floating-ip
  30. https://learn.microsoft.com/en-us/azure/load-balancer/load-balancer-tcp-reset
  31. https://learn.microsoft.com/en-us/azure/virtual-network/what-is-ip-address-168-63-129-16
  32. https://learn.microsoft.com/en-us/azure/load-balancer/load-balancer-standard-diagnostics
  33. https://learn.microsoft.com/en-us/azure/load-balancer/load-balancer-basic-upgrade-guidance