Windows Server Interview Questions – Day 2 Part 1: DNS, DHCP & Networking

Windows Server Interview Questions – Day 2 Part 1: DNS, DHCP & Windows Networking

Contents hide

Day 2 – Part 1 of the Windows Server Interview Preparation Series

DNS, DHCP and networking are fundamental components of almost every Windows Server environment. They are also closely connected to Active Directory, authentication, application access and server communication.

For an experienced System Administrator or System Engineer, interviewers usually expect more than basic definitions. You should understand how these services are designed, configured, monitored and integrated into an enterprise environment.

This guide focuses on core concepts, administration and practical configuration knowledge. Advanced troubleshooting and production incidents are covered separately in Day 2 Part 2.


Section 1 – DNS Fundamentals

1. What is DNS?

DNS, or Domain Name System, is a distributed naming system that translates names into IP addresses and helps clients locate network services.

For example:

server01.example.com
        ↓
192.168.10.20

DNS is also used to locate services through specialized records such as SRV records.

In Windows environments, DNS is particularly important because Active Directory relies heavily on DNS for service discovery.


2. Why is DNS important in a Windows Server environment?

DNS is used for:

  • Hostname resolution
  • Service discovery
  • Application communication
  • Domain Controller discovery
  • Active Directory services
  • Email-related records
  • Internet name resolution
  • Internal application access

A DNS failure can therefore appear as an application, authentication, network or server problem.


3. What is a Fully Qualified Domain Name?

A Fully Qualified Domain Name, or FQDN, identifies a host using its complete DNS name.

Example:

server01.corp.example.com

Where:

server01       → Host name
corp           → Domain/subdomain
example.com    → DNS domain

4. What is a DNS namespace?

A DNS namespace is the hierarchical naming structure used by DNS.

For example:

com
 |
 +-- example.com
       |
       +-- corp.example.com
       |
       +-- sales.example.com

Section 2 – DNS Records

5. What is an A record?

An A record maps a hostname to an IPv4 address.

Example:

server01.example.com → 192.168.10.20

6. What is an AAAA record?

An AAAA record maps a hostname to an IPv6 address.

Example:

server01.example.com → 2001:db8::20

7. What is a CNAME record?

A CNAME record creates an alias for another DNS name.

Example:

portal.example.com
        ↓
webserver01.example.com

CNAME is useful when users need a stable logical name while the underlying host name may change.


8. What is a PTR record?

A PTR record is used for reverse DNS resolution.

It maps an IP address back to a hostname.

Example:

192.168.10.20
       ↓
server01.example.com

Reverse lookup is particularly useful for troubleshooting, logging and applications that perform reverse DNS checks.


9. What is an MX record?

An MX, or Mail Exchange, record identifies mail servers responsible for receiving email for a DNS domain.

Example:

example.com
     ↓
mail.example.com

MX records also have priorities, allowing multiple mail servers to be configured with different preference values.


10. What is an NS record?

An NS record identifies the authoritative DNS servers for a DNS zone.

It tells DNS clients which name servers are responsible for that zone.


11. What is a TXT record?

TXT records store text information associated with a DNS name.

They are commonly used for purposes such as:

  • Domain verification
  • SPF-related information
  • DKIM-related information
  • DMARC-related configuration
  • Other service verification

12. What is an SRV record?

An SRV record identifies the location of a specific service.

The record can specify:

  • Service
  • Protocol
  • Port
  • Target host

Active Directory uses SRV records to help clients locate services such as LDAP and Kerberos.

Example:

_ldap._tcp.dc._msdcs.example.com

Section 3 – DNS Zones

13. What is a DNS zone?

A DNS zone is an administrative portion of the DNS namespace hosted by a DNS server.

A zone contains resource records for the namespace it manages.

For example:

example.com

can be hosted as a DNS zone containing records such as:

server01
server02
mail
www

14. What is a Forward Lookup Zone?

A Forward Lookup Zone is used for resolving names to IP addresses.

Example:

server01.example.com
        ↓
192.168.10.20

This is the most commonly used type of DNS lookup.


15. What is a Reverse Lookup Zone?

A Reverse Lookup Zone is used to resolve IP addresses back to names.

Example:

192.168.10.20
       ↓
server01.example.com

