Free guides, interview Q&As, and job responsibility breakdowns — curated by industry veterans to help you crack MNC interviews
Figure 1: How a DNS query travels from browser to answer
Figure 2: DNS Hierarchy — Root, TLD, Second-Level Domain, and Subdomain
DNS (Domain Name System)
Definition: A network service that translates human-readable domain names into machine-readable IP addresses.
Day-to-Day Example: Like a contacts app on your phone — you tap a friend's name instead of dialing their full phone number from memory.
Name Resolution
Definition: The overall process of converting a domain name into its corresponding IP address so a connection can be made.
Day-to-Day Example: Like asking a receptionist for someone's desk number when you only know their name — the receptionist translates the name into a location.
DNS Resolution Process
Definition: The step-by-step sequence — cache check, DNS server query, record lookup, and IP return — followed whenever a domain name is accessed.
Day-to-Day Example: Like the steps of ordering food through a delivery app: check past orders, search for the restaurant, confirm the address, and get it delivered.
Recursive Query
Definition: A DNS query where the contacted DNS server takes full responsibility for finding the final IP address, querying other servers as needed.
Day-to-Day Example: Like asking a travel agent to book your entire trip — they handle every step until you get the final ticket, instead of you contacting each airline yourself.
Iterative Query
Definition: A DNS query where the server returns the best answer it has or refers the client to another DNS server to continue the search.
Day-to-Day Example: Like asking a stranger for directions and being told, "I don't know, but try asking at the next corner"—you keep moving forward yourself, step by step.
DNS Caching
Definition: Temporary local storage of previously resolved DNS records to speed up repeat lookups and reduce DNS server load.
Day-to-Day Example: Like remembering a friend's address after visiting once, so you don't need to ask for directions again the next time you visit.
Root Level (.)
Definition: The topmost level of the DNS hierarchy, which directs queries toward the correct top-level domain.
Day-to-Day Example: Like the main lobby directory of a large office building that points you to the right floor before you even reach a specific department.
Top-Level Domain (TLD)
Definition: The domain category directly below root, such as generic TLDs (.com and .org) or country-code TLDs (.in and .uk).
Day-to-Day Example: Like the country or category section of a shopping mall directory, .com is like the "general stores" wing, and .in is like the "local" wing.
Second-Level Domain
Definition: The organization or brand name registered directly under a TLD, such as “Google” in google.com.
Day-to-Day Example: Like a specific shop's name within a mall wing — it's the identifiable business, not just the category it belongs to.
Subdomain
Definition: A name created under a main domain to represent a specific service or department, such as mail.company.com.
Day-to-Day Example: Like different departments within the same shop — the shop is the domain, and each department (billing, support) is a subdomain of it.
DNS Zone
Definition: A database section on a DNS server that stores records — host, mail, alias, reverse, and service records — for part of the DNS namespace.
Day-to-Day Example: Like a specific filing cabinet drawer in an office that holds all the records for one department, rather than the entire company.
Forward Lookup Zone
Definition: A DNS zone that resolves domain names into IP addresses, most commonly using A or AAAA records.
Day-to-Day Example: Like looking up a person's home address when you only know their name — you go from name to location.
Reverse Lookup Zone
Definition: A DNS zone that resolves IP addresses back into domain names, typically using PTR records.
Day-to-Day Example: Like looking up whose address it is when you only have the street number — you go from location back to name.
A Record
Definition: A DNS record that maps a domain name to an IPv4 address.
Day-to-Day Example: Like a nameplate on an office door — it tells you exactly which physical office (IPv4 address) belongs to the name on the door.
AAAA Record
Definition: A DNS record that maps a domain name to an IPv6 address, functioning like an A record for the newer IP format.
Day-to-Day Example: Like upgrading that nameplate system to a longer, modernized numbering format used in a newly expanded office building.
CNAME Record
Definition: A DNS record that creates an alias, pointing one domain name to another domain name rather than directly to an IP.
Day-to-Day Example: Like a nickname that gets forwarded to your official name in a company directory — people can search either name and reach the same person.
MX Record
Definition: A DNS record that specifies which mail server is responsible for receiving email for a domain.
Day-to-Day Example: Like the mailroom address printed on an envelope — it tells the postal service exactly which building's mailroom should receive it.
NS Record
Definition: A DNS record that identifies the authoritative DNS server responsible for managing a domain or zone.
Day-to-Day Example: Like the official notice board that tells visitors which department office holds the master records for the building.
PTR Record
Definition: A DNS record used in reverse lookup zones to map an IP address back to a domain name.
Day-to-Day Example: Like a caller-ID system that tells you whose number just called you, based only on the number itself.
SRV Record
Definition: A DNS record that identifies servers providing a specific network service, such as Active Directory domain controllers.
Day-to-Day Example: Like a directory sign in a hospital that tells you exactly which department (service) is on which floor, so you don't wander randomly.
1. Domain Name vs. IP Address
Aspect Domain Name IP Address Format Human-readable text Numeric address Example google.com 142.250.x.x Preferred by Humans Computers Role of DNS Translates this Into this
2. Recursive Query vs. Iterative Query
Feature Recursive Query Iterative Query Who finds the final answer? The DNS server itself The client, with server's hints Server workload Higher Lower Server response Final IP address Best available answer or referral Typical use Client to local resolver Resolver to other DNS servers
3. Forward Lookup Zone vs. Reverse Lookup Zone
Feature Forward Lookup Zone Reverse Lookup Zone Direction Domain Name -> IP Address IP Address -> Domain Name Record used A / AAAA Record PTR Record Usage frequency Most commonly used Used mainly for verification Example google.com -> IP IP -> google.com
4. A Record vs. AAAA Record
Feature A Record AAAA Record Maps domain to IPv4 address IPv6 address Address example 192.168.1.10 2001:db8::10 Common today? Very common Growing with IPv6 adoption Best for Legacy/general networks Modern, large-scale infrastructure
5. CNAME Record vs. A Record
Feature CNAME Record A Record Points to Another domain name (alias) An IPv4 address directly Purpose Simplifies management, redirection Direct name-to-IP mapping Example www.company.local -> server1.company.local server1.company.local -> 192.168.1.10
6. MX Record vs. NS Record
Feature MX Record NS Record Purpose Defines the mail server for a domain Defines the authoritative DNS server for a domain Used by Email systems DNS resolvers/other DNS servers Example company.com -> mail.company.com company.com -> ns1.company.com
7. PTR Record vs. A Record
Feature PTR Record A Record Direction IP -> Domain Name Domain Name -> IP Zone used in Reverse Lookup Zone Forward Lookup Zone Common use Troubleshooting, spam/email verification Website hosting, server access
8. Comparison of All DNS Records
Record Type Purpose Example A Record Domain -> IPv4 Address server1 -> 192.168.1.10 AAAA Record Domain -> IPv6 Address server1 -> 2001:db8::10 CNAME Record Alias -> Original Domain www -> server1 MX Record Defines Mail Server company.com -> mail.company.com NS Record Defines DNS Server company.com -> ns1.company.com PTR Record IP -> Domain Name 192.168.1.10 -> server1 SRV Record Locates Network Services Domain Controller location
9. DNS Hierarchy Levels Compared
Aspect Root TLD Second-Level Subdomain Position Topmost Below root Below TLD Below Second-Level Example . .com google.com www.google.com Represents Global entry point Category/country Organization Service/department
10. DNS Zone vs. DNS Namespace
Feature DNS Zone DNS Namespace Scope A portion of the namespace The complete domain structure Managed by A specific DNS server Distributed across many servers/zones Example company. local zone Entire company. local naming structure
Q1. What is DNS, and why is it important?
Answer: DNS (Domain Name System) converts domain names into IP addresses. It's important because humans remember names like google.com far more easily than numeric IP addresses like 142.250.x.x.
Q2. Explain the DNS name resolution process.
Answer: A domain name is entered, the local cache is checked first, and if not found, the request goes to a DNS server that finds the matching IP address and returns it so the client can connect to the destination.
Q3. What is the difference between a recursive query and an iterative query?
Answer: In a recursive query, the DNS server takes full responsibility for finding the final answer, querying other servers if needed. In an iterative query, the server gives the best answer it has or refers the client elsewhere, reducing its own workload.
Q4. What is DNS hierarchy, and what are its levels?
Answer: DNS hierarchy is the structured organization of domain names, consisting of the root level, top-level domain (TLD), second-level domain, and subdomain, which together allow scalable global name resolution.
Q5. Why is DNS important in Active Directory environments?
Answer: Active Directory depends on DNS to locate Domain Controllers, support user authentication, and enable service location through SRV records; if DNS fails, AD services may stop functioning properly.
Q6. What is DNS Caching, and what benefits does it provide?
Answer: DNS Caching temporarily stores previously resolved records, which speeds up name resolution, reduces network traffic, lowers DNS server workload, and improves the overall user experience.
Q7. What is a DNS Zone, and why is it used?
Answer: A DNS Zone is a database section of a DNS server that stores records for part of the domain namespace, allowing administrators to organize and manage name resolution for their internal servers and services.
Q8. What is the difference between a Forward Lookup Zone and a Reverse Lookup Zone?
Answer: A Forward Lookup Zone resolves domain names into IP addresses using A/AAAA records, while a Reverse Lookup Zone resolves IP addresses back into domain names using PTR records.
Q9. What is the purpose of an NS Record?
Answer: An NS Record identifies the authoritative DNS server responsible for a domain or zone, guiding other DNS servers toward the correct source of information during resolution.
Q10. What is the purpose of an SRV Record, and where is it critical?
Answer: An SRV Record locates servers providing a specific network service. It's critical in Active Directory, where clients use SRV records to locate Domain Controllers and support Kerberos authentication.
Q11. Why are AAAA records becoming more important?
Answer: As networks increasingly adopt IPv6 for scalability and future compatibility, AAAA records — which map domain names to IPv6 addresses — are becoming more widely used alongside traditional A records.
Q12. What role does an MX Record play in email communication?
Answer: An MX Record specifies which mail server is responsible for receiving email for a domain, so a sender's mail server knows exactly where to deliver a message.
Q13. What is the relationship between a CNAME Record and an A Record?
Answer: A CNAME Record points one domain name to another domain name (an alias), while the target domain name ultimately resolves to an IP address through its own A record.
Q14. Why do mail servers check PTR records before accepting email?
Answer: Mail servers use PTR records to verify that an incoming email's source IP address matches a legitimate, resolvable domain name, which helps filter out spam and spoofed messages.
Q15. What happens to network communication if DNS is unavailable?
Answer: Without DNS, devices would need manual IP configuration for every connection; websites, servers, email, and Active Directory services would become difficult or impossible to reach by name.
Q1. A user can access a server using its IP address but not its domain name. What is the likely cause?
Answer: This points to a missing or incorrect A Record, a Forward Lookup Zone issue, or the DNS server not responding — the domain-to-IP mapping isn't resolving correctly.
Q2. Reverse DNS lookup is failing for a server. What DNS record and zone should be checked?
Answer: Check the PTR Record inside the Reverse Lookup Zone — it may be missing, misconfigured, or the Reverse Lookup Zone itself may not have been created.
Q3. Emails from the company domain are being rejected by external mail servers. What should be investigated?
Answer: Check for a missing or incorrect PTR Record, since many mail servers verify PTR records before accepting mail to reduce spam and spoofing; also verify the MX Record configuration.
Q4. Emails are not being delivered to the company domain at all. Which record needs verification?
Answer: Verify the MX Record — it may be missing, point to the wrong mail server name, or have incorrect priority configuration, all of which would prevent proper mail delivery.
Q5. Users can reach a server by its original hostname but not by its alias name. What should be checked?
Answer: Check the CNAME Record — it may be missing, point to the wrong target hostname, or be affected by DNS replication delay.
Q6. Active Directory clients are unable to locate any Domain Controllers. What is the most likely DNS issue?
Answer: This points to missing or misconfigured SRV Records, which AD clients rely on to locate Domain Controllers and perform Kerberos authentication — check AD-related DNS configuration.
Q7. A newly created DNS record isn't resolving yet on client machines. What could explain this?
Answer: The client may still be using a cached DNS entry, there may be a replication delay between DNS servers, or the client could be pointed at the wrong DNS server.
Q8. Users at one branch office can resolve domain names, but users at another branch cannot. How would you troubleshoot this?
Answer: Check DNS server connectivity and IP settings at the affected branch, verify Forward Lookup Zone replication between DNS servers, check firewall rules, and test resolution directly using nslookup.
