Private Namesever setup. Need some help.

[ctomer]

I'm trying to setup private nameservers on 2 domains (stomer.net and stomer.eu) and I'm struggling. I'd be grateful if someone with a bit more knowledge could point out where I'm going wrong.

Both domains were bought at Namecheap.com.

1. Setup up private nameservers in namecheap.com.

ns1.stomer.net -> 69.73.131.161
ns2.stomer.net -> 69.73.131.160

.eu servers require a different format apparently (as per namecheap's instructions):

ns1.stomer.eu -> 69.73.131.161--ns1.stomer.eu
ns2.stomer.eu -> 69.73.131.160--ns2.stomer.eu

Here's a screenshots of my namecheap setup for stomer.net:



2. Setup appropriate dns records on my vps.

So on my stomer.net domain I have the following dns records:

But if I run

dig stomer.net any

I get:

;; AUTHORITY SECTION:
stomer.net.		1397	IN	NS	dns1.name-services.com.
stomer.net.		1397	IN	NS	dns2.name-services.com.
stomer.net.		1397	IN	NS	dns3.name-services.com.
stomer.net.		1397	IN	NS	dns4.name-services.com.
stomer.net.		1397	IN	NS	dns5.name-services.com.

Shouldn't I be seeing something like

;; AUTHORITY SECTION:
stomer.net.		1397	IN	NS	ns1.stomer.net.
stomer.net.		1397	IN	NS	ns2.stomer.net.

I have stomer.eu setup in a similar fashion on my vps. Where am I going wrong? How can I see if my changes on namecheap have been effected? Or do I have to wait for my changes to propagate? Isn't it possible to see my change before propagation is effected?

[EuroNut]

It looks like you've missed one stage, Whilst you've created the name-server records at the registrar, you haven't told the domain to use them.

stomer.net is still using dns1 to dns5.name-services.com. You need to change that at the registrar.

[ctomer]

It looks like you've missed one stage, Whilst you've created the name-server records at the registrar, you haven't told the domain to use them.

stomer.net is still using dns1 to dns5.name-services.com. You need to change that at the registrar.

My understanding was that the stage that you describe was the stage described in this tutorial: http://www.jaguarpc.com/support/tuto..._namecheap.htm

I didn't think there wasn't anything else to do, apart from setup things up at my end, which I've already done.

[EuroNut]

That illustrates how to create your nameservers. The last screen says something like "Done, now you can point your domains at your new nameservers", and that's the part you haven't done yet at namecheap.

It looks like their menu item "Modify DNS" might be where you need to go and look.

Look for a section that lists the current name-servers for your domain as dns1 to dns5 nameservices.com and change that to your 2 name servers.

[ctomer]

That illustrates how to create your nameservers. The last screen says something like "Done, now you can point your domains at your new nameservers", and that's the part you haven't done yet at namecheap.

It looks like their menu item "Modify DNS" might be where you need to go and look.

Look for a section that lists the current name-servers for your domain as dns1 to dns5 nameservices.com and change that to your 2 name servers.

Thank you. I think I've got it.

I mistakenly thought that 'Nameserver Registration' and 'Transfering DNS to Webhost' were 2 separate processes. When it seems you have to first, register your nameservers and then do the 'transfer'

Now, if you I

dig stomer.eu @p.nic.eu any

I get:

;; QUESTION SECTION:
;stomer.eu.			IN	A

;; AUTHORITY SECTION:
stomer.eu.		86400	IN	NS	ns2.stomer.eu.
stomer.eu.		86400	IN	NS	ns1.stomer.eu.

;; ADDITIONAL SECTION:
ns1.stomer.eu.		86400	IN	A	69.73.131.161
ns2.stomer.eu.		86400	IN	A	69.73.131.160

I think this is correct. Thanks for your help.

[EuroNut]

Yeah, it looks like you've found the missing step

By the way, you don't need to register individual nameservers for each domain or TLD. You could just as easily have told stomer.eu to use ns1 and ns2 stomer.com.

[ctomer]

Yeah, it looks like you've found the missing step

By the way, you don't need to register individual nameservers for each domain or TLD. You could just as easily have told stomer.eu to use ns1 and ns2 stomer.com.

Or tell stomer.net to use ns1 and ns2 stomer.eu?

One last thing for my edification, what was the point in registering the nameservers? What does that actually do?

[Pawel Kowalski]

Or tell stomer.net to use ns1 and ns2 stomer.eu?

One last thing for my edification, what was the point in registering the nameservers? What does that actually do?

The nameserver stores all the host records for your server. So as long as your server has a primary and a secondary name server there is no point in setting up additional name servers for each domain, just point your domains to the existing name servers. The only reason you would want sites on your server to host their own name servers is if you are setting up that site as a reseller. At least that's what I know about it, hopefully I'm not wrong.

[EuroNut]

Or tell stomer.net to use ns1 and ns2 stomer.eu?

Yes you could do that, and it would be fine if you're only planning to host 2 or 3 domains under that EU name-server. However, if you're planning on adding more and more domains I would seriously think about having a .COM or a .NET domain as the main name-server work horse. The reason is simply that you're VPS is in the USA, most of your sites' visitors are possibly in the USA, and the main zone-file servers are in the USA. IF you use a European based name-server you're likely to be building in small delays to the look-up of your sites for first-time visitors. Also if you use a .EU name-server to handle, for example, .COM domains, you'll encounter "no glue" issues (go do a Google for that LOL).

One last thing for my edification, what was the point in registering the nameservers? What does that actually do?

Your site can be reached either by typing into your browser http://www.yoursite.com or http://69.73.131.160 (IF it's on a dedicated IP)

Which is easier for you to remember?

Name-servers translate the numbers (IP addresses) that computers love into the easier to remember words that human brains can handle more easily. Basically, the DNS system is the biggest directory and database on the planet, with zillions of searches and changes happening every day.

So, in very simple terms, when someone types (for the very first time) http://www.yourdomain.com into their browser, your browser asks your PC to ask your ISP what the hostname www.yourdomain.com means in terms of an IP address. Your ISP's cache of such details doesn't know, so it asks up the line until it gets to the top level zone servers that simply reply "If you want to find www.yourdomain.com you need to ask ns1 or ns2.yourdomain.com, whose IP addresses are xx.xxx.xxx.xx and xx.xxx.xxx.xx". Then your name-server(s) gets asked, they reply, and the answer shoots back into your own PC's little DNS cache (in case you want to go to that site again in a little while).

The whole question and answer routine takes (usually) less than a part of a second although, sometimes, if you watch the status bar at the bottom of your browser as you type in a web address and hit enter you'll see "Looking up domain.com" there for a second or so. That's what DNS and name-servers are doing for you. Otherwise, every time you wanted to do a Google Search, you'd have to remember one of Google's servers' IP addresses to type into your browser.

DNS is one of the least talked about, and most used, elements of the Net. It doesn't take long to get a handle on it and, once you do, you'll realise just how super-efficient a system it is.

[EuroNut]

The nameserver stores all the host records for your server.

That's a VERY simplified answer. Actually, a name server can store the DNS records for thousands of domains, hosted on servers spread all around the world. Ideally your name servers should be on separate servers in separate locations.

The only reason you would want sites on your server to host their own name servers is if you are setting up that site as a reseller. At least that's what I know about it, hopefully I'm not wrong.

No, there are other reasons - The top level zone servers only provide glue for top level domains, so using a .COM name-server to handle a .CO.UK domain will work, but it takes very slightly longer to get an answer because another step is added into the search. Take a look at http://www.dailychanges.com/ (give it a few seconds to load) and you'll see just how many domains the top level servers are handling (And Daily Changes doesn't report the zillions of look-ups being performed, but just gives you a picture of the number of domains that are being registered, moved around, expired etc).

So giving a .EU or .CO.UK (or other non-top-level domain names) their own name-servers can speed up lookups fractionally.