On Fri, 30 Jul 1999 [EMAIL PROTECTED] wrote:
> 1) first dns hostname
ns1.phing.com
> 2) its ip address
Choose any one of our 4 IP addresses
> 3) secondary dns hostname
ns2.phing.com
> 4) its ip address
Choose any OTHER one of our 4 IP addresses
Some important information for making the decisions:
(1) DNS servers can become loaded if they serve many domains. If they
serve only a few domains, the load is very light.
(2) DNS servers for phing.com typically only serve names ending with
"phing.com" e.g. "web.phing.com", "mail.phing.com".
(3) If customer abc.com wants us to host their mail, they must update
THEIR nameservers so that mail for abc.com gets sent to mail.phing.com.
(4) If customer abc.com does NOT have nameserver, then whoever is serving
their domain must set their nameservers so that mail for abc.com gets sent
to mail.phing.com.
(5) If customer abc.com does NOT have nameserver, and NOBODY is serving
the domain abc.com, then somebody must register with internic.net so that
somebody's (maybe OUR) nameserver will server abc.com. THAT nameserver
must then direct mail for abc.com to mail.phing.com.
Under scenarios (1)-(4), our DNS will only serve phing.com. In scenario
(5), our DNS might have to serve more than just the phing.com domain.
OK, I think that's all the relevant info I can provide for the above
registration decisions. Jackie needs to provide information on which of
the five scenarios above he wants to serve also, then the best decision
can be made as to:
Whether our nameserver should be separated from mail and web.
However, if we recall what was mentioned on the SERVER-LINUX mailing list,
any one of our machines is more than sufficient to serve all three
functions and still not be too slow (i.e. we have kick ass servers). So
if you like, can even put mail+dns+web on one machine and have secondary
dns on a second machine in case the first dns goes down.
Rhan.
