WordPress DNS: A Non-Profits Guide

If you manage a non-profit website on WordPress, DNS (Domain Name System) is the invisible infrastructure keeping your site reachable 24/7. Without correct DNS configuration, your carefully built WordPress site becomes inaccessible, donations stop, and your message never reaches supporters. In this guide, I'll walk you through DNS setup step-by-step, using plain language and real examples from South African non-profits we've hosted.

DNS isn't complicated once you understand what it does: it's a phonebook for the internet. When someone types your non-profit's domain name into their browser, DNS translates that human-readable name (like mynpo.org.za) into a numeric IP address (like 192.0.2.1) that servers understand. Without DNS working correctly, your WordPress site is unreachable, even if it's running perfectly on your hosting server.

What Is DNS and Why Your Non-Profit Needs It

DNS is the foundational service that makes your non-profit's WordPress website discoverable online. Without it, no one can visit your site, receive email from your domain, or trust your organization's digital presence. Think of DNS as the postal service for the internet: it routes requests to the correct destination.

For a non-profit, reliable DNS is critical. Donors expect to find you instantly. Partner organizations need to email you securely using your domain address. Search engines use DNS to verify your site's legitimacy—a misconfigured DNS can tank your search rankings. In South Africa, where many non-profits operate on tight budgets and volunteer tech teams, a DNS outage can mean lost fundraising opportunities and damaged credibility.

At HostWP, we've migrated over 500 South African non-profit websites, and one consistent pattern emerges: organizations that understand DNS early avoid 90% of common hosting issues. When a non-profit's WordPress site goes down, the root cause is usually a DNS misconfiguration, not a server problem. This is why I always prioritize DNS education for new clients.

DNS operates through a hierarchy. Your domain registrar (the company where you bought your domain—like Afrihost, Xneelo, or a global provider like GoDaddy) holds your registrant records. Your hosting provider (like HostWP) provides the actual nameservers that point to your WordPress site. These two must communicate correctly, or your site becomes unreachable.

Faiq, Technical Support Lead at HostWP: "I've found that non-profits often register domains and hosting with different providers, then don't update the nameservers. Six months later, the site vanishes when the old hosting expires. Always point your domain registrar's nameservers to your current hosting provider on day one."

Nameservers vs. DNS Records: What's the Difference?

Nameservers and DNS records are related but distinct. Nameservers are servers that hold all your domain's DNS information. DNS records are the individual instructions stored on those nameservers. Understanding this distinction prevents costly mistakes.

Nameservers are the primary DNS servers your domain registrar points to. When someone looks up your domain, their browser asks: "Who manages DNS for mynpo.org.za?" The registrar replies with nameserver addresses (e.g., ns1.hostwp.co, ns2.hostwp.co). The browser then queries those nameservers for all the domain's DNS records. In South Africa, most registrars (Xneelo, Afrihost, WebAfrica) have user-friendly interfaces for updating nameservers—it's usually a dropdown menu.

DNS records are the specific instructions stored on nameservers. The main types are:

• A Record: Points your domain to your WordPress server's IPv4 address (e.g., 197.245.100.50 on HostWP's Johannesburg infrastructure).
• AAAA Record: Points your domain to the server's IPv6 address (newer internet protocol).
• CNAME Record: Creates an alias—useful for subdomains like www.mynpo.org.za or blog.mynpo.org.za.
• MX Record: Routes email sent to your domain address to your email provider (e.g., Google Workspace, Zoho).
• TXT Record: Verifies domain ownership and enables security protocols like SPF, DKIM, and DMARC for email authentication.
• NS Record: Delegates DNS authority to specific nameservers.

For most non-profits, you'll only touch A, CNAME, MX, and TXT records. When you change hosting providers, you update the A record's IP address. If you use Google Workspace for email, you add MX records that Google provides. If you enable two-factor authentication or email signing, you add TXT records.

How to Point Your Domain to Your Hosting Provider

Pointing your domain to your hosting provider is the critical first step. This is where nameservers come in. Here's how to do it if your domain and hosting are with different companies (which is common for non-profits moving from free platforms to managed WordPress hosting).

Step 1: Get Your Hosting Provider's Nameservers

