[wplug] Registering nameservers

[Joe Topjian]

Hello,

I read a post on a forum about a week ago where someone recommended
using godaddys DNS control panel to set up all their A, MX, etc
records for their primary domain.  Then on the actual server that that
IP points to, they set up BIND and then host all their secondary and
other domains they own.

Now this didn't sit right with me for a week for two reasons:
1) Having Godaddy host the records for one domain you own while you
host the others on another server doesn't seem right
2) Having Godaddy host ANY records at all when you plan on running a
nameserver regardless on if you have other domains doesn't seem right
either

The problem is, I can't find any text to support this.

I was always taught to register your "main" or "workhorse" domain at
any registrar. They will always have an option to register a new
nameserver and to use that. For example, my main domain is
terrarum.net. When I registered it, I also registered two new
nameservers, ns1.terrarum.net and ns2.terrarum.net with the IP address
of my server (yes, thats a single address and I know it should be two
but I only have one IP). Note that this is an actual option to
"register new nameserver" not just toss an A record on their site.
Once that was done, I went back to the main details of my terrarum.net
account and told it about my two new nameservers.  Now on
ns1/2.terrarum.net I can host all the A, MX, CNAME records I want and
everything works fine. And any other domain I register, I just tell it
to use ns1.terrarum.net and ns2.terrarum.net as the DNS servers (thats
why I think of the main one as the workhorse).

Like I said, thats how I was taught. This also makes sense to me
because doing it the way the forum poster said, it seems like thats an
example of lame delegation.  I'm not sure if that's the correct term
or if it's out of context and that's what I'm trying to prove here.

Does anyone know what in the world I'm talking about or am I losing it?  :)

-Joe