smart@manta.mel.dit.csiro.au (Robert Smart) (08/24/90)
Traditionally mail software is set up to send a few specific domains like .bitnet and .uucp to clever relay hosts, and to send the rest by MX record. However the number of top level domains keeps changing and it is hard to keep track of which ones understand MX records, so I do it the other way: I send mail to well-behaved top level domains by MX and send all the rest to our local intelligent mail relay. Unfortunately our local intelligent mail relay is getting heavily overloaded. So I'd like to send as much by MX as possible. Would anybody like to give a list of well behaved top levels. At the moment I have the 3-letter ones plus au, nz, se and ac.uk. It has been put to me the fr and ch are also ok but I'm not sure. Of course I could find out which domains our relay has special (non-MX) rules for, but that keeps changing. Bob Smart <smart@mel.dit.csiro.au>
anselmo-ed@cs.yale.edu (Ed Anselmo) (08/24/90)
We just got bit by this -- a user tried to send mail to a FQDN in the
"HK" (Hong Kong) domain; we didn't have an up-to-date top-level domain
list and thought it was an unqualified name....
The latest list of top-level domains can be retreived by anonymous ftp
from nic.ddn.mil in netinfo:domains.txt. Here's the one I fetched
yesterday:
; [SRI-NIC] NETINFO:DOMAINS.TXT 19-Aug-90
;
; Only top-level domains are listed. Information about subdomains
; should be acquired by asking the top-level domain servers.
;
; Format of entries conforms to that of NETINFO:HOSTS.TXT (RFC952).
; !!NOTE!! this is not the same as the original format!!
;
; DOMAIN: <addresses> : <name> : [possible extra fields]
;
; The addresses given are those of Internet hosts which provide
; a Domain Name Server for that domain.
DOMAIN: 128.6.4.7, 128.6.21.9, 192.5.25.82, 128.103.1.1 : AR :
DOMAIN: 192.67.67.53, 26.3.0.103, 128.9.0.107, 192.33.4.12, 128.8.10.90, 26.1.0.13, 128.102.16.10, 192.52.195.10, 192.5.25.82 : ARPA :
DOMAIN: 192.48.96.2, 192.5.25.82 : AT :
DOMAIN: 128.250.1.21, 128.250.1.26, 130.56.4.16, 128.32.133.1, 192.48.96.3, 192.16.202.1 : AU :
DOMAIN: 192.48.96.2, 192.5.25.82 : BE :
DOMAIN: 128.103.1.1, 128.32.136.12, 31.4.0.10 : BR :
DOMAIN: 128.189.97.41, 192.31.103.6, 128.89.1.178, 192.26.210.1, 128.100.102.3 : CA :
DOMAIN: 130.59.1.30, 128.141.1.113, 192.16.202.1, 192.48.96.2, 128.112.128.1 : CH :
DOMAIN: 192.48.96.2, 192.5.25.82 : CL :
DOMAIN: 192.67.67.53, 26.3.0.103, 128.9.0.107, 192.33.4.12, 128.8.10.90, 26.1.0.13, 128.102.16.10, 192.52.195.10, 192.5.25.82 : COM :
DOMAIN: 192.48.96.2, 192.31.103.3, 128.89.0.92, 192.31.103.4 : DE :
DOMAIN: 129.142.96.42, 192.48.96.2, 192.16.184.4, 192.5.25.82, 130.225.16.40, 129.142.6.64, 129.142.96.41 : DK :
DOMAIN: 192.67.67.53, 26.3.0.103, 128.9.0.107, 192.33.4.12, 128.8.10.90, 26.1.0.13, 128.102.16.10, 192.52.195.10, 192.5.25.82 : EDU :
DOMAIN: 192.12.141.25, 192.5.25.82, 192.48.96.2 : ES :
DOMAIN: 128.214.1.1, 128.214.4.29, 192.48.96.2, 128.121.50.2 : FI :
DOMAIN: 128.93.8.1, 128.93.8.4, 192.5.60.96, 192.16.184.4, 128.112.128.1 : FR :
DOMAIN: 192.67.67.53, 26.3.0.103, 128.9.0.107, 192.33.4.12, 128.8.10.90, 26.1.0.13, 128.102.16.10, 192.52.195.10, 192.5.25.82 : GOV :
DOMAIN: 192.48.96.2, 192.12.141.25 : GR :
DOMAIN: 128.103.1.1, 128.32.136.12, 31.4.0.10 : HK :
DOMAIN: 128.103.1.1, 192.16.202.1, 128.32.136.12, 31.4.0.10, 192.48.96.2 : IE :
DOMAIN: 192.31.103.3, 128.89.0.92, 192.12.141.25 : IL :
DOMAIN: 192.48.96.2, 192.12.141.25 : IN :
DOMAIN: 128.16.5.32, 128.16.8.3 : INT :
DOMAIN: 130.208.165.63, 192.16.202.1, 192.36.125.2, 130.237.216.2, 192.48.96.2, 192.5.25.82, 128.121.50.7 : IS :
DOMAIN: 192.12.192.4, 128.84.254.10, 192.5.25.4, 192.5.21.30, 192.16.202.1, 131.114.1.30, 192.12.194.1, 192.35.82.2 : IT :
DOMAIN: 133.4.1.1, 133.11.7.185 : JP :
DOMAIN: 192.31.103.3, 128.89.0.92, 192.31.103.4 : KR :
DOMAIN: 192.31.103.3, 128.89.0.92, 192.31.103.4 : KW :
DOMAIN: 192.16.202.1, 128.120.2.1, 128.120.2.9 : LK :
DOMAIN: 192.67.67.53, 26.3.0.103, 128.9.0.107, 192.33.4.12, 128.8.10.90, 26.1.0.13, 128.102.16.10, 192.52.195.10, 192.5.25.82 : MIL :
DOMAIN: 128.83.1.33, 131.178.1.1, 128.83.134.2 : MX :
DOMAIN: 192.12.141.25, 192.5.25.82 : MY :
DOMAIN: 128.16.5.32, 128.16.8.3 : NATO :
DOMAIN: 192.67.67.53, 26.3.0.103, 128.9.0.107, 192.33.4.12, 128.8.10.90, 26.1.0.13, 128.102.16.10, 192.52.195.10, 192.5.25.82 : NET :
DOMAIN: 192.48.96.2, 192.12.141.25 : NI :
DOMAIN: 192.16.184.4, 192.5.25.82, 128.93.8.4, 192.16.184.8, 192.48.96.2, 192.36.125.2, 130.237.216.2 : NL :
DOMAIN: 129.240.64.2, 128.39.1.2 : NO :
DOMAIN: 130.217.64.3, 130.217.64.32, 192.31.103.3, 128.89.0.92, 192.31.103.4, 128.102.18.20 : NZ :
DOMAIN: 192.67.67.53, 26.3.0.103, 128.9.0.107, 192.33.4.12, 128.8.10.90, 26.1.0.13, 128.102.16.10, 192.52.195.10, 192.5.25.82 : ORG :
DOMAIN: 129.142.6.64, 129.142.6.65 : PL :
DOMAIN: 134.202.1.105, 134.202.1.107 : PR :
DOMAIN: 128.103.1.1, 128.32.136.12, 31.4.0.10 : PT :
DOMAIN: 192.36.125.2, 130.237.216.2, 130.235.16.11, 192.48.96.2, 128.121.50.2, 192.5.25.82 : SE :
DOMAIN: 128.103.1.1, 128.32.136.12, 31.4.0.10 : SG :
DOMAIN: 192.48.96.2, 192.12.141.25 : TH :
DOMAIN: 128.103.1.1, 128.32.136.12, 31.4.0.10 : TW :
DOMAIN: 128.16.5.32, 128.16.8.3, 192.5.25.82, 128.86.8.25 : UK :
DOMAIN: 128.9.0.32, 128.9.0.33, 192.31.103.6, 128.89.1.178, 192.12.33.51 : US :
DOMAIN: 128.103.1.1, 128.32.136.12, 31.4.0.10 : YU :
--
Ed Anselmo anselmo-ed@cs.yale.edu {harvard,cmcl2}!yale!anselmo-edsmart@mel.dit.csiro.au (Robert Smart) (08/30/90)
The consensus of opinion was that the top level domains known to
the NIC should all support MXes. That isn't to say that the
owner of that top level domain is responsible for everything that
happens below, but that he should impress on the delegated
subdomains the importance of setting up MX records for all
reachable destinations (and not depend on pre-existing %-hack
routes and such). That is certainly what happened in Australia.
So I have changed to using a file generated from a whois command.
Here is an extract from a makefile:
whois %root-dom | awk '/\ / {print $$1}' >/usr/lib/mail/new-top
test -s /usr/lib/mail/new-top
mv /usr/lib/mail/new-top /usr/lib/mail/toplevel
The character after the /\ in the whois line is a tab. This then defines
a sendmail class using an F line. The $$ is to stop make interpreting
the $1 (only use one $ in a shell script).
The point of the exercise is that if new fake domains appear then I
don't have to know about it. And in fact I am sure our major relay
machine (munnari.oz.au) often knows how to get to get to domains
that are on their way but haven't quite made it to the NIC. It also
handles a lot of domains which only make sense in ACSnet.
Bob Smart <smart@mel.dit.csiro.au>keld@login.dkuug.dk (Keld J|rn Simonsen) (09/01/90)
The nameserver for top domain .dk has MX records for all sites reachable in Denmark. Keld Simonsen postmaster@Denmark.Eu.net
Christopher-Vance@adfa.oz.au (09/07/90)
anselmo-ed@cs.yale.edu (Ed Anselmo) writes: | ; [SRI-NIC] NETINFO:DOMAINS.TXT 19-Aug-90 | DOMAIN: 192.31.103.3, 128.89.0.92, 192.31.103.4 : KW : | DOMAIN: 134.202.1.105, 134.202.1.107 : PR : Except that last time I checked, none of the servers listed for these two domains claimed to have an SOA record for the appropriate domain. -- Christopher