What are nameservers?

Nameservers are specialized DNS servers that store and manage your domain's DNS records. When someone types your domain name into a browser, their computer queries your domain's nameservers to find the IP address of your website, mail server, and other services.

How nameservers work:

  1. You register a domain (e.g., example.co.za)
  2. You set nameservers for that domain (e.g., ns1.0724.co.za and ns2.0724.co.za)
  3. DNS records (A, MX, CNAME, etc.) are configured on those nameservers
  4. When someone visits your domain, their device queries your nameservers for DNS records
  5. The nameservers respond with the appropriate IP address or record
  6. The browser connects to that IP address to load your website

Why you need to update nameservers:

  • Pointing domain to hosting: When you purchase hosting, you update nameservers to point to your hosting provider
  • Using external DNS: To use Cloudflare, Route53, or other DNS providers
  • Migrating between hosts: Moving from one hosting provider to another
  • Centralized DNS management: Managing all your domains' DNS in one place

0724 Hosting nameservers

If you have hosting with 0724 Hosting, use these nameservers:

  • Primary nameserver: ns1.practiwebs.co.za
  • Secondary nameserver: ns2.practiwebs.co.za

These nameservers are hosted in South Africa for optimal performance for South African visitors.

How to update nameservers in the client area

Step 1: Log in to the client area

  1. Navigate to https://ca.0724.co.za
  2. Enter your email address and password
  3. Click Login

Step 2: Access your domains

  1. Click Domains in the top navigation menu
  2. Select My Domains from the dropdown
  3. You will see a list of all domains in your account

Step 3: Select the domain

  1. Find the domain you want to update
  2. Click on the domain name (or click Manage)
  3. You will be taken to the Domain Management page

Step 4: Modify nameservers

  1. Scroll to the Nameservers section
  2. You will see the current nameservers for your domain
  3. Click Change or Modify next to Nameservers

Step 5: Enter new nameservers

You will see input fields for nameservers (typically 2-4 fields):

  1. Enter ns1.practiwebs.co.za in the first nameserver field
  2. Enter ns2.practiwebs.co.za in the second nameserver field
  3. Leave additional fields blank unless using 3+ nameservers
  4. Click Change Nameservers or Save

Step 6: Confirm the update

  1. The client area will display a confirmation message
  2. The system submits the nameserver update to the domain registry
  3. You will receive an email confirmation (for some TLDs)

Using external nameservers (Cloudflare, AWS, etc.)

If you use third-party DNS services like Cloudflare, AWS Route53, Google Cloud DNS, or others, follow the same steps but enter their nameservers instead:

Cloudflare nameservers (example):

  • Nameserver 1: assigned-ns1.example.cloudflare.com
  • Nameserver 2: assigned-ns2.example.cloudflare.com

Note: Cloudflare assigns unique nameservers per domain. Use the exact nameservers shown in your Cloudflare dashboard.

AWS Route53 nameservers (example):

  • Nameserver 1: ns-123.awsdns-12.com
  • Nameserver 2: ns-456.awsdns-45.net
  • Nameserver 3: ns-789.awsdns-78.org
  • Nameserver 4: ns-012.awsdns-01.co.uk

Note: Route53 provides four nameservers per hosted zone. Use all four for redundancy.

Nameserver propagation time

After updating nameservers, changes do not take effect immediately due to DNS propagation:

What is DNS propagation?

DNS propagation is the time it takes for updated nameserver information to spread across the global DNS system. During this time:

  • Different users may see different nameservers
  • Some visitors may reach your old hosting, others your new hosting
  • Email may be delivered to old or new mail servers depending on timing

How long does propagation take?

  • Registry update: 15 minutes to 2 hours for the domain registry to process the change
  • Local propagation: 2-4 hours for South African ISPs to update their DNS caches
  • Global propagation: 24-48 hours for worldwide DNS cache updates
  • Maximum TTL: Up to 72 hours in rare cases if old nameserver TTL was very high

Checking propagation status:

Use these tools to check if nameserver changes have propagated:

  • whatsmydns.net: Check DNS propagation from multiple global locations
  • Command line (Linux/Mac): dig NS yourdomain.co.za
  • Command line (Windows): nslookup -type=NS yourdomain.co.za
  • WHOIS lookup: Check nameservers at who.is or registry.net.za (for .za domains)

Verifying nameserver update

After submitting the nameserver change, verify it was processed correctly:

Method 1: Check in the client area

  1. Return to Domains → My Domains
  2. Click your domain
  3. View the Nameservers section
  4. Confirm it shows your new nameservers

