How to Use Custom (Private) Nameservers as a Reseller Print

Custom (private or branded) nameservers let your customers point their domains at names like ns1.example.co.uk and ns2.example.co.uk instead of ours, so your hosting carries your own brand. They need setting up at your domain registrar and on our side, so please talk to us before you change anything.

Before you start

• You need a domain of your own to base them on, for example example.co.uk.
• Custom nameservers are optional. Our standard nameservers, which are in your hosting welcome email and in the client area, work for every account straight away.
• The nameserver settings in WHM's Basic WebHost Manager Setup are server-wide and aren't available to reseller accounts, so you can't set custom nameservers in WHM yourself.

How to set them up

1. Open a support ticket saying which domain you want to use and the nameserver names you'd like (for example ns1 and ns2). We'll give you the IP address each name must point to and set up the DNS side.
2. Register the glue records at your registrar. In your registrar's control panel, find the option usually called Child Nameservers, Register Nameservers, Host Records or Glue Records. Create each nameserver name with the IP address we gave you. If your domain is registered with us, say so in the ticket and we'll do this part for you.
3. Wait for us to confirm that the nameservers are answering correctly.
4. Try a test domain first. Change one domain's nameservers to your new ones and check it with the DNS checker. Nameserver changes can take up to 24 to 48 hours to be seen everywhere.
5. Once that works, give your customers the new nameserver names. Domains already on our standard nameservers can stay as they are or be moved over one at a time.

Troubleshooting

• The registrar won't accept the nameserver names: the glue records usually have to exist first. Register the child nameservers (step 2) before using them on any domain.
• Domains stop resolving after switching: change the domain back to our standard nameservers and open a ticket, rather than leaving a customer's site offline while you investigate.

For general steps on changing a domain's nameservers, see pointing your domain to EDZNET hosting.