[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-users] Re: Primary/Secondary DNS on RaQ3
- Subject: [cobalt-users] Re: Primary/Secondary DNS on RaQ3
- From: Jay Tingley <jayt@xxxxxxxxxxx>
- Date: Wed May 31 14:13:56 2000
[ Rodolfo writes... ]
> The reason that having secondary DNS on a separate server is *not* academic
> is that the outcomes of someone looking for your site differ:
> * If your server dies and you have secondary DNS on another, still-living
> box, customers who try to reach your (or your customers') sites will be told
> you are currently unreachable. You still exist, but you're down.
Rodolfo, I agree with everything you say, but insofar as the viewer
is concerned, whether or not they get a "temporary unavailable" or
"not found" error, the end result is the same: they cannot access
the website.
And with reference to email, if this is a first-time viewer, they
won't have an opportunity to obtain an email address to bounce.
> * If your server dies and is the only DNS on the planet for those sites,
> customers who try to reach your (or your customers') sites will be told that
> you do not exist. NOW you cease to exist... as your customers jump ship.
Yes, but the customer is always right - even when he's wrong. :)
To be honest, I don't think most people realize the difference. To
them, a site they can't access is simply unaccessible.
> When you're running a commercial operation with even *one* customer, this
> makes a big difference. As a matter of fact, Brent's suggestions make all
> the more sense for smaller outfits, since bigger ones can go and create all
> this infrastructure by themselves.
As a small company, it is *crucial* to retain your autonomy from
a larger hosting company. What looks more professional: running
both DNS servers, or having one run by your co-location company?
> I apply (and have recommended to some people) exactly the school of thought
> you propose. However, I do so in a home setting, where the only customer at
> risk is yourself and not a soul cares if your site is down. But in a
> business setting, the results are *very* different.
The ideal solution is to run your own primary and secondary DNS
servers on one RaQ3, then have your co-location company run a
tertiary DNS server. This way, you get the reliability you refer to
as well as the autonomy resellers and hosting companies seek (since
most WHOIS lookups only return 2 DNS servers).
Best Regards,
Jay Tingley
BlackSun | info@xxxxxxxxxxx