Method 2: WHOIS lookup

  1. Visit https://who.is or https://www.registry.net.za (for .za domains)
  2. Search for your domain
  3. Check the "Name Server" section in the WHOIS results
  4. Confirm the new nameservers are listed

Method 3: DNS query

Use command-line tools to query nameservers directly:

dig NS yourdomain.co.za
# or
nslookup -type=NS yourdomain.co.za

Common nameserver update issues

Error: "Domain is locked"

If you receive an error that the domain is locked:

  1. Navigate to your domain in the client area
  2. Look for Registrar Lock or Domain Lock status
  3. Click Disable Registrar Lock
  4. Wait a few minutes, then retry the nameserver update
  5. Re-enable the registrar lock after updating

Error: "Invalid nameserver format"

Nameserver errors typically occur due to formatting issues:

  • Correct format: ns1.example.com (hostname format)
  • Incorrect format: 192.168.1.1 (IP addresses not allowed)
  • Incorrect format: http://ns1.example.com (no protocol prefix)
  • Ensure nameservers are fully qualified domain names (FQDNs)
  • No trailing dots, spaces, or special characters

Nameserver not updating

If the nameserver does not change after 24 hours:

  1. Check domain status in the client area (must be "Active")
  2. Verify the domain is not expired or suspended
  3. Ensure registrar lock was disabled during update
  4. Check for pending transfers (updates blocked during transfers)
  5. Contact 0724 Hosting support if issue persists

Special considerations for .za domains

South African .co.za, .net.za, and .org.za domains have specific requirements:

ZACR nameserver requirements:

  • Minimum: 2 nameservers required
  • Maximum: 13 nameservers allowed
  • Format: Must be valid hostnames (not IP addresses)
  • Functionality: Nameservers must be operational and respond to DNS queries
  • Glue records: If using your own domain as nameserver (e.g., ns1.yourdomain.co.za), glue records must be configured at the registry

Propagation for .za domains:

  • .za domains typically propagate faster than international domains
  • Updates usually visible within 2-6 hours in South Africa
  • ZACR WHOIS updates within 15-30 minutes of registry confirmation

Best practices for nameserver management

  • Always use at least 2 nameservers: Provides redundancy in case one fails
  • Use nameservers from the same provider: Avoid mixing nameservers from different hosting companies
  • Update before migrating: If migrating hosting, set up DNS records on the new nameservers before updating
  • Lower TTL before major changes: Reduce DNS TTL values 24-48 hours before nameserver updates to speed up propagation
  • Test DNS configuration: Verify all DNS records (A, MX, CNAME) are configured on new nameservers before switching
  • Enable registrar lock after update: Lock the domain to prevent unauthorized nameserver changes
  • Monitor email delivery: Watch for email delivery issues during propagation period
  • Keep old hosting active: Maintain old hosting for 48-72 hours after nameserver change to avoid downtime

Understanding DNS records vs nameservers

Many users confuse nameservers with DNS records. Here's the difference:

Nameservers:

  • Tell the internet where your DNS records are hosted
  • Set at the domain registrar level
  • Updated infrequently (only when changing DNS providers)
  • Example: ns1.practiwebs.co.za

DNS Records:

  • Store specific routing information (website IP, mail server, etc.)
  • Managed on the nameserver itself (e.g., via DirectAdmin or DNS provider dashboard)
  • Updated frequently as needed
  • Example: A record pointing example.co.za to 192.168.1.1

Analogy: Think of nameservers as the address of a library (where to find the information), and DNS records as the books inside the library (the actual information).

What happens after changing nameservers?

After nameserver propagation completes:

  • Website: Your domain will resolve to the website on the new nameserver's A record
  • Email: Email will be delivered according to the MX records on the new nameservers
  • DNS management: All DNS changes must now be made on the new nameservers, not the old ones
  • Old DNS ignored: DNS records on the old nameservers are no longer used

Post-change checklist:

  • Verify website loads correctly from multiple locations
  • Send test emails to check mail delivery
  • Check subdomains are resolving properly
  • Test any API endpoints or services using your domain
  • Confirm SSL certificates are working (may need to be reissued)
  • Update DNS records on the new nameservers if needed

Getting help with nameserver updates

If you need assistance updating nameservers, troubleshooting propagation delays, or configuring DNS after a nameserver change, contact 0724 Hosting support. We can help with:

  • Updating nameservers if you cannot access your client area account
  • Configuring DNS records on 0724 Hosting nameservers
  • Troubleshooting nameserver update errors
  • Verifying DNS propagation status
  • Setting up custom nameservers (vanity nameservers)
  • Migrating DNS records from old to new nameservers