Nameserver1 nameserver2

Dear Friends

I setup at home an internet server with windows 2003, everything is working fine, I have static IP address which all my domains r forwerded to, my question is' I sow in other internet servers they have NS1 & NS2 which they give thier clients to update their domains to the right server, who is or what is creating those NS1 & NS2' is Windows 2003 server doing it or ISP??

Thank's

 

Hello, from interpretation of your question I would say that the WAN DNS servers that host your C-NAME and MX records point to your Windows Server at your static IP address; ergo www.123.com translates to 82.100.200.201 and vice-versa, the latter IP address representing your static IP address at home, so when anyone types your web address in their browser the DNS servers do a forward lookup on their database and point you to the correct server at you home address.

Hope this has helped answer your question.

 

Thank's PROLIANT for your replay, now the situation is I have for example a domain name, I would like to direct it to my sever, since I don't have yer nameserver(s) becase I don't know how to create them so' in the domain name record I m using the NS1 & NS2 of the domain sellers company & in the zone domain record I put in my static IP address, I would like to have/create my own NS1 NS2 (nameserver(s)) but I don't know where/how to create them' maybe I can get some advice.

Thank's

 

It is possible to host and manage your own internet DNS domain name space, but there are a couple of important considerations.

First, your DNS system needs to be accessible all the time: 24x7 with an absolute minimum of downtime. This is important as when your DNS is down ALL your internet resources effectively become unavailable to other people. A home xDSL will struggle to provide that. You need a solid internet connection with a reasonable guarantee (SLA) of uptime. That often means something like a leased line.

Second, any mistake in your DNS set up will result in loss of access to some of your resources, so you need to be happy with being able to correctly set up DNS.

ISPs have both constant access to the internet and DNS expertise. Therefore, for most home and SME users, letting your ISP manage your internet home space is the best solution.

However, that does not prevent you managing a local DNS server for your own internal network or personal use.

So, the next question is what are you trying to achieve by hosting your own DNS name space? You may well be able to achieve what you want without taking over your whole name space.

 

thank's ReggieB, my main question was how to achive nameservers like NS1 & NS2, in this moment I have ket's say 20 domains which I manage their web sites, all those web sites r on my server (at home) instead of using NS1 & NS2 to direct the domain name to the right server I m useing an static IP address, I understand well your answer about DNS server but still I would like to understand how is being created the NS1 & NS2 on the internet, let's say I manage my own DNS server, who will update the whole internet network that for example www.mydomain.com is directed to NS1.mydomain.com etc'

Thank's

 

DNS works in a hierarchical fashion, with a relatively small number of top level entities and a very large number of lower level entities. Its a pyramid type arrangement.

The easiest way to describe how it works and answer your question is to describe how DNS resolves a name. Lets start with a variant of your example: 'NS1.mydomain.co.uk'. Say you type that into your browser, what happens next.

1. Your computer looks up its TCP/IP settings for the address of its local DNS server and sends a request to that DNS server saying "give me the IP address that matches the address 'NS1.mydomain.co.uk'.
2. Your DNS server (either running on a local server or hosted by your ISP) looks at the address and first sees if it is an address it hosts. It will often then look in its cache to see if its resolved that name recently and already has a mapping. If neither of the above, the server now has to resolve the address and it does this from right most element - this is the highest level domain. In this case the highest level element is 'uk'. There are only a limited number of top level domains (called root domains) and therefore there only has to be a small number of servers (root servers) that hold information about which DNS servers act as the authority for each top level domain. So your DNS server sends a request to a root server asking "which server is the authority for the domain 'uk'.
3. We now work down through the hierarchy. Your DNS server sends a request to the 'uk' server asking "which server is the authority for 'co.uk'. As this DNS server only has to hold information about the name space immediately below 'uk', the amount of information it holds is large but not excessively so. It can quickly find the authority for 'co' in the 'uk' address space.
4. The next request is sent to the 'co.uk' authoritative server, requesting the server that is authority for 'mydomain' within the '.co.uk' name space. That server returns the address of the domain server managing the 'mydomain.co.uk' name space.
5. The last request then asks the 'mydomain.co.uk' server for the IP address for the host 'NS1' and we have the IP address.
6. The IP address is returned to the original system, that passes it to the browser. The browser then sends an HTTP request to the IP address that the DNS system resolved for it.

As the system is hierarchical, all the DNS server managing the 'mydomain.co.uk' name space has to do is be registered with the server next up in the hierarchy (the 'co.uk' server), and manage the address mappings for the daughter nodes and hosts below it.

All this sounds like a lot of backwards and forward, but is in fact small packets of information moving very fast. Also there is caching going on that means some steps can be left out (for example, I think the same servers will manage both 'uk' and 'co.uk'). So the result is fairly quick. However, if you monitor your web browsing traffic, you'll see that the DNS name resolution takes up a significant (if not most of the) time it takes to get a web page.

So in summary. You or your ISP set up a DNS server to host the 'mydomain.com' name space. You or your ISP register this with the authority managing the '.com' server which now knows to send requests for addresses within this domain to your server. And then you manage the mappings of hosts within your name space. So all you need to do is have a host mapping for "NS1" with its IP address in your DNS server, and the same for "NS2 ". Other users will find it via the 'com' server.

If NS1 and NS2 are your DNS servers, when you register the domain, you'd inform the authority that NS1.mydomain.com and NS2.mydomain.com where your DNS servers. More important than their names: you would also provide their IP addresses and in this way the authority for '.com' has the IP address of the servers holding all the name space information for your domain.