1
00:00:00,840 --> 00:00:06,240
And to begin with, we're integrating DNS with Active Directory Domain Services.

2
00:00:06,240 --> 00:00:07,650
Just by way of review,

3
00:00:07,650 --> 00:00:12,700
we're not doing a full‑scale workup of DNS and Windows Server DNS,

4
00:00:12,700 --> 00:00:14,070
that's assumed knowledge.

5
00:00:14,070 --> 00:00:15,560
Hopefully you already have it,

6
00:00:15,560 --> 00:00:18,460
but check the Pluralsight library for fundamental

7
00:00:18,460 --> 00:00:20,350
Windows Server training if you need it.

8
00:00:20,350 --> 00:00:27,040
But recall that DNS is this global directory of hostname to IP address mappings.

9
00:00:27,040 --> 00:00:31,330
And in the DNS zone file we have a number of resource record types.

10
00:00:31,330 --> 00:00:36,030
There's the start of authority, or SOA, record that provides zone metadata,

11
00:00:36,030 --> 00:00:37,900
replication data, etc.

12
00:00:37,900 --> 00:00:42,590
Your authoritative name servers for your zones have NS records,

13
00:00:42,590 --> 00:00:43,620
name server records.

14
00:00:43,620 --> 00:00:45,580
Each host in your environment,

15
00:00:45,580 --> 00:00:48,770
this host could reference a server or an application,

16
00:00:48,770 --> 00:00:51,850
whatever, it's either going to be A or AAAA.

17
00:00:51,850 --> 00:00:57,750
A is an IPv4 host IP address mapping, AAAA, or quad A, is an IPv6.

18
00:00:57,750 --> 00:01:01,520
Canonical name is an alias record where you can map a

19
00:01:01,520 --> 00:01:04,510
hostname to another hostname in your zone.

20
00:01:04,510 --> 00:01:08,170
Active Directory being a Lightweight Directory Access Protocol,

21
00:01:08,170 --> 00:01:11,270
or LDAP, identity store uses SRV,

22
00:01:11,270 --> 00:01:14,760
or service location records to advertise hosted

23
00:01:14,760 --> 00:01:16,700
services within Active Directory,

24
00:01:16,700 --> 00:01:20,790
and that makes it easier for your client devices to find those services.

25
00:01:20,790 --> 00:01:25,290
MX is mail exchange, that's obviously for your communication servers.

26
00:01:25,290 --> 00:01:28,780
TXT records are normally used for domain verification,

27
00:01:28,780 --> 00:01:34,550
You'll use TXT or MX to verify to Azure that you own a domain,

28
00:01:34,550 --> 00:01:35,330
for example.

29
00:01:35,330 --> 00:01:38,040
If you're looking to route the top of your zone,

30
00:01:38,040 --> 00:01:41,720
company.com let's say, that's called the apex route,

31
00:01:41,720 --> 00:01:44,020
you can use ANAME records for that.

32
00:01:44,020 --> 00:01:49,490
PTR are reverse lookup records. Instead of domain name or hostname

33
00:01:49,490 --> 00:01:52,260
to IP address, when you create a pointer zone,

34
00:01:52,260 --> 00:01:55,570
it does just the opposite where you can resolve a fully‑qualified

35
00:01:55,570 --> 00:01:58,740
domain name for a resource starting with its IP address.

36
00:01:58,740 --> 00:02:01,190
Now there's some other DNS resource records,

37
00:02:01,190 --> 00:02:07,000
but these are the most common and directly pertinent to what we're doing in this training.