One of our email recipients has 17 mx records, and our emailing program postfix on linux does not retrieve these records. When using dig, the same thing happens.
This command returns no mx records
>dig mx fnb.co.za
But when using +trace, the records get returned
>dig mx fnb.co.za +trace
The question is whether there is a setting we can make to make the standard mx lookup work properly.
Thanks
shouldn't you use:
dig -t mx fnb.co.za.
Technically at least under Linux, man page says that:
dig fnb.co.za. mx
works as well (resource name followed by type)
Even though I had success with the order you mentioned too... but it's not documented that way. At least on on my dig man page.
The command line variations still do not return the MX records for the domain
They work for me. For that domain. Maybe something is getting blocked on your side??
If this is from a Linux host, try the "host" command as well:
host -t mx fnb.co.za.
That is great feedback, it indicates that we have some underlying setup problem on our Linux system/firewall whatever, maybe a packet sizing issue or firewall port 53, those are indicated in postings.
Thanks for trying it out.
---------- Post updated at 09:48 AM ---------- Previous update was at 09:44 AM ----------
This works too:
dig @8.8.8.8 -t mx fnb.co.za.
So that further indicates an issue with our own DNS setup..