Re: [cobalt-users] Shared IP Address: DNS / Website - Good / Bad Practice?

[flash22@xxxxxxx]

On Sat, 2 Dec 2000, Gary S. Ownsby wrote:

> We have a remotely hosted RaQ3i.
> 
> DNS is running on base IP address.
> We have also leased 16 addition IP addresses.
> We are using FrontPage 2000.
> Base IP website projected hits per year: 500,000
> 
> The company we lease the RaQ3 from said that we could run a website on the
> base IP address along with DNS service.  This would basically save using one
> of the 16 additional IPs.  To do so, we were told to name the RaQ3 host as
> "WWW".  So it appears as www.ourcompanyname.com.  We registered the DNS
> server name with Network Solutions as www.ourcompanyname.com.  Registration
> was successful.  We published a website to the base IP address.  DNS and the
> website work fine.
> 
> Ordinarily DNS servers are named something other than "WWW" like "NS1", etc.
> This would seem to preclude sharing the same IP with a website.  Is sharing
> a base IP address between a DNS and website good or bad practice??  It seems
> to work but are there potential problems that we were not made aware of?  We
> need to know before we begin a mass migration of existing websites on other
> servers to the RaQ3 which will require modifying the DNS record for each
> one.
> 

There's nothing wrong with this per se, but you didn't have to do it this
way, you can create a A record for the nameserver on the same ip address
as the one you used for 'www' and call it ns1 ...(be sure to add a NS
record for it to identify it as a nameserver so the root servers are
happy_) uncheck the reverse IP automatic creation btw, it's confused.

The drawback to using www for both the web site and the nameserver is that
you are going to have a heck of a project if you ever decide to move the
nameserver to another server, you will have to change all the domain
registration records, using a different name like 'ns1' means you woud
only have to change the ip address ns1 points to ...


g.