Knowledge base
To use nameservers named inside your own domain, such as ns1.yourdomain.com, the registry needs their IP addresses first. Add these glue records yourself on the domain's Nameservers tab.
If you run your own DNS servers and want your domain to use nameservers named inside the domain itself (for example ns1.yourdomain.com and ns2.yourdomain.com for yourdomain.com), the registry has to know their IP addresses before the domain can use them. Those addresses are called glue records. Without them, nobody could find your nameservers, because finding them would first need the nameservers themselves.
You can add glue records yourself for any domain you registered with us.
ns1.yourdomain.com).
A new glue record usually appears at the registry within a few minutes. The card shows, for each nameserver, the addresses the registry itself publishes.
glue records here; their own domain's registry holds them.
10.x.x.x), local addresses and reserved ranges are refused, because no one on the internet could reach a nameserver there.
To change the address, save the same nameserver name again with the new address. To remove one, press Remove beside it. A glue record for a nameserver your domain still uses cannot be removed: change the domain's nameservers first, so the domain keeps working.
If you connected a domain that is registered with another company, add glue records at that company: the registry only accepts them from the domain's own registrar.
We show the reason on the card. Check the address is your nameserver's public address and try again. If it still fails, contact support with the nameserver names and addresses and we will register them for you.
What we have been writing about hosting, SEO and running sites at scale.
How hosting shapes indexing and link equity in 2026: keeping pages indexed, vetting aged domains before you build on them, link building without a footprint, and an honest line on what infrastructure can and cannot do for SEO.
Read the post →A practical checklist for fast, secure WordPress: server-level caching, a per-site object cache, the handful of plugins worth running, keeping the stack current, and the WooCommerce pages you must never cache.
Read the post →What actually separates good managed hosting from a cheap box with a control panel — migrations, backups, isolation, real caching and honest scaling — and how to judge it before you commit.
Read the post →Support is included on every plan, the desk is open 24 hours a day, and you can write to us in any of our 58 languages — we answer you in yours.
Contact support → All articles →