SOLVED How to set up nameservers via WHM and add to domain registrar

[Bowral]

Hi everyone,

I'm new to WHM and wanted to get some help as to how I successfully create nameservers and then add them to the domain name via the registrar. At the moment, this is what I've done:

Step 1. Via WHM

1. Set up nameservers via the 'basic webhost manager' set up in WHM
2. Created 4 name servers (e.g. ns01.domain.com.au, ns2 etc)
3. Each name server has the same IPV4 address that by default is associated with the server (e.g. 180.100.100.11)

Step 2. Via Domain name registrar (e.g Netregistry)

1. Log into Netregistry account where mywebsitedomain.com.au (for example) is held, go to domain delegation
2. Create my own glue records with the 3 name servers I created previously, including the same 180.100.100.11 IPV4 address
3. Update the name servers from ns1.netregistry.net, ns2 etc, to the ones I created

Issue:

After I've done this and I do a DNS propagation check for NS, it comes up with nothing and can't get domain name connected to server

Questions:

1. How do I get the domain name to properly connect to my server?
2. I set up a cPanel account already for (e.g.) www.mywebsitedomain.com.au and it has a dedicated IP address of (e.g) 10.0.0.22 - do I need to place that IP address anywhere?
3. What records do I need to create within the cPanel accounts zone editor?

I apologise in advance if this all sounds rather rudimentary, I am very green with this so any guidance would be much appreciated

Cheers,
Luke

 

[cPRex]

Hey there! It sounds like you're just missing one step - setting up A records in the main zone for mywebsitedomain.com.au so the nameservers resolve in DNS. Can you add those and see if that gets things working?

 

[ejsolutions]

Each name server has the same IPV4 address that by default is associated with the server (e.g. 180.100.100.11)

This is not such a good idea. At the worst, it should only be 2 nameservers, pointing to the one server. Fundamentally, this is still ill-advised though as for various reasons, the nameservers should at least be on different servers, if not at different locations. A small (cheap) VPS with about 1GB RAM/10GB storage is just big enough to use as a secondary nameserver. (I have 4 similarly specced VPS, used as NS3 through NS6.) These have WHM DNS Only installed on them.
You may be better served by using one of the many external DNS providers, some of which are free, for a limited number of domains.

Take a look at leafdns dot com and intodns dot com - they'll guide you towards a better setup, to some degree.

 

[cPRex]

While the single IP isn't ideal, a lot of users don't want the expense of geographically-diverse nameservers. If you aren't doing that, you may has well just have the minimum two on the same IP, as 4 doesn't provide any advantage.

 

[ejsolutions]

.. a lot of users don't want the expense of geographically-diverse nameservers.

Yup. I get three of mine for about $20/year, in total, which is unusual.

 

[Bowral]

Hey @cPRex and @ejsolutions, thanks to you both for your input, setting up the A records correctly worked a treat which is awesome . Great feedback as well regarding nameserver location, some definite food for thought.

Thanks again!

Luke.

 

[cPRex]

I'm glad to hear things are working well for you now!

 

[ejsolutions]

Coincidentally, today I've setup another DNS Only instance, on a $6/yr 896MB/10GB VPS (needed a small tweak to install).
There's a few good VPS providers, Down Under.
Have fun with your new setup.