Log into your HostWP account (or your hosting provider's control panel). Look for "Nameservers" or "DNS Settings." You'll see something like:

• ns1.hostwp.co
• ns2.hostwp.co
• ns3.hostwp.co

Write these down. Different providers use different nameserver addresses, so don't guess.

Step 2: Access Your Domain Registrar

Log into the registrar where you purchased your domain (Xneelo, Afrihost, WebAfrica, etc.). Find the DNS or Nameserver settings. This is usually under "Domain Management" or "My Domains."

Step 3: Update Nameservers

Replace the current nameservers with your hosting provider's nameservers. Delete the old ones, add the new ones. This is the most critical step. Save the changes.

Step 4: Wait for Propagation

DNS propagation takes 24–48 hours (sometimes up to 72 hours). During this time, some users will reach your old site, others your new WordPress site. This is normal. Check propagation using free tools like whatsmydns.net—it shows which nameservers different parts of the internet are seeing.

Configuring Essential DNS Records for WordPress

Once your domain points to HostWP (or your hosting provider), you'll configure individual DNS records. Most hosting providers (including HostWP) provide a control panel (cPanel or similar) where you manage DNS records directly.

The A Record (Most Important)

Your A record points your domain name to your server's IP address. If your WordPress site is hosted on HostWP's Johannesburg infrastructure at IP 197.245.100.50, your A record would be:

The "@" symbol means "the root domain" (mynpo.org.za itself). TTL (Time To Live) is 3600 seconds (1 hour)—how long DNS information is cached before being re-checked.

The CNAME Record (For Subdomains)

If you want www.mynpo.org.za to work, add a CNAME record:

This tells the internet that www.mynpo.org.za is an alias for mynpo.org.za (which already points to your server via the A record).

MX Records (For Email)

If your non-profit uses Gmail or Google Workspace for email, Google provides MX records you add to your DNS. For example:

The Priority field tells email servers which to try first (lower number = higher priority). If you don't add MX records, emails sent to yourname@mynpo.org.za will bounce.

TXT Records (For Email Authentication and Domain Verification)

TXT records verify ownership and secure email. Common TXT records include:

• SPF (Sender Policy Framework): Tells email systems which servers are authorized to send email from your domain. Without SPF, emails get flagged as spam. A typical SPF record looks like: v=spf1 include:_spf.google.com ~all
• DKIM (DomainKeys Identified Mail): Cryptographically signs your emails to prevent spoofing. Your email provider (Google, Zoho) generates a DKIM record you paste into DNS.
• DMARC (Domain-based Message Authentication): Enforces email policies and reports violations: v=DMARC1; p=quarantine; rua=mailto:dmarc@mynpo.org.za

These are optional but highly recommended. They prevent malicious actors from sending phishing emails pretending to be your non-profit—critical for donor trust and POPIA compliance in South Africa.

Troubleshooting Common DNS Issues

Even with correct configuration, DNS issues happen. Here's how to diagnose and fix the most common problems.

Site Shows "Cannot Find Server" or "Server Not Responding"

This usually means DNS isn't pointing to your hosting provider. Check: (1) Have nameservers finished propagating? Use whatsmydns.net to verify. (2) Are the nameservers correct? Log into your registrar and compare them to your hosting provider's documentation. (3) Are there typos? One character wrong breaks everything. If all looks correct but the site still doesn't load, contact your hosting provider's support (HostWP's is 24/7 and SA-based).

Email Doesn't Work but Website Does

Your A record is correct (site loads), but MX records are missing or wrong. Log into your DNS control panel and add your email provider's MX records exactly as provided. Use an email test tool like mxtoolbox.com to verify MX records are set correctly.

Site Works for Some Users but Not Others (Slow Propagation)

This is normal during the 24–48 hour propagation window. Your ISP's DNS cache may hold old records. Try flushing your local DNS cache: on Windows, open Command Prompt and type ipconfig /flushdns; on Mac, open Terminal and type sudo dscacheutil -flushcache. Or simply use a different internet connection (mobile hotspot) to test.

Website Moves Offline After Renewal

Common scenario: your hosting expires, you renew it, but forget to update nameservers back from the old provider. The domain registrar still points to dead nameservers. Update nameservers to your new hosting provider immediately after renewal. At HostWP, we handle this for you during migration—you don't have to touch DNS.

SSL Certificate Shows "Not Trusted"

HostWP provides free Let's Encrypt SSL certificates, but the certificate is issued for specific domain names (e.g., mynpo.org.za, www.mynpo.org.za). If the CNAME for www doesn't exist or is wrong, browsers will show a certificate warning. Ensure both A and CNAME records match the domains your SSL is issued for.

DNS Best Practices for Non-Profit Websites

Proper DNS hygiene prevents headaches and keeps your non-profit's online presence secure and reliable.

1. Document Everything

Write down your domain registrar, hosting provider, nameservers, and DNS records. Store this in a shared document (Google Drive) accessible to board members or trusted volunteers. When the tech volunteer leaves, you'll still know how to access everything. Too many non-profits lose domain and hosting access because DNS details are only in one person's email.

2. Use Strong Registrar and Hosting Passwords

Your registrar account and hosting account control your entire web presence. If someone gains access, they can redirect your domain, steal your data, or shut down your site. Use unique, strong passwords and enable two-factor authentication if available. Xneelo, Afrihost, and HostWP all support 2FA.

3. Set Registrar Auto-Renewal

Domains expire if not renewed. A lapsed domain can be snatched by someone else. Enable auto-renewal on your registrar so you're never surprised. Mark renewal dates on your calendar as a backup.

4. Monitor Email Deliverability (SPF, DKIM, DMARC)

If your non-profit sends emails from your domain (newsletters, thank-you messages), configure SPF and DKIM records. This prevents emails from bouncing or landing in spam. Load shedding and unreliable internet in parts of South Africa mean donors may not see unsolicited emails—proper SPF/DKIM setup ensures legitimate emails get through.

5. Use a Managed WordPress Host (Like HostWP)

Managed WordPress hosting providers handle DNS setup and maintenance for you. We add DNS records, manage propagation, and troubleshoot issues. With HostWP's white-glove migration service, we migrate your non-profit's entire site and configure DNS—you don't touch a thing. This is especially valuable if your tech team is volunteer-run.

6. Backup DNS Records Regularly

Export your DNS records periodically (most control panels allow this). If your registrar's servers are compromised or your account is hacked, you'll have a backup to restore from. This is part of standard POPIA data protection practice for non-profits handling donor information.

7. Keep Nameservers in Sync Across Registrar and Host

Your registrar should point to your hosting provider's nameservers, and those nameservers should manage all your DNS records. Don't mix—for example, don't use registrar nameservers for one domain and hosting provider nameservers for another. This creates confusion during troubleshooting and can break your site during migrations.

At HostWP, our nameservers (ns1.hostwp.co, ns2.hostwp.co, ns3.hostwp.co) are reliable and monitored 24/7 from our Johannesburg data centre. We've built redundancy to prevent DNS failures, even during South Africa's load shedding periods when power is unstable.

Frequently Asked Questions

What's the difference between a domain registrar and a hosting provider?

A domain registrar (like Xneelo or Afrihost) is where you buy and renew your domain name. A hosting provider (like HostWP) is where your WordPress files and database live on a server. Both work together—the registrar holds the nameservers (which point to the host), and the host manages DNS records that tell the internet how to reach your site.

How long does DNS propagation take?

DNS propagation typically takes 24–48 hours, occasionally up to 72 hours. This is the time for DNS changes (like updating nameservers) to spread across the internet's network of DNS servers. You can't speed this up, but you can check progress using tools like whatsmydns.net. Your site will work for most users before full propagation completes.

Can I change my domain registrar without losing my website?

Yes. When you move registrars, you simply update the nameservers at your new registrar to point to your hosting provider. Your hosting doesn't change, so your website stays live. Ensure you unlock the domain at your old registrar and request an authorization code (EPP) before moving. Keep the old registrar active until propagation completes.

What happens if I let my domain expire?

Your domain becomes inactive and your website goes offline. In South Africa, there's typically a 30–60 day grace period where you can renew at a penalty fee. After that, the domain enters redemption (expensive recovery) or becomes available for anyone to register. Enable auto-renewal or set a calendar reminder at least 30 days before expiration.

Do I need to configure DNS records if my domain and hosting are with the same company?

Not usually. If you host with HostWP and buy a domain through HostWP, DNS is automatic—your domain points to your hosting with zero configuration. However, if you already own a domain elsewhere and point it to HostWP, you'll update nameservers at your registrar. Either way, HostWP's team can guide you at no extra cost.