OpenVZ Forum


Home » General » Support » Nameservers (Which IP addresses to use.)  () 1 Vote
Re: Nameservers [message #42798 is a reply to message #42797] Mon, 30 May 2011 01:57 Go to previous messageGo to previous message
Ales is currently offline  Ales
Messages: 330
Registered: May 2009
Senior Member
KitchM wrote on Sun, 29 May 2011 20:28
So, to put it another way. The containers IP address and the nameservers it is assigned are for the benefit of the container provider.

Container won't work without them.

Quote:
However, the customer who is rented the container is able to set their own IP addresse(s) and nameserver(s) as they desire for their own domain.

Yes.

Quote:
What I don't understand is how those two sets of specifications are kept separate.

You don't need a domain in order to have a container. You don't even need a domain in order to reach a container. The DNS for a domain and the DNS for a container are set in different places, they are completely different things.

Quote:
The customers nameservers can continually be overwritten by the ones used by the service provider, as I've seen it happen with resolv.conf.

The contents of the resolv.conf can change, yes. As long as the entries are valid, the change shouldn't affect the container much. If the customer happens to have a domain registered somewhere, this change won't affect the domain in any way. The equivalent of this would be changing the resolv.conf from OpenDNS public DNS to Google's public DNS. Both entries should work pretty much the same.


Try to imagine a few different scenarios:

1) try to think of a situation where a container customer owns no domains. Eliminate the existance of a domain from this scenario alltogether. Assume that the customer will only use an IP to reach his container. How should the container be set up? You'll understand faster if you start this way...

2) after the previous imaginary container is set up and after the customer has started using it, imagine that the customer suddenly remembers he has registered a domain some years ago at some third party registrar. This registrar offers the customer to use registrar's DNS for the domain. What does he need to do in order to point this domain to his existing and fully operational container? You'll see that he shouldn't need to change the resolv.conf at all.

3) then a third scenario - customer decides he wants to run his own DNS inside the container, he wants ns1.hisolddomain.com and ns2.hisolddomain.com to be used for hisolddomain.com. What does he need to do? You'll see that he still doesn't need to change the resolv.conf.

4) the last scenario - customer decides he wants to use his own DNS inside his resolv.conf within his container. What does he need to do?

Once you can imagine all four scenarios, you're pretty much set to go as far as the basic DNS is concerned. It would be best if you could try this out on some test server or a virtual machine at home...

Hope this helps.

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: enter failed: unable to exec sh: No such file or directory
Next Topic: Install on SL6/RHEL6
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sun Aug 03 06:32:49 GMT 2025

Total time taken to generate the page: 0.78145 seconds
Powered by FUDforum Powered by Virtuozzo Containers