On Sun, Sep 21, 2003 at 02:50:43AM -0400, support@codefit.com wrote:
> i.e., if I have a domain name fakedomain.com and register that name as a
> name server with a registrar - ns1.fakedomain.com, ns2.fakedomain.com, can I
> also use the fakedomain.com as an actual web site, and also set up the
> register info for fakedomain.com as a domain which points to itself, i.e.
> point to ns1.fakedomain.com, ns2.fakedomain.com?
No, this is where that whole glue thing comes in.

When you set up the nameservers for the domain with your registrar,
you'll need to fill in IP addresses as well as names.  Then when the
registrar pushes out your NS information to the com/net/whatever
nameservers, they'll also put A records for those NS records out there
as well.  (The A records are the glue.)

Now, when someone queries for fakedomain.com, the com nameservers will
reply with the NS records ns[12] *and* the glue records.  This should
give the resolver just enough information to be able to contact ns[12],
where the authoritative answers are.  Note that ns[12] will also have
those A records, but ns[12] will be authoritative for them.  If you
update those A records, you'll have to manually update the glue records
via your registrar as well.

You may want to invest in a copy of "DNS & BIND" by Albitz & Liu.  They
explain all this stuff in good detail.

> Would fakedomain.com need
> to have a different IP address from the NS1 And NS2 IP’s?

They're just A records.  Point them whereever you'd like.  (The only
issue with having the same address for ns1 as ns2 is that this means you
have effectively one nameserver, which is less than ideal.)

-- 
Ed Schmollinger - schmolli@frozencrow.org

-- Attached file included as plaintext by Ecartis --

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE/bZnsuUf1YjPlx/ARApaSAJ9vmV0dZa083WmiCv14QWcRkAIQJACeLy72
Ji+L2nlXm9kFMDodFcWCDIY=
=pD88
-----END PGP SIGNATURE-----