Messages are not delivered from the queue with the error message "domain lookup error"
Solution
In order to resolve domain names, Axigen uses the DNR service which performs DNS queries and caches results. In order for this service to function correctly it is required that the nameservers provided by your Service Provider be configured in the service.
For details regarding the configuration steps of this service please see the following page in our online documentation resource available at the following address: https://www.axigen.com/docs/en/DNR-Settings_94.html
The most common reasons for the encountered error message and possible resolutions are detailed below:
- The recipient domain name is mis-spelled (examplee.com instead of example.com) for one or more of the message's recipients, this will cause the error message if the mis-spelled domain name does not exist or it does not have any MX or A records. The solution is to inform the sender of this error if it is a local account to resend the message using the corrected recipient address.
- No nameserver IP addresses are configured in the DNR service causing any remote messages to fail to deliver. The solution is to properly configure the DNR service as per the online documentation mentioned above.
- The domain name cannot be resolved due to a bad configuration or missing information (missing valid MX and A records) on behalf of the nameserver hosting the respective domain. The solution is to contact the domain owner using alternative ways to inform him about the encountered problem.
- The DNR service is unable to contact any of the configured nameservers due to connectivity issues or network mis-configuration. The solution is to check any firewall rules, network routes and service availability issues.
If none of the provided solutions resolve the encountered domain lookup error please contact the support department and mention that the solutions provided in this article do not apply for your particular case.
For details regarding the configuration steps of this service please see the following page in our online documentation resource available at the following address: https://www.axigen.com/docs/en/DNR-Settings_94.html
The most common reasons for the encountered error message and possible resolutions are detailed below:
- The recipient domain name is mis-spelled (examplee.com instead of example.com) for one or more of the message's recipients, this will cause the error message if the mis-spelled domain name does not exist or it does not have any MX or A records. The solution is to inform the sender of this error if it is a local account to resend the message using the corrected recipient address.
- No nameserver IP addresses are configured in the DNR service causing any remote messages to fail to deliver. The solution is to properly configure the DNR service as per the online documentation mentioned above.
- The domain name cannot be resolved due to a bad configuration or missing information (missing valid MX and A records) on behalf of the nameserver hosting the respective domain. The solution is to contact the domain owner using alternative ways to inform him about the encountered problem.
- The DNR service is unable to contact any of the configured nameservers due to connectivity issues or network mis-configuration. The solution is to check any firewall rules, network routes and service availability issues.
If none of the provided solutions resolve the encountered domain lookup error please contact the support department and mention that the solutions provided in this article do not apply for your particular case.
OS:
LinuxWindowsFreeBSDNetBSDOpenBSDSolaris
Distros:
WindowsDEB based distros amd64FreeBSD 7.x