news://msnews.microsoft.com/#
[email protected]
Look man...It's so effing simple. Register the domain host
dns1.yourdomain.com at 203.145.145.145 with your registrar. Change the
primary DNS server for your domain to dns1.yourdomain.com with your
registrar. Make sure that port 53-UDP is forwarded through any firewalls and
the DNS server is listening on 203.145.145.145. That's friggin' it. You're
done.
Your registrar is required to do two things:
1. Register domain hosts for your domain. This is how you create DNS servers
for your domain. You tell your registrar that you would like to register the
domain host dns1.yourdomain.com at 203.145.145.145. This is how a root
server learns the name and IP address of a DNS server for your domain. It
could take a couple of days for a root server to register a new domain host.
2. Associate your domain name with the DNS servers for your domain name.
(i.e. - When someone queries a root server for the IP address for
yourdomain.com, the root server answers with the DNS server names for
yourdomain.com. If I queried a root server for the IP address for
yourdomain.com, it would answer with the DNS server names for
yourdomain.com, either dns1.yourdomain.com or dns1.yourhostingprovider.com.
These are the primary and secondary DNS servers which you configure with
your registrar for your domain name.)
Anything more that your registrar provides is icing on the cake.
If you would tell me who your registrar is, I'll get you links from their
help files on how to do this.
As far as resource records go, you'd want to start off with a couple of
basic ones (I'm assuming that 203.145.145.145 is the only globally-unique IP
address that you have.):
name type value
yourdomain.com a 203.145.145.145
www cname yourdomain.com
mail mx0 yourdomain.com
Keep in mind that these resource records would be maintained in the forward
lookup zone of the primary DNS server for your domain, maybe
dns1.yourdomain.com listening on 203.145.145.145 (your personal DNS server).