Question

What nameservers to use / how to set up multiple domains within one VPS (virtualmin)

  • Posted on December 13, 2013
  • marcelAsked by marcel

Hello,

I succesfully installed virtualmin. I have set up one domain as virtual server , this works. I see my HTML uploaded to that domain.

However, I now try to set up multiple domains in virtualmin. So I created a sub-server (thats how virtualmin calls it), being my domain. I tried to use own nameservers for this domain, which I have setup in my master domain.

But this does not work. Why does this not work, and any info/tutorials on how to set up multiple domains in virtualmin, and what NS settings to use?

To summarize my question: I have 2 domainnames registered by an external domain registar. I want both domains running on a single VPS. How can I do this?

Thanks a lot in advance! Been bugging with this the whole day.


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Thanks Pablo, you made it al much clearer now. I will definitively look for a new registar, and I agree that just using one nameserver would not be smart (yes, there is going to run production apps on the VPS…). I think, until I have more knowloedge of nameservers, I just will go with ns1, 2 and 3 of digitalocean. That seems like the most safe option right now.

<b>“I have read that, but I also read that glue records where not the same as nameservers.”</b> <br> <br>The <a href=“https://www.digitalocean.com/community/articles/how-to-create-vanity-or-branded-nameservers-with-digitalocean-cloud-servers”>article</a> does <b>not</b> suggest that Glue records <i>are</i> the same as nameservers. <br> <br><b>“Is it really advisable to use own nameservers instead of digitaloceans`?”</b> <br> <br>It is <b>not</b> advisable to use only one of your own servers as a nameserver, in lieu of the <b>3</b> nameservers that DigitalOcean allows you to use, for free. <br> <br><b>“I mean, how serious is the loss you describe.”</b> <br> <br>Is not being able to access your server a “serious” issue, for you? Just like many things in life, there are few one-size-fits-all approaches when it comes to computing. If you’re simply using this server as a sandbox in which to learn the intricacies of server management, then I would submit that it’s well worth effort to learn how to manage your own nameserver. If your droplet is a production server, you’d be nuts to only use 1 nameserver AND – even worse – host that DNS server on the same server as your site(s)/app. <br> <br>As wonderful of a service that DigitalOcean is, hardware failures; network problems; software bugs; and more, are a reality of computing-life that no one – not Google, Amazon Web Services, GoDaddy, Linode, RackSpace, etc. – are immune to. In the IT world, redundancy has <i>always</i> been a goal. It’s just that for the longest time, it was cost-prohibitive. That is (only one of the big reasons) why DigitalOcean has been so successful, so fast: Now, you can have redundancy until your little heart is content, all the while not sacrificing quality and without breaking the Piggy Bank. <br> <br><b>“Because, in case my registar does not support glue records…”</b> <br> <br>Perhaps it’s time for a new registrar.

I have read that, but I also read that glue records where not the same as nameservers. But I got now a new e-mail from my registar and they say: <br>“You can just point al your A records to the IP of the VPS, that will solve this”. But that is not in line with your comment “Glue records are not A records”, so I am a little bit confused right now. <br> <br>I will try with changing nameservers and adding the IPs of the digitaloceans nameservesr there. <br> <br>BTW, earlier you commented: "At that point, you'd lose the safety net of redundancy and gain absolutely nothing.". Is it really advisable to use own nameservers instead of digitaloceans? I mean, how serious is the loss you describe. Because, in case my registar does not support glue records, then I will have to go with digitaloceans nameservers. <br> <br>