Our Nameserver

Short version / TL;DR

• If you bought your domain from us → use the DNS management tool in your Client Management Portal (full control).

• If you’re on Shared or Reseller hosting → manage DNS in Plesk (recommended) or keep DNS external and point your A record to the hosting IP for the location where your data is hosted (e.g. Nigeria).

• If you prefer to delegate DNS to us so we manage everything for you, change your registrar’s nameservers to our nameservers below — they are fully replicated and authoritative.

What we provide (nameservers — fully replicated)
Our DNS nameservers are fully synchronized. When you add or change records they replicate across all nameservers, so there’s no need to pick one by location. Use any or all of these when delegating DNS to us:

1) If you purchased your domain from us

• Use the Client Management Portal → Domains → DNS Management tool to add/edit any records (A, CNAME, MX, TXT, etc.).

• This is the simplest option: one place for billing, DNS and support.

Quick steps

1. Log into Client Portal.

2. Locate SiteHUB ToolBox Drop down

3. Go to DNS Manager → Add A Domain.

4. Add or edit records (save). Changes replicate to our nameservers automatically.

2) Shared & Reseller Hosting customers

Option A — Manage DNS in Plesk (recommended if your DNS should be tied to the hosting)

• Plesk has DNS zone management per domain. Edit records in Plesk → Domains → DNS Settings.

• Typical flow: create/edit A records, MX for email, TXT for SPF, etc. Saving updates the DNS served by your hosting (and — if you use our nameservers — is reflected globally).

Option B — Manage DNS externally (at your registrar or a third-party DNS provider)

• If you prefer to keep DNS outside our systems (for example, your registrar’s DNS or a third-party DNS service), do not change nameservers to ours. Instead configure records externally.

• If you prefer to manage DNS externally (e.g., at your domain registrar or a third-party DNS service), you’ll need to point your domain's A record to an IP in a location where your data is hosted (e.g. Nigeria).

Example (external DNS):

• example.com. A 167.88.51.88 ← (IP of the server hosting your site in Nigeria)

• www CNAME example.com.

3) Delegate DNS to us (so we manage everything)
If you want us to be the DNS authority (so you can edit DNS inside Plesk or the Client Portal and not at your registrar), change your domain’s nameservers at the registrar to our nameservers above. Because our nameservers are fully replicated, records you add via our portals will be served from all three.

Quick steps

1. At your registrar: find the domain → Nameservers.

2. Replace current nameservers with:
   ng1.sitehub.ng - 167.88.48.88
ng2.sitehub.ng - 51.68.32.233
ng3.sitehub.ng - 167.88.51.88

3. Save. DNS edits you make in our portal or Plesk will then be authoritative.

Common DNS records & when to use them (short)

• A — points a hostname to an IPv4 address (use this to point example.com to your hosting IP).

• AAAA — points to an IPv6 address.

• CNAME — points a hostname to another hostname (e.g., www → example.com). Don’t use CNAME on the root (@) if your registrar forbids it.

• MX — mail exchange records (point to the server that handles email).

• TXT — verification and policy records (SPF, DKIM, Google verification, etc.).

• NS — nameserver records (only change if delegating subzones).

• SRV — used by some services (VoIP, some chat/app services).

Recommended TTL

• Use 3600 (1 hour) for most records during setup/testing. Once stable, you can increase (e.g., 86400) if desired.

Example full zone (common setup)

(Replace IPs and hostnames with the ones for your account/server.)

Propagation & troubleshooting

• DNS changes can take effect anywhere from a few minutes up to ~24 hours depending on cache and TTL.

• If something doesn’t resolve: flush your local DNS cache, try dig/nslookup, or use an online DNS checker. If nameservers are set to ours but you can’t see your new records, confirm you edited DNS in the Client Portal or Plesk.