Quote:
Originally Posted by Rubber Duck
That is not what I am talking about. I am talking about what happens at Name Resolution. When the query is sent to the registry, as I understood it, a unique IP address is returned. It must be, otherwise, how the hell can you resolve a name? The Nameservers at Verisign cannot just say it is in that heap over there.
|
Go back and read through my DNS for Domainers article again. It explains this in detail.
The registries do not hold IP addresses for domains. They hold IP addresses of a domain's nameservers - the nameservers that you set for a domain through your registrar control panel. You simply tell the registry that you want the nameservers for fiddle.com to be ns1.fastpark.net and ns2.fastpark.net, or ns1.netauth.com and ns3.netauth.com.
Domains are not allocated an IP address by the registry. Domains are allocated IP addresses by the person who is managing the DNS servers which you entered above. There is no built-in and inseparable IP address belong to a domain. A domain is nothing more than a name with it's list of nameservers entered into the registry.
In fact most people who manage DNS services can't even be arsed to enter an IP record for anything other than the www.
Example:
Code:
www.domain.com -> 1.2.3.4
domain.com -> no ip
I hate it when people do this, because I don't really like to type the "www" part just to go to a website. The "www" hostname is nothing more than a relic of familiarity and isn't necessary at all.
I see it's time for DNS for Domainers Part 2. It will come out after about 1 week from now as I am pretty busy.
.