IPv4 reverse lookup zones use the in-addr.arpa namespace.


16. What is a Primary DNS Zone?

A primary zone contains the writable copy of DNS zone data.

Depending on the DNS architecture, it can store and manage the authoritative records for that zone.


17. What is a Secondary DNS Zone?

A secondary zone contains a read-only copy of zone data obtained through zone transfer from another DNS server.

It can provide:

  • Redundancy
  • Load distribution
  • Additional authoritative DNS service

18. What is a Stub Zone?

A stub zone contains limited information about another DNS namespace, primarily information needed to identify authoritative name servers.

It can help with DNS delegation and name resolution between DNS namespaces.


Section 4 – Active Directory-Integrated DNS

19. What is an AD-integrated DNS zone?

An AD-integrated DNS zone stores DNS zone data within Active Directory rather than relying solely on traditional DNS zone files.

Advantages can include:

  • AD-based replication
  • Secure dynamic updates
  • Multi-master DNS updates
  • Integration with AD replication
  • Easier management in domain environments

20. What is secure dynamic DNS updating?

Secure dynamic updates allow authorized domain computers and services to register and update DNS records automatically.

This reduces the need to manually create records for every Windows client.


21. Why can incorrect DNS configuration cause Active Directory problems?

Active Directory depends on DNS for locating services and Domain Controllers.

Incorrect DNS can therefore affect:

  • Domain joins
  • Authentication
  • Group Policy
  • Domain Controller discovery
  • Replication
  • Application access

When troubleshooting an AD-related problem, DNS should be one of the infrastructure components considered early.


Section 5 – DNS Forwarding

22. What is DNS forwarding?

DNS forwarding allows a DNS server to forward queries it cannot resolve locally to another DNS server.

For example:

Internal DNS
     ↓
Forwarder
     ↓
External DNS
     ↓
Internet

Forwarders are commonly used for resolving external names without requiring every internal DNS server to perform recursive internet queries directly.


23. What is a Conditional Forwarder?

A conditional forwarder sends DNS queries for a particular domain to specified DNS servers.

Example:

partner.com
     ↓
Partner DNS Server

This is useful when two organizations or internal DNS namespaces need to resolve each other’s names.


24. What is DNS delegation?

DNS delegation allows responsibility for a portion of a DNS namespace to be assigned to different authoritative DNS servers.

For example:

example.com
     |
     +-- sales.example.com

The sales.example.com namespace can be delegated to different DNS servers.


Section 6 – DNS Resolution Process

25. What happens when a client tries to resolve a hostname?

A simplified process is:

Client application
       ↓
Local DNS cache
       ↓
Configured DNS server
       ↓
DNS lookup
       ↓
Authoritative/forwarding DNS server
       ↓
IP address returned
       ↓
Client connects to destination

The exact process depends on whether the requested record is already cached and how the DNS infrastructure is configured.


26. What is DNS caching?

DNS caching temporarily stores DNS responses so that repeated queries can be answered more efficiently.

Caching occurs at different levels, including:

  • Client
  • DNS server
  • Application

Caching reduces DNS traffic and improves response times, but stale cached information can sometimes contribute to resolution problems.


27. What is DNS TTL?

TTL stands for Time to Live.

It specifies how long a DNS response can normally be cached before it should be queried again.

For example:

TTL = 3600 seconds

means the record can normally be cached for one hour.


Section 7 – DNS Aging and Scavenging

28. What is DNS aging and scavenging?

DNS aging and scavenging help identify and remove stale dynamic DNS records.

This is particularly useful in environments with:

  • DHCP clients
  • Frequently changing computers
  • Large numbers of endpoints
  • Dynamic IP assignments

It should be configured carefully because incorrect scavenging settings can remove records that are still required.


Section 8 – DNSSEC

29. What is DNSSEC?

DNSSEC, or DNS Security Extensions, provides mechanisms for validating the authenticity and integrity of DNS responses.

It helps protect against certain DNS-related attacks such as forged DNS responses.

DNSSEC does not encrypt normal DNS queries.


Section 9 – DHCP Fundamentals

30. What is DHCP?

DHCP, or Dynamic Host Configuration Protocol, automatically provides network configuration to clients.

