Nameserver nightmare

4 posts / 0 new
Last post
#1 Tue, 06/21/2011 - 23:49
jmbolanos

Nameserver nightmare

I can see this is an issue that many people get stuck with but I can't see any posts that are like the issue I have (I've tried the solutions from many posts but go nowhere).

OK....here goes

I have a domain registered with a domain registrar www.jmb-webserver.com that points to my static IP address. The website setup on a virtualmin virtual server jmb-webserver.com works fine. In the DNS options I have the following records

ns1 A - IPv4 Address 192.168.0.2 (this is the local IP address for the webserver) ns2 A - IPv4 Address 192.168.0.2

jmb-webserver.com NS - Name Server jmb-webserver.com. (created automatically)

I have another domain called hudportal.com on another virtual server and I have set the nameservers at the domain registrar to ns1.jmb-webserver.com and ns2.jmb-webserver.com - the details for this sever are

hudportal.com NS - Name Server jmb-webserver.com.

The domain registrar reports that they cannot set the nameservers to ns1 and ns2 jmb-webserver.com for hudportal.com because they don't exist.

Please help!

Tue, 06/21/2011 - 23:59
andreychek

Howdy,

The domain registrar reports that they cannot set the nameservers to ns1 and ns2 jmb-webserver.com for hudportal.com because they don't exist.

Yup, that's correct :-)

Nameservers don't automatically exist, you have to first register a given IP as a nameserver.

There's some details on setting up nameservers here in the section "How do I setup nameservers for my server":

https://www.virtualmin.com/documentation/dns/faq

Wed, 06/22/2011 - 10:06 (Reply to #2)
Locutus

Nameservers don't automatically exist, you have to first register a given IP as a nameserver.

Just for completeness' sake: This statement is not generally true. ;) My hoster e.g. allows setting any IP address as nameserver in their NIC configuration interface. I only need to register those that I want to use as masters with their slave nameservice feature.

Though in particularly this case, your statement is of course correct. :)

Wed, 06/22/2011 - 05:55
ronald
ronald's picture

Ill add to that.

You can not have nameservers pointed to a LAN address. They are not known to the outside world.
Your static WAN address 92.xx.x.240 is the one you need to register as a nameserver at your registrar (where you bought the domain) Those are called glue records.

You will need a second IP though, I rent a cheap VPS to act as a nameserver for example.

Then those 2 WAN IP's you will add to your Virtualmin installation as the nameservers.

Or if you use your registrars nameservers, you need to change only and all A and MX records at the registrar for all domains you will host and make them point to your WAN IP 92.xx.x.240.

Topic locked