Re: [cobalt-users] Colo says need scond server

["Steven Werby" <steven-lists@xxxxxxxxxxxx>]

Frank Cubillos <cubillos@xxxxxxxxxxxxxxxxxx> wrote:
> This is incorrect isn't it?
> "Also, the cobalt server can be setup as a Name Server and we know how to do
> this.

It can be setup as a name server.  Whether this person knows how to do it or not
(it's easy) is another story.  <grin>

> However, unless you wish to get two RAQ servers and setup DNS on both
> of them, you wil still need to use our DNS server as a backup DNS server.

Not true.  Every registrar I'm aware of requires at least two name servers to be
associated with each domain name.  In reality, you can create a second name servers
on the same server as long as they're on different IPs.  It's a terrible idea though.
The reasons have been covered in-depth in the archives so I won't point them out
here.  Some non-US registrars are smart and require that the two name servers be on
separate class-C IP subnets.  Whoever wrote the statement above (I assume your colo
provider) is correct in that you should_have a real, working secondary name server,
but it doesn't have to be on a RaQ and it doesn't have to be through them.  In fact,
it's not a bad idea to have your secondary name server in a different facility than
your primary, but it's not necessary.  In any case, as long as your primary name
server is reachable, new records in your DNS should be immediately visible to most
services around the world (the exception being some programs do look at secondary DNS
instead of primary DNS).

> Which means that even though you enter the DNS into your RAQ server, it will
> need to be on ours as well to serve as a backup."

If you want them to do the DNS that's true.

> Or am I dazed and confused? I am just tired of emailing my colo with every
> domain I add so they can enter it on their DNS. Thanks in advance for any
> suggestions!

They should be able to come up with an automated solution to get your DNS into their
name server.  If they're using a RaQ2/3 they could install a cron job on your server
to email them the contents of your records file whenever the date on it changes or
grab all of your zone files.  There are more elegant solutions than this, but you
shouldn't be the one who has to suggest them or implement them.

Steven Werby {steven-lists@xxxxxxxxxxxx}