Link to home
Create AccountLog in
Avatar of Theo
Theo

asked on

Explanation of domain transfer

I am setting up a VirtualServer for my domains and am now in the process of getting my domain name to resolve to the new server.
According to DirectAdmin I have two nameservers on my VPS: ns1.klimatosoof.nl and ns2.klimatosoof.nl . At the site of my registrar I have set these nameservers to my domain name 'olivijn.org'. I have NOT changed the dns details here.

On my VPS I have connected this domain name to a DirectAdmin-reseller/user. Ólivijn.org'now shows up in Admin level-DNS Administration and its records mentions the same nameservers as above.

What I find somewhat strange though is that when I use NSLookup for olivijn.org I get a ''servefail' message. It may be that I just have to wait till the propagation is effective, but I may have done something wrong as well.  Some clarification would be welcome.
Avatar of kloux
kloux
Flag of United States of America image

You have your domain registered through a domain resgistrar.  From here you can see where the name servers point.  At the location of the name servers you should be able to add DNS records here.  

I looked up the domain and the name servers are as you stated above, ns1.klimatosoof.nl and ns2.klimatosoof.nl.  Where are these name servers?  They wouldn't be on your VPS but may be located or controlled where you are hosting your VPS?  You should be able to make an A record and point it to the IP of your VPS.
Avatar of Theo
Theo

ASKER

Thank you. The nameservers were there from the start. If I create new users, these nameservers already exist. So I do not know whether they are on my vps or elsewhere. I am offered however the option to create my own nameservers, but I do not know why I should do that.

I am hosted at olm.net

I have sofar never had an explanation for the following: at my registrars site I cab BOTH change the nameservers and the ipnrs for a given domain name. I always understood that changing the nameserver was enough and that thereafter all one had to do was to make sure that the hosting server picks up that domain name.

The hosting company shouln't need any name server information.  The purpose of the box is to get the public to your box correct?  You're going to host something on this server.  

All you need pointing to the public address of your VPS are DNS records.

Where your name servers are you should be able to create records.  A records, MX records for example.  Let's say this is going to host a web site.  I would create an A record for WWW and @ pointing towards your public address of your VPS.   Once this is done we should be able to run some NSLOOKUP queries to verify.

Hope this helps.  Let me know how you're making out with it.
Avatar of Theo

ASKER

I think I am very slowly beginning to understand the workings of this. At my registrar I can set both the name servers and the dns. I do not think that there actually is a nameserver on my VPS and I am trying now whether the standard name server of my hosting company (ns1/2.olm.net) can be used for the same purpose. If that works all I have to do ids set the dns at my registrar to the correct IP.
This way the fact that I have only one IP on my VPS presents no problems anymore.

Is this a correct interpretation?
ASKER CERTIFIED SOLUTION
Avatar of kloux
kloux
Flag of United States of America image

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer