[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 10:15:30 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
> >===================================
> >Then, I only have to add two entries:
> >
> >james.com IN NS ns2.james.com
> >ns2.james.com IN A ip-address-of-myISP-dns
> >===================================
> >Is my understanding correct?
>
> Yes. Note that ns2.james.com. <-- requires a dot at the end in order to be
> "fully-qualified." The rule is simple: if the name ends in a dot, it's the
> entire name; if not, BIND adds your domain name to it. So as you wrote it
> (with no dot), it won't work since ns2.james.com.james.com. will not
exist.
Thanks, I think I am ready to try the virtual name server setup. It's going
to free me a little bit from my current ISP since I presumably can use the
same "virtual" name servers by changing the DNS entry pointing to the new IP
addresses. I think I can fly.... I think I can fly... well, we will see.
On Thu, 10 May 2001, Rodolfo J. Paiz wrote:
> You're not actually using Network Solutions, right? If so, I (personal
> opinion) suggest you run, don't walk, to another registrar.
Yes, I am. I had my share of difficulties with NSI. But I am a tad more
relaxed than most people. I am keeping my options open and might decide to
make the move. I will look into bulkregister.com and opensrs.com. Thanks
for the suggestion.
> This is going to sound odd, but I don't really understand "nameserver host
> registration with NSI" since other registers (mostly bulkregister for me)
> don't hassle me with it. But I *think* that any name-address pair you
> provide for which DNS works and which answers is OK with them. So
> registering ns2.james.com as a nameserver with your ISP's IP address
should
> work as long as they already answer for the zone. Let me know if I happen
> to be right.
Actually this is what I tried initially. I tried to register name server
with ISP's IP. NSI barked that that IP has already been registered and
cannot be used by another host. So, I used one of my own IP in registering
the name server host name.
It seems that now I can just make the ns2.james.com. IN A
ip-address-of-myISP-dns entry. Then, it should work, right?
>
> As for the unique IP thing, forget it. You can run any number of services
> on one IP; *no one* had better care what else is on it. The point of a
> nameserver host, as I understand it, is that they want to verify that the
> nameservers you list actually answer for the zone you're registering. As
> long as that basic condition is met, you can do anything else you please.
It seems I am learning more reasons to move away from NSI and its antiquated
ways of doing things.
James