Originally posted by conkermaniac
I don't understand this stuff about Name Servers still...
I'm not sure wm2k1's explanation cleared it up for you (it confuses me), but in short...
Domain name >
Nameserver (contains zone file for domain) >
Server
Your
Domain name (example: billy.com) must have
Nameservers (example ns1.host.com, ns2.host.com), which will have your domain's zone file. The zone file basically (short explantion), tells where everything goes, what server the domain is on, where to deliver mail (what server), where subdomains should go, etc.
Now that you've got things pointing to the right place, next step is to set the
Domain name on the
Server (you can't just point domains at servers and hope that they will resolve, they won't).
On the
Server, everything must be set up so that when the call comes (so to speak), the server is ready. Similar to your home computer, when a request for the domain comes, you have have to set it so that it knows where the files for the
Domain are in order to return the proper file.
Somewhat simplistic explanation, but...
Sample zone file:
Code:
DNS records
name class type data time to live
eebu.com IN NS ns1.webwurkx.com 86400s (1d)
eebu.com IN NS ns2.webwurkx.com 86400s (1d)
eebu.com IN A 64.247.6.153 3600s (1h)
[url]www.eebu.com[/url] IN A 64.247.6.153 3600s (1h)
eebu.com IN MX preference: 10
exchange: mail.eebu.com
3600s (1h)
eebu.com IN SOA server: ns1.tera-byte.com
email: [email]hostmaster@tera-byte.com[/email]
serial: 2001122300
refresh: 3600
retry: 900
expire: 3600000
minimum ttl: 3600
3600s (1h)
6.247.64.in-addr.arpa IN SOA server: ns1.nac.net
email: [email]dnsadmin@nac.net[/email]
serial: 1004682031
refresh: 10800
retry: 900
expire: 604800
minimum ttl: 86400
86400s (1d)