🚀 go-pugleaf

In article <Bz8q7n.293@mudos.ann-arbor.mi.us> mju@mudos.ann-arbor.mi.us (Marc Unangst) writes:
>And from what you're saying, you don't really want to be in charge of
>your own little section of the DNS because it's too much trouble to do
>correctly.

It would be nice, but I don't need to be in charge of it. 

>So, register in the .US domain, where there are nice people at ISI to
>take care of the nitty-gritty details for you.

Why? Isn't my current MX record adequate?  I seem to recall saying that
I was aware of wildcard MX's because I already had one.

>Okay, so the root nameservers is "someone".  I still think it's a lot
>more reliable and efficient to store 32 bits of information on each of
>a dozen machines -- especially when that data changes very rarely --
>than it is to store 500 bytes or so of data on each of thousands of
>hosts.

So, don't store 500 bytes or so of data for thousands of hosts.

>Registering in the .US domain is no more difficult than
>registering in the UUCP maps, and you won't even have to find another
>machine to connect to if you're already talking to an
>Internet-connected machine who is willing to forward mail for you.  

Uhh, let's see here. If I register in the UUCP maps, I don't need to
find any other machine to talk to, whether on the Internet or not. If I
register in the .US domain, I need to be talking to an Internet
connected machine who is willing to forward mail to me. If I am not,
then I need to find one. The latter seems to be more effort than the
former.