Azure DNS

Private DNS Resolver service

  • Inbound (just an IP) and Outbound endpoint
  • My on prem DNS can forward to inbound endpoint (which is just an IP)
  • Forwarding rule sets can be created to resolve in Azure my onprem DNS
    • Can be linked to different VNets

Dangling DNS

  • Create an alias to a resource
  • After time resource is deleted
  • But alias still points to it
  • Bad actor can create a service with the same record name
  • So now my alias points to bad actor’s service

split horizon scenario


references:

MS Learn

  • A is the host record, and is the most common type of DNS record. It maps the domain or host name to the IP address.
  • CNAME is a Canonical Name record that’s used to create an alias from one domain name to another domain name. If you had different domain names that all accessed the same website, you’d use CNAME.
  • MX is the mail exchange record. It maps mail requests to your mail server, whether hosted on-premises or in the cloud.
  • TXT is the text record. It’s used to associate text strings with a domain name. Azure and Microsoft 365 use TXT records to verify domain ownership.

Additionally, there are the following record types:

  • Wildcards
  • CAA (certificate authority)
  • NS (name server)
  • SOA (start of authority)
  • SPF (sender policy framework)
  • SRV (server locations)

Enable Auto-registration

Subscribe to NordLetter

A weekly newsletter on living in Finland.

UPDATED