🚀 go-pugleaf

In <Bz7p3C.Iry@cs.psu.edu> fenner@snobol.cs.psu.edu (Bill Fenner) writes:
>In article <N-9KrAEPBh107h@boombox.apana.org.au> djk@boombox.apana.org.au writes:
>|In <Byw7M3.IxJ@cs.psu.edu> fenner@postscript.cs.psu.edu (Bill Fenner) writes:
>|>There is no way to register yourself as an Internet->UUCP gateway
>|
>|Wouldn't:
>|	*.UUCP.  IN MX 500 my.host.domain.
>|in the DNS do this?

>No; you shouldn't put top-level records in your own name server.

I never said you'd put it in your nameserver, you get it put into the
DNS (officially).  Ie: that line would just appear as is (subsitute
my.host.domain for whatever deluded host thinks it wants to be an
InterNet->.UUCP gateway) in the root zone file at nic.ddn.mil.

Of course, if there is more than one deluded site which thinks it
wants to be advertised as Internet->.UUCP gateway, just add a few more
lines, as long as they all agree on the pref so that MX-based mailers
will share the load between them.

>if they did get picked up by the root name servers, do you really want *every*
>piece of mail from the Internet to the .UUCP pseudo-domain going through your
>machine?

Hey, I never said you'd want to -- the question was, "can you do it?"

If we assume that there are n (0<n<10) sites that are prepared to accept
all mail from Internet to .UUCP which is not otherwise handled (a BIG
assumption, I know) this could, technically, be done.  Can we agree
that it is theoretically possible to advertise inet->.uucp in the DNS?

I guess a technical reason why it would be a bad idea is that there are
probably some Internet sites out there whose mailers are misconfigured
enough to check MXes before handling local uucp traffic (not that they
should be asking the DNS to resolve a *.UUCP name in the first place!).

-- 
David Keegel	Home:	<djk@boombox.apana.org.au>  Tel: +61 3 593-1460