WEBVTT 00:00.180 --> 00:09.450 On this slide we have the information about recursive and interactive querist even more information 00:09.450 --> 00:11.220 about this Querist. 00:11.310 --> 00:18.010 I've mentioned them in previous slides but here we can see even more information. 00:18.240 --> 00:27.990 So in a recursive query DNS server receiving the name resolution Reclast takes full responsibility for 00:27.990 --> 00:36.420 resolving the name in interactive Querrey the server that receives the name resolution request immediately 00:36.480 --> 00:40.260 response for the best information it possesses. 00:40.290 --> 00:48.350 So if it doesn't care for information on this request it immediately response that it doesn't have. 00:48.450 --> 00:59.940 Please ask some other DNS server please note that in most cases it would be improper to configure one 00:59.940 --> 01:05.010 DNS server to send a recursive query to another DNS server. 01:05.280 --> 01:15.840 It only can happen when we configure forwarder than this forwarder is responsible for all querist from 01:15.930 --> 01:23.880 other DNS servers to some external for example resources. 01:23.880 --> 01:26.830 Think about forwarder as Ayahs. 01:26.850 --> 01:30.970 PS DNS server 01:34.460 --> 01:42.430 one of the scenarios in which DNS servers Samter recursive queries to other DNS servers is when you 01:42.430 --> 01:49.180 configure server to function as a forwarder on a network run in several DNS servers. 01:49.180 --> 01:57.700 You might not want all this sort of sand and querist to other DNS servers in the Internet. 01:57.790 --> 02:05.790 If the network has a relatively slow connection to the Internet for example several Suroosh with meet 02:05.800 --> 02:14.670 in repeated Guerreros my queues to march of the available bandwidth to prevent this. 02:14.670 --> 02:24.480 The Windows DNS server enables you to configure one server to function as a forwarder for all Internet 02:24.510 --> 02:29.730 queries generated by the other servers on the network. 02:29.730 --> 02:36.570 Now let's look through those types Leora size zone types in Windows or on DNS. 02:36.560 --> 02:44.880 Primaries alone secondary's alone and Stobbs all primaries all creates a primary zone that contains 02:44.970 --> 02:52.820 the master copy of the zone database where admin and administrators make all changes to the zones Russos 02:52.830 --> 02:53.780 records. 02:53.910 --> 03:02.280 If a zone is not stored in the active directory the server creates a primary Mostert zone database file 03:02.700 --> 03:04.410 on the local drive. 03:04.410 --> 03:13.620 So this file is stored on a local drive and it has its address and you can configure and change this 03:13.620 --> 03:18.480 file to update primer is. 03:18.790 --> 03:29.540 But it is much more simple when you have a D integrated zone who will talk about it later. 03:29.540 --> 03:36.020 What other benefits are the advantages of keeping the ozone Adium to great secondaries alone. 03:36.030 --> 03:44.420 Is it's just the copy of primary zone which is kept on another server and it is updated when the primary 03:44.420 --> 03:45.970 zone is updated. 03:47.420 --> 03:58.630 So it is only Read-Only corporate and it is nice to only when the primary zone is changed Stobbs zone 03:58.910 --> 04:16.770 just contains the key resource records and when there is a request for some information you just forwards 04:16.920 --> 04:25.710 the request to the host of The Zone or replies with a referral to that host depending on whether the 04:25.710 --> 04:35.050 query is recursive or iterative even more information about zone types her primary zone DNS zone is 04:35.050 --> 04:44.080 required for DNS functionality and name resolution for of any domain name and primary DNS zone is both 04:44.500 --> 04:53.980 authoritative for the zone and the primary point of storage for the secondary zone is not required and 04:54.070 --> 05:03.020 not authoritative but are useful to read Usenet for traffic and provide foster name resolution especially 05:03.260 --> 05:07.850 not use in an active directory integrated primary. 05:09.510 --> 05:12.220 Use an active directory integrated zones. 05:12.280 --> 05:23.710 So there are quite many advantages of using integrated zones instead of file based loans. 05:23.900 --> 05:36.140 So this advantages are the conservation of network bandwidth and increased security zone files are replicated 05:36.230 --> 05:37.500 automatically. 05:39.230 --> 05:50.880 Along with all our other domain control as in demand and active directory data you can modify the DNS 05:50.880 --> 06:00.100 resource records on and the right to build domain controller host and a cold of the zone data and active 06:00.100 --> 06:05.980 directory will automatically update all the other domain controllers. 06:05.980 --> 06:13.570 You don't have to create secondary's zones or manually configure zone transfers because Active Directory 06:13.670 --> 06:18.240 performs all database replication activities. 06:18.260 --> 06:26.140 You can also create a custom replication scope that copies the database to the domain controllers you 06:26.250 --> 06:35.230 specify Active Directory conserves net for bandwidth by your application only the DNS data that has 06:35.230 --> 06:38.260 changed since the last replication. 06:38.290 --> 06:48.920 And by compressing the data before transmitted over the Internet the zone replications also use the 06:48.920 --> 06:57.920 Fool's security capabilities of active directory including encryption and Kerberos based authentication 06:58.880 --> 07:03.990 which is more a lost than loss of file based loan transfers. 07:04.860 --> 07:10.170 DNS records there are a number of records which are used in DNS. 07:10.170 --> 07:20.430 We'll take a look at most commonly used records such as host tracker or a record a record is used in 07:20.520 --> 07:22.040 IP version 4. 07:22.230 --> 07:31.830 And what a record this is pronounced as what a record is used in the IP version 6. 07:31.880 --> 07:37.750 This record resolves a particular name to an IP address. 07:37.770 --> 07:41.170 Note that the records are self-created. 07:41.190 --> 07:49.020 When the machine is joint to the domain when the machine is not joined to the domain you have to add 07:49.110 --> 07:55.380 the records manually and configure the file. 07:55.520 --> 08:02.300 The DNS file the next record is LS record to see Name records. 08:02.450 --> 08:09.240 This is a record that you can create which takes a name and points to another name. 08:09.260 --> 08:15.360 An example is of one long record which points to one shot record. 08:15.410 --> 08:21.520 For example long name pointing to the name just where 08:25.360 --> 08:34.370 that good then the the next record is mail exchange or mix record and then mix record tells the domain 08:34.760 --> 08:46.160 where to point for its email services name servers name server or unearths record points which DNS server 08:46.490 --> 08:55.000 to use as authority for long and the last one is part of a sort. 08:55.050 --> 08:57.600 Or as a record. 08:57.720 --> 09:05.230 This record indicates that the server is the best authoritative source for data concerning the zone 09:06.330 --> 09:08.930 each zone must have. 09:09.190 --> 09:21.600 And C as o a record and only one as a record can be in a zone only only one record and the last slide 09:21.600 --> 09:31.220 is about tools and utilities which can help when troubleshooting DNS related issues. 09:31.290 --> 09:34.510 The first tool to use is IP config. 09:35.590 --> 09:36.120 To. 09:36.200 --> 09:43.410 Sorry I'll take apan I become fake with Slash Fleisch DNS. 09:43.410 --> 09:52.920 This forces the client to destroy its locally cast cast copies of DNS resolver records and gets new 09:52.920 --> 10:02.340 information that is current from the DNS server which is always helpful when you have a new record and 10:02.400 --> 10:12.900 you cannot resolve this record from the server because your client gets the information from locally 10:12.930 --> 10:21.510 cached corpus of DNS server and another one is epicanthic display DNS. 10:21.510 --> 10:30.920 This shows the contents of your local DNS cache and you can view all the contents with this utility. 10:31.010 --> 10:39.650 This command system administrator sulfonylureas and asked to look up to. 10:39.650 --> 10:45.690 This is very good and robust to event viewer. 10:45.830 --> 10:56.160 NET mourner's troll for network information on the server DNS as M.D And of course being resolved pinna 10:56.230 --> 11:00.870 we cannot know if the server is available and is reached. 11:00.980 --> 11:05.160 So is the first tool which should be used. 11:05.180 --> 11:08.610 You can always get more information on the Internet. 11:08.660 --> 11:13.340 This links are the ones which I've used to prepare these slides. 11:13.340 --> 11:17.000 So take a look and maybe they could be of use for you.