1
00:00:06,460 --> 00:00:14,950
When users sign into Active Directory their computers look and ask for as real records to locate the

2
00:00:14,950 --> 00:00:22,800
nearest domain controller a records specify information about available services e.g. domain controller

3
00:00:22,840 --> 00:00:31,980
dynamically registers its addresses in DNS and it's doing it at Star top by registering and updated

4
00:00:31,980 --> 00:00:34,130
it service record in DNS.

5
00:00:34,180 --> 00:00:42,910
Clients can locate a suitable domain controller to service they are assigned a request by using DNS

6
00:00:42,980 --> 00:00:51,140
lookups which use these as their real records as a real records for ADT is follow the follow in Room

7
00:00:51,260 --> 00:00:58,230
from underscore service dot underscore protocol dot domain name.

8
00:00:58,270 --> 00:01:06,190
For example if a client is looking for a server that is running the light way direct or access protocol

9
00:01:06,190 --> 00:01:11,440
or held up service in the a datum dot com domain.

10
00:01:11,440 --> 00:01:18,050
It queries for El derp dot underscore to speed dot a datum dot com.

11
00:01:18,130 --> 00:01:23,540
I plan to use these sites when it needs to contact the demand controller.

12
00:01:23,560 --> 00:01:27,810
It starts by looking up as the records in DNS.

13
00:01:27,820 --> 00:01:35,350
The response to the DNS query includes a list of the domain controllers on the same side as the client

14
00:01:35,600 --> 00:01:39,550
a list of domain controllers from the next closest site.

15
00:01:39,640 --> 00:01:42,710
That does not include two marauders.

16
00:01:42,970 --> 00:01:51,000
If no domain controllers were available in the same site and try and next closes site group policy set

17
00:01:51,040 --> 00:01:57,710
and is enabled and it includes a random list of available domain controller in the domain.

18
00:01:57,940 --> 00:02:06,310
If there is no domain controller is the next closest site administrators can define sites in 80 days.

19
00:02:06,400 --> 00:02:14,760
When you define sites you should consider which parts of the network have good connectivity and bandwidth.

20
00:02:14,770 --> 00:02:23,230
For example if a branch office connects to the domain datacenter through an unreliable wide area network

21
00:02:23,230 --> 00:02:28,680
link you should define the branch office and the data center as separate sites.

22
00:02:28,690 --> 00:02:36,220
The net logon service that runs on each domain controller registers as service records in DNS.

23
00:02:36,260 --> 00:02:43,870
If there is a real records are not turned or in DNS correctly you can trigger the domain controller

24
00:02:43,870 --> 00:02:51,820
to register those records by restarting the net logon service on that domain controller.

25
00:02:51,900 --> 00:03:00,250
Note that this process reregister as only the service records if you want to register the host.

26
00:03:00,250 --> 00:03:02,700
Record information in DNS.

27
00:03:02,740 --> 00:03:11,320
You must run a pick on fake slash registered DNS command from a command prompt just as you would for

28
00:03:11,380 --> 00:03:12,970
any other computer.