It can provide:

  • IP address
  • Subnet mask
  • Default gateway
  • DNS servers
  • DNS domain/suffix
  • Other DHCP options

31. Explain the DHCP DORA process.

DORA represents:

Discover
   ↓
Offer
   ↓
Request
   ↓
Acknowledge

Discover

The client broadcasts a DHCP discovery message.

Offer

A DHCP server offers an IP configuration.

Request

The client requests the offered configuration.

Acknowledge

The server confirms the lease.


32. What is a DHCP scope?

A DHCP scope defines the range of IP addresses that a DHCP server can lease to clients on a particular network.

Example:

Network:       192.168.10.0/24
Scope:         192.168.10.50–192.168.10.200
Gateway:       192.168.10.1
DNS:           192.168.10.10

33. What is a DHCP exclusion range?

An exclusion prevents specific addresses within the scope from being leased dynamically.

For example:

Scope:
192.168.10.10 – 192.168.10.200

Excluded:
192.168.10.10 – 192.168.10.30

Those addresses can then be reserved for statically configured infrastructure devices.


34. What is a DHCP reservation?

A DHCP reservation associates a specific IP address with a client’s MAC address.

Example:

MAC Address
      ↓
192.168.10.50

This allows the device to use DHCP while consistently receiving the same address.

Reservations are commonly used for:

  • Printers
  • Network devices
  • Servers
  • Appliances
  • Special infrastructure endpoints

35. What is a DHCP lease?

A lease defines how long a client can use an IP address assigned by DHCP.

Before the lease expires, the client normally attempts to renew it.


Section 10 – DHCP Options

36. What is DHCP Option 003?

Option 003 normally specifies the default gateway supplied to clients.


37. What is DHCP Option 006?

Option 006 specifies the DNS servers that clients should use.


38. What is DHCP Option 015?

Option 015 specifies the DNS domain name/domain suffix supplied to clients.


39. Why are DHCP options important in an enterprise?

DHCP options allow network configuration to be centrally distributed.

For example:

DHCP
 |
 +-- IP Address
 +-- Subnet Mask
 +-- Default Gateway
 +-- DNS Servers
 +-- DNS Domain

This reduces manual configuration and helps maintain consistency.


Section 11 – DHCP Relay

40. Why is DHCP relay required?

DHCP clients initially use broadcasts, and routers normally do not forward broadcasts between subnets.

A DHCP relay allows DHCP requests from one subnet to reach a DHCP server located on another subnet.

Example:

Client VLAN
    ↓
Router/L3 Switch
    ↓
DHCP Relay
    ↓
DHCP Server

This allows organizations to use centralized DHCP servers across multiple networks.


41. Where is DHCP relay normally configured?

DHCP relay is typically configured on a Layer 3 device such as:

  • Router
  • Layer 3 switch
  • Firewall

The exact configuration depends on the network platform.


Section 12 – DHCP Failover

42. What is DHCP failover?

DHCP failover allows two DHCP servers to share responsibility for DHCP scopes and provide redundancy.

It helps reduce the risk of DHCP becoming a single point of failure.

Common operational models include:

  • Load balancing
  • Hot standby

43. Why is DHCP high availability important?

If DHCP becomes unavailable, new or renewing clients may eventually lose network configuration.

This can affect:

  • Workstations
  • Printers
  • Phones
  • IoT devices
  • Other dynamically addressed systems

DHCP redundancy therefore becomes important in larger production environments.


Section 13 – IP Addressing

44. What is a subnet mask?

A subnet mask identifies which portion of an IPv4 address represents the network and which portion represents the host.

Example:

IP Address:  192.168.10.25
Mask:        255.255.255.0
CIDR:        /24

The /24 indicates that 24 bits represent the network portion.


45. What is CIDR?

CIDR stands for Classless Inter-Domain Routing.

CIDR represents network prefixes using notation such as:

192.168.10.0/24
192.168.10.0/25
10.10.0.0/16

CIDR allows networks to be divided more flexibly than traditional class-based addressing.


46. What is a default gateway?

The default gateway is the Layer 3 device a host uses to reach destinations outside its local subnet.

Example:

Client
192.168.10.50
       ↓
Default Gateway
192.168.10.1
       ↓
Other Network

47. What is APIPA?

APIPA stands for Automatic Private IP Addressing.

