RE: [cobalt-users] dns and nameservers

["Jim Carey" <ozbcoz@xxxxxxxxxxxxxxxx>]

> As web.ozdns.net and web2.ozdns.net are exactly the same -- why not simply
> have web2.ozdns.net point to ip-address of this secondary
> nameserver you've
> found?  (this will require an ip that is not currently registred as a
> nameserver)
the problem with that is that the nameserver is currently registered so I
won't be able to point my web2.ozdns.net to it - I understand you can't have
two nameservers pointing to the same ip

> Yep, it will. But it will choose name server according to who "answers
> fastest". So chances are, that it will always chose new.nameserver.com if
> the two others are down.

that's good then


> How long time does it take for your named to restart? (i.e. how
> long are you
> "non-responsive")

only a short period - it simply executes the std cobalt update dns server
index.cgi which takes /etc/records and regens the pri and restarts named -
but does happen - worried that some ISP's, email servers may say - "ah he's
down, will now go into my retry in 4 hours routine", rather than trying the
next nameserver and hopefully by then finding us

>
> I'm have made a bind dns server that serves zones directly from a mysql
> database, so that I will not have to worry about these kind of things. It
> also makes it easier to handle management of zones and resource records.

that sounds nice - most of my dns info is in a MySQL database and then my
cron job reads that and updates /etc/records - your approach is a few steps
more advanced than mine :-)

>
> --
> Jens Kristian Søgaard, Mermaid Consulting I/S,
> jens@xxxxxxxxxxxxxxxxxxxx,
> http://www.mermaidconsulting.com/
>
>
> _______________________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> To Subscribe or Unsubscribe, please go to:
> http://list.cobalt.com/mailman/listinfo/cobalt-users