Feel free to donate to help support PCTechStream.com Thank you so much to all of those who have contributed!

04 - DNS Tutorial Overview.
Creating reverse lookup zones and zone type (standard secondary)
A reverse lookup zone does just the opposite. When a computer requests the hostname of an IP address, the reverse lookup zone is queried and the result is returned. A secondary zone is a read-only copy of the zone that was copied from the master server during zone transfer. In fact, a secondary zone can only be updated through zone transfer. Reverse lookup zones have NO technical relationship to forward zones. The Reverse Lookup Zone takes IP addresses and finds domain names.

Transferring the DNS records from primary to secondary zones
Zone transfers are always initiated at the secondary server for a zone and sent to their configured master servers which act as their source for the zone. Master servers can be any other DNS server that loads the zone, such as either the primary server for the zone or another secondary server. When the master server receives the request for the zone, it can reply with either a partial or full transfer of the zone to the secondary server. By default, the DNS server will only allow a zone transfer to authoritative DNS servers listed in the name server (NS) resource records for the zone.

Verifying the DNS client configuration on Windows 7
The DNS Client service is the client component that resolves and caches Domain Name System (DNS) domain names. When the DNS Client service receives a request to resolve a DNS name that it does not contain in its cache, it queries an assigned DNS server for an IP address for the name. If the DNS Client service receives the requested address, it stores the name and address in its cache to resolve future requests without having to query the DNS server. All computers that use DNS to resolve domain names (including DNS servers and domain controllers) use the DNS Client service for this purpose.


DNS Quiz Questions.

  1. Prior to launching a new DNS server, Maria tested it in a lab and confirmed that it works. Maria verified that the server resolves resource records, such as MX, PTR, and "A," from her zone (all the records were created manually). Confirming the functionality, Maria proceeded, thinking that test records will be deleted by the scavenging process because she enabled it on the zone level right before putting the DNS server in production. After implementing the server in production, you notice that some records are redirected to the IPs that do not exist. You examine the content of the zone file and discover that Maria's test records have not been removed. How should this server have been configured to prevent this?

    For each resource record, you should have added another TIME record, which would provide timestamp information for the purposes of scavenging.
    To quickly get rid of those records, set the clock on the DNS server a month ahead and restart the DNS service.
    You should delete test records manually.
    Records, created before aging and scavenging was enabled, do not contain timestamp information and hence fall outside the scope of the scavenging process.


  2. Before installing your first domain controller in the network, you installed a DNS server and created a zone, naming it as you would name your AD domain. However, after the installation of the domain controller, you are unable to locate infrastructure SRV records anywhere in the zone. What is the most likely cause of this failure?

    A. The zone you created was not configured to allow dynamic updates.
    B. A and D
    C. NONE
    D. The local interface on the DNS server was not configured to allow dynamic updates.


  3. Which of the following conditions must be satisfied to configure dynamic DNS updates for legacy clients?

    All two
    The zone to be used for dynamic updates must be configured to allow dynamic updates.
    The DHCP server must support, and be configured to allow, dynamic updates for legacy clients.


  4. Which one of the following commands can be used to empty the DNS cache on a DNS client?

    ipconfig /emptydns
    nbtstat -RR
    ipconfig /all
    ipconfig /flushdns


  5. A DNS server was installed when there was no connectivity to the Internet, and as a result it automatically added the "." zone to its forward lookup zone lists. Your users are reporting that they are unable to resolve any Internet names. Assuming that Internet connectivity is now in place and is working properly, what can you do to resolve the issue?

  01 - Installing and setting up the first DNS server 2008 R2 - Creating forward lookup zones and zone type (standard primary) - Creating the first host (A) record for the first DNS server


  02 - Creating reverse lookup zones and zone type (standard primary) - Creating the first pointer (PTR) record for the first DNS server - Testing the first DNS server by running a (simple query)


  03 - Installing and setting up the second DNS server 2008 R2 - Connecting to the primary DNS from the DNS manager - Creating forward lookup zones and zone type (standard secondary)


  04 - Creating reverse lookup zones and zone type (standard secondary) - Transferring the DNS records from primary to secondary zones - Verifying the DNS client configuration on Windows 7

04 - DNS Diagram Tutorial


  05 - Promoting the secondary DNS to primary DNS server - Changing zone types from (secondary) to (primary) - Promoting the primary DNS to secondary DNS server - Changing zone types from (primary) to (secondary)







Next >