Why DNS exists: The problem it solves

Every device connected to the internet has an IP address - a numerical identifier like 197.221.23.45. When your browser needs to load a website, it must connect to the server's IP address.

The problem:

  • Humans are bad at remembering long numbers
  • IP addresses are hard to remember: 197.221.23.45
  • Websites sometimes move to different servers with new IP addresses
  • You would need to memorize hundreds of IP addresses for sites you visit

The solution: DNS

  • Instead of remembering 197.221.23.45, you remember 0724.co.za
  • DNS automatically translates domain names to IP addresses
  • If a website moves to a new server, you update DNS once and everyone automatically connects to the new location

Analogy: DNS is like a phonebook. Instead of memorizing everyone's phone number, you save their name in your contacts. When you want to call them, you look up their name and your phone finds their number automatically.

How DNS works: Step by step

When you type example.co.za into your browser, here is what happens:

Step 1: Your computer asks for help

  • Your device does not know the IP address for example.co.za
  • It sends a DNS query (request) to a DNS server
  • Usually your internet provider's DNS server or public DNS like Google (8.8.8.8)

Step 2: DNS server looks up the answer

  • The DNS server checks if it knows the answer (from cache or records)
  • If not, it asks other DNS servers in a hierarchy
  • Eventually it reaches the authoritative nameserver that has the answer

Step 3: DNS server returns the IP address

  • DNS server responds: example.co.za is at 197.221.23.45
  • Your computer caches (remembers) this answer temporarily

Step 4: Your browser connects to the website

  • Now your browser knows where to go: 197.221.23.45
  • It connects to that IP address and loads the website

Speed: This entire process happens in milliseconds (0.02-0.2 seconds). You never notice it.

What are nameservers?

Nameservers are specialized DNS servers that store DNS records for your domain. When someone tries to visit your website or send you email, their computer asks your nameservers for the information.

How nameservers work:

  1. You register a domain (e.g., yourcompany.co.za)
  2. You point the domain to nameservers (e.g., ns1.practiwebs.co.za)
  3. Your nameservers store DNS records (website IP, email server, etc.)
  4. When someone visits your domain, their computer asks your nameservers where to go
  5. Nameservers provide the answer (IP addresses and other information)

0724 Hosting nameservers:

When you host with 0724 Hosting, use these nameservers:

  • ns1.practiwebs.co.za
  • ns2.practiwebs.co.za

These tell the world that 0724 Hosting controls DNS records for your domain.

DNS records: What information DNS stores

DNS stores different types of records. Each record type serves a specific purpose. See our detailed guide: Common DNS Record Types.

Most common DNS records:

  • A record: Points domain to website IP address (IPv4)
  • AAAA record: Points domain to website IP address (IPv6)
  • MX record: Points domain to email server
  • CNAME record: Creates alias (subdomain pointing to another domain)
  • TXT record: Stores text information (SPF, DKIM for email security)
  • NS record: Specifies which nameservers control the domain

Example DNS setup for example.co.za:

  • A record: example.co.za → 197.221.23.45 (website)
  • A record: www.example.co.za → 197.221.23.45 (website with www)
  • MX record: example.co.za → mail.example.co.za (email server)
  • TXT record: SPF record authorising email servers

Where DNS settings are managed

Two places to update DNS:

1. At your domain registrar (where you bought the domain):

  • Set which nameservers control your domain
  • Example: Point yourcompany.co.za to ns1.practiwebs.co.za
  • Only change this when switching hosting providers or DNS management

2. At your nameserver/hosting provider (where nameservers point):

  • Manage DNS records (A, MX, CNAME, TXT, etc.)
  • Change website IP, email server, subdomains
  • For 0724 Hosting clients: Manage in DirectAdmin DNS Manager

Important distinction:

  • Nameservers (registrar): WHO controls DNS for your domain
  • DNS records (hosting/nameserver): WHERE your domain points (website IP, email server, etc.)

Common DNS use cases

Use case 1: Point domain to website

You want yourcompany.co.za to load your website.

  1. Set nameservers at registrar to ns1.practiwebs.co.za and ns2.practiwebs.co.za
  2. In DirectAdmin (or DNS manager), create A record:
  3. yourcompany.co.za → 197.221.23.45 (your server IP)
  4. Wait for DNS propagation (up to 24-48 hours)
  5. Website now accessible at yourcompany.co.za

Use case 2: Set up email for domain

You want info@yourcompany.co.za email to work.

  1. Ensure nameservers point to your hosting provider
  2. In DNS manager, create MX record:
  3. yourcompany.co.za MX priority 0 → mail.yourcompany.co.za
  4. Create A record for mail server:
  5. mail.yourcompany.co.za → 197.221.23.45
  6. Wait for DNS propagation
  7. Email now works for @yourcompany.co.za

Use case 3: Create subdomain

You want shop.yourcompany.co.za to point to online store.

  1. In DNS manager, create A record or CNAME:
  2. shop.yourcompany.co.za → 197.221.23.46 (different server)
  3. Or shop.yourcompany.co.za CNAME → shopify.example.com (third-party service)
  4. Wait for propagation
  5. Subdomain now accessible

DNS propagation: Why changes take time

What is DNS propagation?

When you update DNS records, the changes do not happen instantly worldwide. DNS propagation is the time it takes for DNS changes to spread across the internet.

Why DNS changes take time:

  • Caching: DNS servers and devices cache (remember) DNS answers temporarily
  • TTL (Time To Live): Each DNS record has a TTL value (e.g., 3600 seconds = 1 hour)
  • Global distribution: DNS servers worldwide need to update their cache
  • No central notification: DNS servers only check for updates when the old cached answer expires

