The Domain Name Service (DNS) protocol provides a distributed name resolution service. We need DNS because we humans have trouble remembering the numerical IP addresses of computers, so we let the computers running Domain Name Service perform the name lookup, changing a computer's name into the IP addressees computers need to communicate. Domain Name Service (DNS) is the mechanism used to translate the name of a computer into computer's IP address. DNS is provided by a special computer (a server) running DNS software such as Berkeley's Internet Name Daemon (BIND), Microsoft DNS or another DNS server application. Using DNS your web browser can translate an Internet domain name such as www.inetdaemon.com, into an IP address where the website is located. DNS servers provide this translation by performing a 'lookup'. When they lookup a name and return an address, it is referred to as forward DNS lookup. Domain Name Service can also translate IP addresses into domain names which is called reverse DNS lookup.
THE DOMAIN NAME SYSTEM
- Domains
- DNS Hierarchy
- Zones
- DNS Servers
- DNS Server Types
- Authoritative
- Non-Authoritative
- Caching / Recursive Servers
- Iterative Servers
- DNS Server Functions
- DNS Server Types
- DNS Resolution
- Delegation
- Forward
- Reverse [ in-addr.arpa ]
- Iterative
- Recursive
- Round-Robin Resolution
- Split DNS (aka Split-brain DNS)
- DNS Configuration
- DNS Registrars
- DNS Shared Registration System
- DNS Domain Registration
CONFIGURING DNS
Configuring Berkeley Internet Name Daemon (BIND 8 & 9)
- namedb (contains the following files)
- named.root
- named.conf
- named.pid
- Advanced Configurations
- Split DNS
- Hidden Master
Microsoft DNS
- DNS Administrative Control Panel
- Active Directory with Integrated DNS