Re: [exim] MX record exists but exim doesn't detect it

Top Page
Delete this message
Reply to this message
Author: basti
Date:  
To: exim-users
Subject: Re: [exim] MX record exists but exim doesn't detect it
Am 27.12.20 um 21:12 schrieb Jeremy Harris via Exim-users:
> On 25/12/2020 13:01, Sagar Acharya via Exim-users wrote:
>> The central problem is however, that dig gives me the correct MX
>> record and nslookup doesn't. MX record exists, just exim is not able
>> to find it.
>>
>> I even tried this email id. It gives these prompts
>> ...
>> dnslookup router called for sagaracharya@???
>>       domain = tutanota.com
>> tutanota.com in "*"? yes (matched "*")
>> DNS lookup of tutanota.com (MX) gave TRY_AGAIN
>> ...
>>
>> How does exim find DNS? Which command does it particularly use?
>
> Exim uses a library routine called res_search().
> It does not use a command (meaning en executable program).
>
> The library accesses the system facilities for getting DNS results.
> How those work are not under Exim's control, beyond the API of
> the library.


dig ask the nameserver "directly". so it looks like a dns problem of
your host. what does dig say if you query nameservers list in
/etc/resolv.conf?

dig <some query> @nameserver