[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Virtual Name Server
- Subject: Re: [cobalt-users] Virtual Name Server
- From: "jwk at Zone Alpha" <jwk@xxxxxxxxxxxxx>
- Date: Thu May 10 11:09:39 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
----- Original Message -----
From: Rodolfo J. Paiz <rpaiz@xxxxxxxxxxxxxx>
To: <cobalt-users@xxxxxxxxxxxxxxx>
Sent: Thursday, May 10, 2001 6:37 PM
Subject: Re: [cobalt-users] Virtual Name Server
> This is why I always use the two NS records as being part of the same
zone.
> If he's joe.com, I have:
>
> joe.com. IN NS ns1.joe.com.
> joe.com. IN NS ns2.joe.com.
> ns1.joe.com. IN A 111.111.111.111
> ns2.joe.com. IN A 222.222.222.222
>
> where 111.111.111.111 and 222.222.222.222 are the nameserver addresses I
> use for *every* domain. In this case it's easy as pie to change the two IP
> addresses registered as nameservers to my machines, then just make sure I
> have A records in that zone that say this machine has that name.
>
> Make sense? Again, I can help you on how to do things right but I refuse
to
> predict how NSI will want to do them.
Rodolfo,
What you say here makes a lot of sense. Very clear logic. But this is
*not* what NSI allows. Once they have 111.111.111.111 and 222.222.222.222
in their database, they refuse to register additional name server host on
these IP addresses. I thought there must be some good reason why we cannot
have more than one name server hosts pointing at the same IP.
James