And to begin with, we're integrating DNS with Active Directory Domain Services.
Just by way of review,
we're not doing a full‑scale workup of DNS and Windows Server DNS,
that's assumed knowledge.
Hopefully you already have it,
but check the Pluralsight library for fundamental
Windows Server training if you need it.
But recall that DNS is this global directory of hostname to IP address mappings.
And in the DNS zone file we have a number of resource record types.
There's the start of authority, or SOA, record that provides zone metadata,
replication data, etc.
Your authoritative name servers for your zones have NS records,
name server records.
Each host in your environment,
this host could reference a server or an application,
whatever, it's either going to be A or AAAA.
A is an IPv4 host IP address mapping, AAAA, or quad A, is an IPv6.
Canonical name is an alias record where you can map a
hostname to another hostname in your zone.
Active Directory being a Lightweight Directory Access Protocol,
or LDAP, identity store uses SRV,
or service location records to advertise hosted
services within Active Directory,
and that makes it easier for your client devices to find those services.
MX is mail exchange, that's obviously for your communication servers.
TXT records are normally used for domain verification,
You'll use TXT or MX to verify to Azure that you own a domain,
for example.
If you're looking to route the top of your zone,
company.com let's say, that's called the apex route,
you can use ANAME records for that.
PTR are reverse lookup records. Instead of domain name or hostname
to IP address, when you create a pointer zone,
it does just the opposite where you can resolve a fully‑qualified
domain name for a resource starting with its IP address.
Now there's some other DNS resource records,
but these are the most common and directly pertinent to what we're doing in this training.