Typical propagation times:

  • A/AAAA records: 30 minutes to 24 hours (typically 2-4 hours)
  • MX records (email): 1-6 hours
  • Nameserver changes: 24-48 hours (can take longer)
  • TXT records: 30 minutes to 4 hours

See our detailed guide: What is DNS Propagation and How Long Does It Take?

Check DNS propagation:

Use online tools to check if DNS changes have propagated:

  • WhatsMyDNS.net: Check DNS from multiple locations worldwide
  • DNS Checker: Verify A, MX, CNAME records globally
  • MXToolbox: Check email DNS (MX records)

DNS and email: Why email needs DNS

Email relies heavily on DNS to function. Without proper DNS configuration, email will not work.

DNS records needed for email:

  1. MX record: Tells other email servers where to deliver email for your domain
    • Example: yourcompany.co.za MX → mail.yourcompany.co.za
  2. A record: Points mail server hostname to IP address
    • Example: mail.yourcompany.co.za A → 197.221.23.45
  3. SPF record (TXT): Authorises which servers can send email for your domain
    • Example: v=spf1 mx a ~all
  4. DKIM record (TXT): Cryptographic signature proving email authenticity
  5. DMARC record (TXT): Email authentication policy

See our guide: SPF, DKIM, and DMARC Email Security.

DNS security: Why DNS can be targeted

DNS hijacking:

Attackers can change your DNS records to redirect traffic to malicious sites:

  • How it happens: Attacker gains access to your registrar or DNS manager account
  • Result: Visitors go to fake website; email is intercepted
  • Prevention: Use strong passwords, enable two-factor authentication on registrar account

DNS spoofing/cache poisoning:

Attackers insert fake DNS responses into DNS server caches:

  • How it happens: Exploits weaknesses in DNS server software
  • Result: Users receive incorrect IP addresses for legitimate domains
  • Prevention: Use DNSSEC (DNS Security Extensions), reputable DNS servers

Best practices for DNS security:

  • Enable two-factor authentication on domain registrar account
  • Use strong, unique passwords for registrar and DNS manager
  • Lock domain at registrar to prevent unauthorized transfers
  • Monitor DNS records regularly for unauthorized changes
  • Use reputable DNS providers (like 0724 Hosting)

Managing DNS with 0724 Hosting

If 0724 Hosting is your registrar:

  1. Log in to the client area at https://ca.0724.co.za
  2. Go to Domains → My Domains
  3. Click domain name
  4. Click Manage Nameservers to change nameservers
  5. Or click Manage DNS to edit DNS records

If you host with 0724 Hosting but domain is elsewhere:

  1. At your domain registrar, set nameservers to:
    • ns1.practiwebs.co.za
    • ns2.practiwebs.co.za
  2. Wait 24-48 hours for nameserver change to propagate
  3. Then manage DNS records in DirectAdmin:
    • Log in to DirectAdmin
    • Go to Account Manager → DNS Management
    • Add/edit A, MX, CNAME, TXT records

DNS management guide:

See our DirectAdmin guide: Managing DNS Records in DirectAdmin.

Public DNS servers: Alternatives to your ISP

Why use public DNS servers?

  • Speed: Faster than some ISP DNS servers
  • Reliability: Less downtime than ISP DNS
  • Privacy: Some public DNS providers do not log queries
  • Security: Block malicious sites automatically

Popular public DNS servers:

Google Public DNS:

  • Primary: 8.8.8.8
  • Secondary: 8.8.4.4

Cloudflare DNS:

  • Primary: 1.1.1.1
  • Secondary: 1.0.0.1
  • Privacy-focused, very fast

OpenDNS:

  • Primary: 208.67.222.222
  • Secondary: 208.67.220.220
  • Includes content filtering options

Change DNS servers on your computer:

Windows:

  1. Control Panel → Network and Internet → Network Connections
  2. Right-click network connection → Properties
  3. Select Internet Protocol Version 4 (TCP/IPv4) → Properties
  4. Select "Use the following DNS server addresses"
  5. Enter preferred DNS: 1.1.1.1, alternate: 8.8.8.8

macOS:

  1. System Preferences → Network
  2. Select connection → Advanced → DNS tab
  3. Click + and add 1.1.1.1 and 8.8.8.8

Linux:

  1. Edit /etc/resolv.conf or use NetworkManager
  2. Add: nameserver 1.1.1.1

Troubleshooting DNS issues

Problem: Website not loading after DNS change

Cause: DNS propagation in progress or incorrect DNS records.

Solution:

  • Wait 24-48 hours for full propagation
  • Check DNS records with WhatsMyDNS.net
  • Verify A record points to correct IP address
  • Clear browser cache and DNS cache

Problem: Email not working

Cause: Missing or incorrect MX records.

Solution:

  • Check MX records with MXToolbox.com
  • Verify MX record points to correct mail server
  • Ensure A record exists for mail server hostname
  • Wait for DNS propagation (up to 6 hours for MX changes)

Problem: DNS not resolving at all

Cause: Nameserver issue or DNS server problem.

Solution:

  • Verify nameservers are set correctly at registrar
  • Check if nameservers are responding (use DNS checker tools)
  • Try changing your computer's DNS servers to Google (8.8.8.8) or Cloudflare (1.1.1.1)
  • Contact 0724 Hosting support if nameservers appear down

Getting help with DNS

If you need assistance with DNS configuration, troubleshooting, or understanding how DNS works for your website and email, contact 0724 Hosting support. We can help with:

  • Setting up DNS records for your domain
  • Configuring email DNS (MX, SPF, DKIM, DMARC)
  • Troubleshooting DNS propagation issues
  • Migrating DNS from another provider
  • Understanding DNS for South African domains (.co.za)
  • Advanced DNS configurations