Networking / Beginners

Primary and Secondary Servers

The primary DNS servers are owned and managed by specific domains. These servers provide authoritative replies for hostname resolution within the domain. For example, the domain ibm.com is managed by a set of IBM-owned name servers such as ns.watson.ibm.com and ns.austin.ibm.com. These name servers can resolve all hostnames within their domain.

Secondary name servers provide authoritative responses but may not be directly owned or managed by the domain. Secondary servers receive periodic updates from primary servers. These updates, or zone transfers, are accomplished through a TCP connection. All authoritative information from the primary is transferred to the secondary.

[Previous] [Contents] [Next]

In this tutorial:

  1. Domain Name System (DNS)
  2. DNS Common Uses
  3. Hostname-to-Address Mapping
  4. Common Lookup Tools
  5. Naming Confusion Attack Vectors
  6. Dotted Names
  7. Name Formatting
  8. Exploited Anonymity
  9. Mail Servers
  10. Sender Policy Framework Overloading
  11. Domain Keys Overloading
  12. DNS Protocol
  13. Packet Information
  14. Simple DNS Server
  15. Distributed Architecture
  16. Top Level Domain Servers
  17. Generic Top Level Domain (gTLD)
  18. Secondary Level Domain (SLD)
  19. Primary and Secondary Servers
  20. Caching Servers
  21. DNS Management
  22. DNS Direct Risks
  23. DNS Performance versus Security
  24. DNS Cache Poisoning
  25. Corrupt DNS Packets
  26. DNS Domain Hijacking
  27. DNS Server Hijacking
  28. Dynamic DNS
  29. Similar Hostnames
  30. Domain Renewals
  31. Hostnames
  32. Zone Transfers
  33. Host Listing
  34. DNS Fields
  35. Mitgation Option
  36. Technical Threat Mitigation
  37. Social Threat Mitigation
  38. Defining Trusted Replies