Index: [Article Count Order] [Thread]

Date:  Fri, 13 Oct 2006 09:33:49 -0700
From:  "Bruce Timberlake" <brucetimberlake (at mark) gmail.com>
Subject:  [coba-e:07559] Re: OT: DNS Querys
To:  coba-e (at mark) bluequartz.org
Message-Id:  <f76f5d3e0610130933y5ae06628p47adc880d7895e (at mark) mail.gmail.com>
In-Reply-To:  <1486c6440610130841h1babe23bo61e5d449e7eb60e7 (at mark) mail.gmail.com>
References:  <20061013064159.M26498 (at mark) www.constantino.net>	 <003c01c6eeaf$d261f380$7725da80$ (at mark) tv>	 <1486c6440610130841h1babe23bo61e5d449e7eb60e7 (at mark) mail.gmail.com>
X-Mail-Count: 07559

If it's possible, I would recommend keeping the DNS with the registrar
or some external service, rather than providing DNS services from the
same box that the domain is hosted on.

If you keep the DNS "external" to the hosting platform, if your server
goes down or is offline for some reason, the domain will still resolve
and give a "temporarily offline" message to visitors; if your server
is also doing all the DNS, the domain won't resolve at all and will
give a "domain does not exist" error.

A subtle difference, for sure, but I always like to keep DNS someplace
that "won't" go down... most registrars have a control panel for that
sort of thing; you'll need to use it to alter the master DNS servers
anyway. At a minimum, leave your secondary service someplace external
and allow it to sync from the BQ server...