When a Windows client configured for DHCP cannot obtain an address, it may assign itself an address in the:

169.254.0.0/16

range.

An APIPA address is therefore an important troubleshooting clue when a client cannot obtain a DHCP lease.


Section 14 – Static vs Dynamic IP Addressing

48. What is the difference between static and dynamic IP addressing?

Static

The IP configuration is manually assigned.

Common for:

  • Servers
  • Network devices
  • Infrastructure services

Dynamic

The IP configuration is assigned automatically through DHCP.

Common for:

  • Workstations
  • Laptops
  • User devices

The choice depends on the system’s requirements and network design.


Section 15 – Windows Network Configuration

49. How do you view a Windows server’s network configuration?

Use:

ipconfig /all

This can show:

  • IP address
  • Subnet mask
  • Default gateway
  • DNS servers
  • DHCP status
  • MAC address
  • DNS suffix

50. How do you release and renew a DHCP address?

Use:

ipconfig /release
ipconfig /renew

This is useful when investigating DHCP-related configuration problems.


51. How do you clear the local DNS cache?

Use:

ipconfig /flushdns

This removes locally cached DNS information and forces subsequent queries to be resolved again.


Section 16 – Windows Network Troubleshooting Tools

52. What is NSLookup?

nslookup is a command-line utility used to query DNS.

Examples:

nslookup server01

Specific record type:

nslookup -type=SRV _ldap._tcp.dc._msdcs.example.com

53. What is Ping?

ping uses ICMP Echo messages to test basic IP connectivity and measure approximate round-trip time.

Example:

ping 192.168.10.1

However, a failed ping does not automatically prove that the destination is unreachable, because firewalls may block ICMP.


54. What is Tracert?

tracert helps identify the network path toward a destination.

Example:

tracert 8.8.8.8

It can help identify where traffic stops or experiences unexpected routing behavior.


55. What is PathPing?

pathping combines aspects of ping and traceroute-style analysis and can help identify packet loss along a network path.

Example:

pathping 192.168.10.20

56. What is Test-NetConnection?

PowerShell’s Test-NetConnection is useful for testing network connectivity and TCP ports.

Example:

Test-NetConnection server01 -Port 443

For RDP:

Test-NetConnection server01 -Port 3389

Section 17 – TCP/IP and Ports

57. Why should a System Administrator understand TCP and UDP?

Many infrastructure services depend on specific protocols and ports.

When troubleshooting connectivity, you need to determine whether:

  • DNS is reachable
  • SMB is reachable
  • RDP is reachable
  • LDAP is reachable
  • HTTPS is reachable
  • A firewall is blocking the service

Understanding TCP/UDP therefore helps distinguish application, firewall and network problems.


58. What is the difference between TCP and UDP?

TCP

TCP is connection-oriented and provides mechanisms for reliable delivery, sequencing and retransmission.

Common examples:

  • HTTPS
  • SMB
  • LDAP
  • RDP

UDP

UDP is connectionless and has lower protocol overhead.

Common examples include:

  • DNS queries
  • DHCP
  • Some streaming and real-time applications

The actual transport used depends on the application and protocol.


59. Which ports should a Windows Administrator know?

Some important examples include:

ServicePortProtocol
DNS53TCP/UDP
DHCP Server67UDP
DHCP Client68UDP
Kerberos88TCP/UDP
LDAP389TCP/UDP
LDAPS636TCP
SMB445TCP
RDP3389TCP/UDP
HTTP80TCP
HTTPS443TCP
Global Catalog3268TCP
Global Catalog over SSL3269TCP

In an actual production environment, the required ports depend on the service and configuration.


Section 18 – Windows Firewall

60. What is Windows Defender Firewall?

Windows Defender Firewall is the host-based firewall included with Windows.

It can control network traffic based on factors such as:

  • Inbound/outbound direction
  • Protocol
  • Port
  • Program
  • Network profile
  • IP address

61. What are the Windows network profiles?

Windows commonly uses:

  • Domain
  • Private
  • Public

Different firewall rules can apply depending on the active network profile.


62. Why can a service work locally but fail remotely?

A service can be running correctly while remote connections are blocked.

Possible causes include:

  • Windows Firewall
  • Network firewall
  • Incorrect listening port
  • Service binding
  • Routing
  • Network ACL
  • Security policy

