Since we cleaned up 44.130/16 a while ago, we have
some hints for your
first cleanup round. Maybe you should consider taking obsolete CNAME-
and MX-records into account. Example:
to-be-deleted.txt:
g7suh IN A 44.131.254.242
ampr.org:
2e1arm IN CNAME g7suh
Yes, please take good notice of that!
Some time ago I have made a lot of effort to delete all dangling CNAME and MX
records, hundreds of them.
Apparently there have been cleanups where entire subnets worth of A records were
deleted, but many MX and CNAME records still referred to them. It looks like
at some time, for every A record created in certain US subnets, a corresponding
MX record (just "call IN MX 10 call") had been created. A bit pointless, but
worse is that those were not removed when the A records were removed.
This time around, please make sure that whenever some record is removed, all
records that point to it are also removed.
As Jann correctly points out, there are MX records that point to external servers
(although sometimes the trailing period was forgotten, making them inoperative).
During the above cleanup, I found several of those that do not exist in DNS anymore,
and deleted them as well. I did not check if the ones that still resolve would
offer SMTP service and would accept mail to the specific domain name (in .ampr.org!).
Probably lots of them don't.
This weekend I sent out a mailing about renewing registration by tacking @amsat.org
@veron.nl and @vrza.nl to all callsigns (the latter are two amateur societies here)
and of course I got many delivery failures back where the address at the aliasing
service exists, but the address the mail is forwarded to no longer exists.
We are not the only one with this cleanup problem...
Rob