At 07:08 PM 2/9/00 -0500, you wrote:
Why dns1.beautytech.com and not admin.beautytech.com for your DNS?
That's the way Sage/Interliant set up mine and other RAQs.
Dan, you can call your nameserver anything you want. Most of us call them
either ns.domain.net, or ns1.domain.net, and so forth. It's just an
evolving usage; no standards involved <smile>.
For example, Jatek, where I used to be part owner, hosts it's secondaries
at <pongo.calgate.net> (which I think is a dumb idea, since
<pongo.calgate.net> points to a competitor's website <frown>).
But if you look at my whois record for <nobaloney.net>, you'll see
<ns1.ns-one.net> and <ns2.ns-one.net>. I currently also have
<ns3.ns-one.net>, but Domain Bank (who I currently use as a registry)
doesn't have a way to let me enter more than two nameservers into their
whois database or the root servers <frown>.
I bought the <ns-one.net> domain name JUST for hosting
name-services. Look at the website at <www.ns-one.net> and you'll see I
go out of the way to make sure that no-one looking at your name-servers
(should us use us <smile>) would leave you to buy hosting from me. Of
course I can also set up dns servers at your domain; I can easily host
<ns1.you.com> at our location, even on our own name-servers.
Jeff
--
Jeff Lasman <jblists@xxxxxxxxxxxxx>
_______________________________________________
cobalt-users mailing list
cobalt-users@xxxxxxxxxxxxxxx
http://list.cobalt.com/mailman/listinfo/cobalt-users