Skip to content
English
Sign in
  • There are no suggestions because the search field is empty.

DNS (Domain Name System)

Understanding DNS (Domain Name System)

A step by step guide to understanding DNS (Domain Name System) and the process of how it, the internet, and servers work together.


1. What is DNS?

DNS (Domain Name System) is a database that matches domain names (like example.com) with the IP addresses (like 192.0.2.1) that computers use to locate each other on a network.

Without DNS, users would have to remember and type in raw IP addresses to visit websites or use online services.

2. Common Terms
  • DNS (Domain Name System): The system that translates domain names into IP addresses.
  • Nameserver: A server that directs DNS resolvers to the authoritative DNS records for a domain.
  • Domain Name: The readable address (e.g., flypaper.com) that points to a website or service.
  • IP Address: The numerical address (IPv4 or IPv6) that identifies a server.
  • TTL (Time to Live): How long a record is cached before refresh.
  • Propagation: The time it takes for DNS changes to update across the internet.
  • Cache: Temporary storage of DNS lookups kept by resolvers, OS, or browsers.
  • Registrar: The company where a domain is purchased (GoDaddy, Namecheap).
  • Forwarding / Redirection: When traffic from one domain is sent to another.
  • Subdomain: A prefix like blog.example.com or shop.example.com.
  • HTTP/HTTPS: Protocols used to transfer data. HTTPS adds SSL/TLS encryption.
  • SSL Certificate: A digital certificate enabling HTTPS.
  • WWW: A common subdomain prefix.
  • TLD (Top Level Domain): The last part of a domain (e.g., .com, .org).
3. Common DNS Records
  • A Record: Maps a domain to an IPv4 address.
  • AAAA Record: Maps a domain to an IPv6 address.
  • CNAME: Points one domain to another.
  • MX Record: Routes email to mail servers.
  • NS Record: Identifies authoritative servers.
  • TXT Record: Stores text data (SPF, DKIM, DMARC).
  • SRV Record: Defines services like SIP, Teams, etc.
4. Understanding the Internet and Servers
  • The Internet: A global network of devices with IP addresses; DNS works like a street address system.
  • Servers: Store and deliver resources like websites, apps, and data.
  • User Devices: Request info from servers; DNS ensures devices and servers can find each other.
5. How does DNS work?
  1. You type a web address into your browser.
  2. Your computer asks a DNS resolver (ISP or public like Google 8.8.8.8).
  3. If cached, it returns the IP immediately.
  4. If not, it queries authoritative servers:
    • Root servers: Tell it which TLD server to ask (.com).
    • TLD servers: Point to the authoritative server for the domain.
    • Authoritative server: Returns the actual IP address.
  5. The resolver sends the IP back to your computer.
  6. Your computer connects to the server hosting the site.
  7. The result is cached for faster lookups next time.
6. What is a Nameserver?

A nameserver is a specialized server that handles queries about where a domain's services are located. It directs DNS resolvers to the authoritative records.

Why would someone have two nameservers?

  • External (public) DNS: Published for the internet (web, email).
  • Internal DNS: Managed in private networks (company servers, intranets).
7. What is Caching?

Caching is temporary storage of DNS query results to make lookups faster.

TTL (Time to Live): Sets how long a record is cached before refresh.

8. Domains, Registrars, and Hosting
  • Domain Name: A registered name like example.com.
  • Subdomain: A prefix like shop.example.com.
  • Domain Registrar: Company where a domain is purchased (GoDaddy, Squarespace, etc.).
  • DNS Host/Provider: Service managing DNS records (registrar or Cloudflare, AWS Route 53).
  • Website Host: Server where the site lives (Flypaper, Duda, WordPress, Shopify).
9. What is SSL?

SSL (Secure Sockets Layer): Encrypts data transferred between browsers and websites.

Purpose: Protects sensitive info, builds trust, enables HTTPS, improves SEO ranking.

How We Manage It: We use Duda's built-in tool to create and manage SSL certificates, not registrars.

10. How We Use DNS at Flypaper
  • New Domains: Sometimes purchased in GoDaddy for client sites.
  • Transferred Domains: Brought under our control for easier management.
  • Duda DNS Records:
    • CNAME (www → s.multiscreensite.com, TTL 600)
    • A Record (@ → 35.172.94.1, TTL 600)
    • A Record (@ → 100.24.208.97, TTL 600)
  • Third Party Records: Sometimes added for vendors or email.
  • Email Records: Provided by third-party hosts/IT. Flypaper doesn't manage email accounts.
  • Access: We cannot share DNS logins but can transfer domains if needed.
11. Forwarding & Redirects
  • Automatically sends traffic from one domain to another.
  • Using Duda: Add alternative domains in the Site Domain section, then save and republish.
12. Important Things to Remember
  • Domain Transfers: Always capture DNS records before transfer to avoid outages.
  • TTL: Changes can take minutes to 72–78 hours. Set client expectations.
  • Why DNS Records Might Fail:
    • Cached results or local servers
    • Conflicting or duplicate entries
    • Typos or bad vendor instructions