Changing a restricted .ng domain after it is registered
On a reserved extension the registry holds a copy of what you filed, so some changes are a form and some are a letter. Which is which, why, and how to send the ones that are.
DAN updated September 22, 2026 6 min read 
Most of what people want to change on a domain is self-service, and should be. On a reserved extension some of it is not, and the split catches people out because it does not follow the usual rule that anything you can see you can edit.
The reason is worth understanding once, because it explains every case. When you registered a .gov.ng, .edu.ng or .sch.ng name you filed a document with NiRA, and that document said who you are, who to contact, and which nameservers the domain should use. The registry kept it. Anything the filed document states is the registry’s record, not ours, and our own copy is a reflection of theirs. Changing the reflection would only put the two out of step.
So the question for any change is a simple one: was it in the letter?
What you can change yourself, right now
DNS records. A, AAAA, CNAME, MX, TXT, the lot, as often as you like. The letter named your nameservers, not the records inside the zone, so nothing here touches the filed record.
What the domain is connected to. Attaching it to a service, adding a subdomain, moving a site from one service to another. All DNS underneath.
Auto-renew, and paying for the renewal.
Who on your team can see it. That is our own access control and the registry has no view of it.
What needs a new letter
Everything the filed document stated. In practice that is a short list, and nameservers are the one that comes up.
Nameservers. Moving DNS to another provider, or bringing it to us from one. The nameserver form on the domain page is closed on a reserved extension for exactly this reason.
The administrative or technical contact. The person named in the letter has left, or the role has moved to someone else. Worth doing properly rather than leaving a former colleague as the registry’s contact of record.
The registrant itself. A merger, a renaming, an institution absorbed into another. Rare, slow, and always a letter.
None of this is a permission problem on our side, and it is not us being careful with your account. We could write a new nameserver into our own database today. The registry would still be serving the old one, your domain would resolve to neither of the things you expected, and you would have a harder problem than the one you started with.
How to request a change
Through the same thread that got the domain registered. Open the domain in the dashboard and go to Requirements. That page does not disappear once the domain goes live, which is deliberate: it is the file, and this is what the file is for.
Write a fresh letter on your letterhead stating what you want changed. A sample is below.
Have it signed by someone who can sign for the institution, the same standard as the original application.
Upload it on the Requirements page and say in the thread what the change is.
We file it with the registry and apply the change once it is accepted.
You get an email when anything moves, and so do we when you write. Nobody has to sit refreshing the page.
A letter for a nameserver change
Shorter than the registration letter, because the registry already has you on file. It needs to identify the domain, state the change, and be signed by someone who can make it.
For a contact change, keep the same shape and swap the middle: name the person leaving the record, give the new name, designation, official email and phone, and confirm the rest is unchanged.
The case worth planning for
Moving DNS to us from somewhere else, on a domain whose letter named the other provider. This is the one where the order of operations matters, because doing it in the obvious order takes your site down.
The obvious order is: file the letter, nameservers move, then build the zone. In between those last two steps the domain is pointing at us and we are answering with an empty zone, which is a site that has stopped existing.
Do it the other way round:
Ask us to provision the zone first. We can do that at any time, because a zone nobody is delegated to is inert.
Copy your records across and check them against your current provider. An automatic copy finds the common ones and misses the unusual ones, and the unusual one is always the thing somebody depends on.
Then file the nameserver letter.
When the registry applies it, the zone is already right and the switch is invisible. Say in the thread that this is what you are doing and we will set the zone up before the letter goes anywhere.
How long any of this takes
The same as the original application, which is to say about a week for a complete request, and longer when something has to be asked about. Nameserver changes are usually at the quicker end because the registry is amending a record rather than deciding whether you qualify for one.
The part that runs long is almost never the registry. It is getting the letter signed, which on a .gov.ng domain can take longer than everything else put together. If you know a change is coming, start the signature before you need it.
Why it works this way
It would be easy to read all of this as a restriction we chose, and it is worth being clear that it is not. Reserved extensions exist so that a .gov.ng address can be trusted without thinking about it, and that only holds if the registry, rather than whoever happens to have the dashboard password, decides what the record says.
What we can do is make the part we own honest: tell you a form is closed instead of letting you press save on something that will not take, keep the conversation and the documents in one place you can find a year later, and not pretend a wait is ours to shorten when it is not.
The same applies to any reserved extension that comes along later. The flow on this page is not specific to the three we sell today.
The registration guides
If you have not registered the domain yet, start with the guide for your extension.
Everything else about domains, including the ones that go live the moment you pay, is on the domains product page.
Related posts
How to register a .gov.ng domain
.gov.ng is closed to everyone outside government, and the application has to be signed by an officer senior enough to bind the agency. What NiRA requires, who signs, and how the hold is cleared.
DAN 
How to register a .sch.ng domain
.sch.ng is reserved for Nigerian primary and secondary schools, and NiRA holds every new one until your registration and approval documents clear. The requirements, a sample letter, and the wait explained.
DAN 
How to register a .edu.ng domain
You can buy a .edu.ng name in minutes, but it will not resolve until NiRA has seen your accreditation documents. Here is who qualifies, what to send, a letter you can copy, and what we do with it.
DAN