DNS over DSL

[Kevin Darcy]

Despite the fact that NSI's forms only appear to allow one "primary" and one "secondary" nameserver, you
can actually have 3 or more nameservers in your delegations (see, e.g., daimlerchrysler.com). So I'd just
add smtp.kensingtonlabs.com to your delegations and to your NS records (just specify multiple
"secondary" nameservers). Then you can juggle around master and slaves all you want.

NOTE: your zone's NS records don't match its delegations (hostpro.net versus netlimited.net). Naugthy,
naughty. While you're changing your delegations anyway, you should take the time to fix that.


- Kevin
Kenneth Porter wrote:

> I'd like to bring control of my DNS in-house. Currently it's hosted by
> netlimited.net and my office gateway, on a 416 kbps SDSL line, is an
> unadvertised slave allowed to transfer. I'm thinking of reversing the
> relationship and having my gateway become the master. Since the gateway
> is a member of the domain, what needs to happen? I'm figuring that a NS
> and A (glue) record must be added both to the domain's zone file and
> the NSI's record in the root server. Is that correct?
>
> For reference, the domain is kensingtonlabs.com, and the gateway is
> smtp.kensingtonlabs.com.
>
> Ken
> mailto:shiva at well.com
> http://www.sewingwitch.com/ken/
> [If answering a mailing list posting, please don't cc me your reply. I'll take my answer on the list.]