This is why checking only whether the service is running is insufficient.


Section 19 – Network Adapter Troubleshooting

63. What would you check if a Windows server suddenly loses network connectivity?

I would check:

  1. Network adapter status
  2. IP configuration
  3. Default gateway
  4. DNS
  5. Physical/virtual connectivity
  6. VLAN
  7. Switch port
  8. Firewall
  9. Routing
  10. Recent configuration changes

Useful commands:

ipconfig /all
ping <gateway>
nslookup

and:

Get-NetAdapter
Get-NetIPConfiguration
Test-NetConnection

64. How do you view network adapters using PowerShell?

Use:

Get-NetAdapter

For IP configuration:

Get-NetIPConfiguration

For IP addresses:

Get-NetIPAddress

Section 20 – Network Name Resolution

65. What is the difference between hostname resolution and network connectivity?

These are separate troubleshooting layers.

For example:

server01
   ↓
DNS resolution
   ↓
192.168.10.20
   ↓
Network connectivity
   ↓
TCP port
   ↓
Application/service

A server can be reachable by IP while its hostname fails to resolve.

Conversely, a hostname can resolve correctly while the required service port is blocked.


66. Why should you test a specific TCP port instead of relying only on ping?

Ping tests ICMP connectivity.

It does not prove that the required application service is accessible.

For example:

Test-NetConnection server01 -Port 443

tests TCP connectivity to HTTPS.

This is more useful when investigating an application-specific connectivity problem.


Section 21 – DNS and DHCP Integration

67. How do DHCP and DNS work together?

In a dynamic Windows environment:

Client
  ↓
DHCP
  ↓
IP configuration
  ↓
DNS registration
  ↓
Hostname resolution

DHCP can provide the DNS server and domain information to clients, while dynamic DNS can allow clients to register their hostnames.

The exact registration behavior depends on the Windows and DHCP/DNS configuration.


68. What is DHCP DNS registration?

Windows clients can dynamically register their DNS records.

In managed environments, DHCP servers can also be configured to perform DNS updates on behalf of clients.

This can help maintain accurate DNS records for dynamically addressed devices.


Section 22 – DNS Administration Tools

69. Which Windows tools can be used to administer DNS?

Common tools include:

  • DNS Manager
  • PowerShell DNS cmdlets
  • nslookup
  • Event Viewer
  • Server Manager

PowerShell can be useful for automation and bulk administration.


70. Which PowerShell commands are useful for DNS administration?

Examples include:

Get-DnsServerZone
Get-DnsServerResourceRecord
Add-DnsServerResourceRecordA
Remove-DnsServerResourceRecord

Use destructive commands carefully and verify the target zone/record before making changes.


Section 23 – DHCP Administration Tools

71. Which tools can be used to administer Windows DHCP?

Common tools include:

  • DHCP Management Console
  • PowerShell
  • Server Manager
  • Event Viewer

Useful PowerShell examples include:

Get-DhcpServerv4Scope
Get-DhcpServerv4Lease
Get-DhcpServerv4Reservation

Section 24 – DNS and DHCP High Availability

72. How can DNS be made highly available?

Options include:

  • Multiple DNS servers
  • AD-integrated DNS
  • Multiple Domain Controllers
  • Secondary DNS servers
  • Appropriate network redundancy

The design depends on the organization’s requirements.


73. How can DHCP be made highly available?

Windows DHCP supports failover configurations between DHCP servers.

Other network architectures may also use redundant DHCP services.

The important principle is to avoid making DHCP a single point of failure where business requirements demand redundancy.


Section 25 – Enterprise Network Design Concepts

74. Why should servers and clients be placed in different subnets or VLANs?

Network segmentation can improve:

  • Security
  • Traffic management
  • Broadcast control
  • Troubleshooting
  • Access control
  • Network organization

A typical enterprise might separate:

Users
Servers
Management
Voice
Guest
IoT

into different network segments.


75. What is a VLAN?

A VLAN is a logical Layer 2 network segment.

It allows devices connected to the same physical switching infrastructure to be separated into different logical broadcast domains.

Example:

VLAN 10 → Users
VLAN 20 → Servers
VLAN 30 → Voice
VLAN 40 → Guest

