Most extensions follow one rule: between 2 and 13 nameservers. A few registries are stricter.
| Extension | Rule |
|---|---|
| Most (.com, .net, .org, …) | 2 to 13 nameservers |
| .CN | Up to 6 nameservers |
| .ES | 2 to 7 nameservers |
| .EU | Up to 9, and child nameservers you create count toward that limit |
| .SX | 2 to 10, and child nameservers you create count toward that limit |
| .NZ | Nameservers and child nameservers together cannot exceed 10 |
| .DE | 2 to 13, each with its own IPv4 address, and the new nameservers must already serve the zone |
| .US | Every nameserver must use an IP address issued in the United States |
| .TEL | Nameservers are assigned by the registry and cannot be changed |
.DE: set up the zone first
The .DE registry checks the new nameservers before it accepts them. They must already answer for your domain, with the same records you use today. If they do not, the change is refused. Create the zone at your new host first, then change the nameservers.
Don't make two domains depend on each other
A .COM and a .NET domain cannot use each other's nameservers for resolution — the lookup has nowhere to start.
- ✗
example.comonns1.example.net, whileexample.netis onns1.example.com - ✓ Two .COM domains using each other's nameservers work, because they are under the same registry.
Note
Nameservers under some third-level extensions (such as .IN.NET or .BR.COM) cannot be used by a .COM or .NET domain. The .COM and .NET registry refuses them.