Which route should I take?

Nameservers, unless you have email on the domain that you do not want to move. Nameservers are stable; the IPs are not.

I have email on this domain. Will nameservers break it?

It will, unless you recreate your MX records at WordPress.com after the change. If that sounds like more than you want to do, use the A-record route instead — it leaves your mail alone.

Does this work for self-hosted WordPress?

No. Self-hosted WordPress lives on your own server, so you point an A record at that server’s IP address, which your host gives you.

Connect a .ng domain to WordPress.com

WordPress.com prefers nameservers. Records work too, with one caveat worth knowing.

This page is about WordPress.com, the hosted service. Self-hosted WordPress on your own server is a different thing: there you point an A record at your server’s IP address, and your host tells you what it is.

WordPress.com recommends changing nameservers rather than using A records, and gives a reason worth repeating: its IP addresses change from time to time, and when they do, a site connected by A record stops working until you update it. If you have no mail on the domain, take the nameserver route.

The records

Type	Name / Host	Value
NS	@	ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.comThe recommended route. Set these as the domain’s nameservers in the panel — the registry accepts between two and five.
A	@	192.0.78.24The alternative route: two A records on the root, this one and the next.
A	@	192.0.78.25

Read from WordPress.com's own documentation on 9 September 2026 — the source is linked at the foot of this page. If your dashboard shows something different from what is here, your dashboard is right: use it.

Step by step

1In WordPress.com, go to Upgrades → Domains → Add a domain → Use a domain I own, and enter your domain.
2Choose which route you want: nameservers, or A records.
3For nameservers: in the OneBit panel, open the domain, go to nameservers, and set the three WordPress.com ones. Note that this moves ALL your DNS, so recreate any MX records at WordPress.com.
4For A records: in the panel, go to DNS and add both A records on the root, removing any existing root A record first.
5Back in the domain, open DNS check and confirm the resolvers agree with what you just set. That is the difference between "I saved the record" and "the internet can see it".

Worth knowing before you start

WordPress.com states its IP addresses can change over time and that a domain connected by A record will stop working if they do. If you use the A-record route, treat those numbers as something to re-check rather than set and forget.

Then check it worked

Saving a record and the internet seeing a record are two different events. Open the domain in the panel and run the DNS check: it asks twenty public resolvers directly, including ipNX in Nigeria, and shows you which already have the new answer. More on what the check covers.

Questions

Which route should I take?: Nameservers, unless you have email on the domain that you do not want to move. Nameservers are stable; the IPs are not.
I have email on this domain. Will nameservers break it?: It will, unless you recreate your MX records at WordPress.com after the change. If that sounds like more than you want to do, use the A-record route instead — it leaves your mail alone.
Does this work for self-hosted WordPress?: No. Self-hosted WordPress lives on your own server, so you point an A record at that server’s IP address, which your host gives you.

Sources

Need the domain first?

Check whether the name you want is free across .ng, .com.ng, .org.ng, .net.ng and .i.ng.

Check a domain