Communication between different VLANs requires Layer 3 routing.


76. What is inter-VLAN routing?

Inter-VLAN routing allows devices in different VLANs/subnets to communicate through a Layer 3 device.

Example:

VLAN 10
   ↓
Layer 3 Switch/Router
   ↓
VLAN 20

Access between the networks can then be controlled using routing and firewall policies.


77. What is a default route?

A default route is used when a more specific route to a destination does not exist.

It is commonly represented as:

0.0.0.0/0

For an end-user device, the default gateway normally provides the path toward other networks.


Section 26 – Windows Network Configuration Best Practices

78. What are some networking best practices for Windows Servers?

Important practices include:

  • Use appropriate static addressing where required.
  • Configure correct DNS servers.
  • Avoid using public DNS directly on domain members where internal DNS is required.
  • Document IP addresses.
  • Use meaningful hostnames.
  • Maintain accurate DNS records.
  • Avoid unnecessary firewall rule exposure.
  • Segment networks appropriately.
  • Monitor network utilization.
  • Keep network drivers and firmware maintained.
  • Document dependencies and ports.

Section 27 – Quick Command Reference

Network configuration

ipconfig /all
ipconfig /release
ipconfig /renew
ipconfig /flushdns

DNS

nslookup
nslookup server01
nslookup -type=SRV _ldap._tcp.dc._msdcs.example.com

Connectivity

ping
tracert
pathping

PowerShell networking

Get-NetAdapter
Get-NetIPConfiguration
Get-NetIPAddress
Test-NetConnection

DNS PowerShell

Get-DnsServerZone
Get-DnsServerResourceRecord

DHCP PowerShell

Get-DhcpServerv4Scope
Get-DhcpServerv4Lease
Get-DhcpServerv4Reservation

Rapid Revision

Before moving to Day 2 Part 2, make sure you understand:

  • DNS
  • FQDN
  • DNS namespace
  • A records
  • AAAA records
  • CNAME records
  • PTR records
  • MX records
  • NS records
  • TXT records
  • SRV records
  • Forward lookup zones
  • Reverse lookup zones
  • Primary zones
  • Secondary zones
  • Stub zones
  • AD-integrated DNS
  • Dynamic DNS
  • DNS forwarding
  • Conditional forwarding
  • DNS delegation
  • DNS caching
  • TTL
  • DNS aging/scavenging
  • DNSSEC
  • DHCP
  • DORA
  • DHCP scopes
  • Reservations
  • Exclusions
  • Leases
  • DHCP options
  • DHCP relay
  • DHCP failover
  • IP addressing
  • CIDR
  • Default gateway
  • APIPA
  • TCP vs UDP
  • Common infrastructure ports
  • Windows Firewall
  • Network profiles
  • VLANs
  • Inter-VLAN routing
  • DNS/DHCP integration
  • Windows networking PowerShell
  • DNS/DHCP administration tools

Final Interview Tip

When answering networking questions, avoid jumping immediately to a solution.

Use a layered troubleshooting approach:

Physical / Virtual Connectivity
          ↓
IP Configuration
          ↓
Routing
          ↓
DNS
          ↓
Firewall / Port
          ↓
Service
          ↓
Application

For example, if a user says:

“I cannot access the application server.”

Don’t immediately say:

“I’ll check DNS.”

Instead, establish:

  1. Does the client have a valid IP?
  2. Can it reach its gateway?
  3. Can it reach the destination network?
  4. Does the hostname resolve?
  5. Is the required port reachable?
  6. Is the service listening?
  7. Is a firewall blocking the connection?
  8. Is the application itself healthy?

That structured approach is what separates memorized interview answers from practical infrastructure troubleshooting.

Continue to Day 2 Part 2

Understanding DNS, DHCP, IP addressing, and Windows networking concepts is only the first step. In real-world System Administrator interviews, you will also be asked how you would diagnose and resolve network problems in a production environment.

Continue with Day 2 Part 2: Advanced DNS, DHCP & Windows Networking Troubleshooting Scenarios, where we cover practical interview scenarios involving DNS failures, DHCP issues, IP conflicts, connectivity problems, firewall and port troubleshooting, routing issues, and real-world Windows networking incidents.

Leave a Comment