> The only real problem I have is that the DNS's idea of our domain doesn't
> correspond _exactly_ with what the local ip coordinator thinks exists. This
> is a shame, and from what I've read in UKIP, they have a similar problem.
>
This problem should be common to any amateur packet network that has
become "adult" enough for providing IP services. Well, maybe except
those regions where the "network" actually consists of "wormholes". I
brought up a discussion about building subdomains for ampr.org in the
german News network, mainly to improve SMTP mailrouting but also to ease
administration and to speed up integrating new hosts.
> Although Brian has never said that the DNS server at ucsd.edu should be counted
> as the true "source" of information, with much more widespread use of the
> Internet, it's much easier to check through Internet DNS (if available) for
> the various A or MX records.
>
IF AVAILABLE.
if (!available)
{ you have to provide something own }
else { forget the whole story }
DNS is needed for that many services! Not only SMTP mailrouting, but
also for HTTP proxies/caches and many other interesting things. Even
more: some things simply rely on having subdomained structures, not
*flat* ones.
> The uk has been permitted to have a uk.ampr.org, but I think they still have
> trouble with this working properly (I may be wrong). As far as downloading
> zone information is concerned, zoning as in uk.ampr.org is much easier, as
> you only request the relevant entries and the files are thus much smaller.
>
Hm, you say there is an internetted DNS where you can request zone maps
for uk.ampr.org? Sounds interesting, but my main interest is to set up a
net of DNS within the packet radio network that updates itself with
automatic zone-transfers. I don't see why I should need "permission" for
that?
> Here's probably not the place to discuss this (zoning of ampr.org).
>
Right. Maybe we should start a thread in digital.misc?
> If you want a copy of the perl scripts I wrote (they are not very complicated)
> let me know. I also have one which checks for differences between the
> ip coordinators view of his sub-domain, and the DNS equivalent view. This is
> useful for finding errors, and missing, or extra entries.
>
I am interested. Vice versa I could send you my awk-script. It's not
that clever, it just scans a domainfile and filters the records by
subnets and builds the zone/reverse-maps. However it does one
interesting thing: It builds a map for "ampr.org" containing CNAME
records that point to the subdomained name of the host. Thus you can ask
the DNS for both naming variants and always get an answer. This is quite
useful for mailrouting, because you actually don't need to know the
subdomained name :-)
> > Has anybody experiene with this idea, or what is the clue for better routing ?
As far as IP-Routing is concerned, DNS have nothing to do with it.
-- 73s de Matthias