out of place mx records.

Mike Bernhardt bernhardt at bart.gov
Fri Oct 29 15:59:29 UTC 2010


I'd like to suggest an alternative reason for the presence of those records:
The Perl script H2N will install them by default for every single host in
the zone file, unless you use the -M option to suppress their creation.

Obviously this has nothing to do with the value, or lack thereof, of those
records. But in answer to your original question, it may be that the only
reason they exist in your environment is that your predecessor used H2N with
minimal customization to generate the zone file.




More information about the bind-users mailing list