starred/modoboa-modoboa

Fork 0

mirror of https://github.com/modoboa/modoboa.git synced 2026-04-26 09:26:00 +03:00

[GH-ISSUE #2038] Improve DNS checks to allow DNS servers not working temporary #1511

New issue

Closed

opened 2026-02-27 11:17:28 +03:00 by kerem · 5 comments

kerem commented

2026-02-27 11:17:28 +03:00

Owner

Originally created by @MrGeneration on GitHub (Oct 20, 2020).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/2038

Impacted versions

Modoboa: 1.16.1
installer used: Yes
Webserver: Nginx

Steps to reproduce

Force your DNS resolver to be unavailable for a moment (for whatever reason).

Current behavior

Modoboa regulary tries to resolve all relevant DNS entries for configured domains if enabled.
It will, in case e.g. a MX record no longer can be found, send a mail to the domain owner to inform about this issue.

Expected behavior

If Modoboa is unable to query the DNS server for a moment it should temporarily ignore this issue (maybe change the record from green to yellow to indicate a temporary issue) and maybe inform the instance owner. The logfile states a resolution timeout:

Issue #1023 technically would be very useful in such an situation as well.

TL;DR

If DNS resolution fails inform instance owner and do not thread this situation as non existent DNS record.

Originally created by @MrGeneration on GitHub (Oct 20, 2020). Original GitHub issue: https://github.com/modoboa/modoboa/issues/2038 # Impacted versions * Modoboa: 1.16.1 * installer used: Yes * Webserver: Nginx # Steps to reproduce Force your DNS resolver to be unavailable for a moment (for whatever reason). # Current behavior Modoboa regulary tries to resolve all relevant DNS entries for configured domains if enabled. It will, in case e.g. a MX record no longer can be found, send a mail to the domain owner to inform about this issue. ![image](https://user-images.githubusercontent.com/6549061/96621148-8eb7ac00-1308-11eb-94a9-fc3e7c9e1a02.png) # Expected behavior If Modoboa is unable to query the DNS server for a moment it should temporarily ignore this issue (maybe change the record from green to yellow to indicate a temporary issue) and maybe inform the instance owner. The logfile states a resolution timeout: ![image](https://user-images.githubusercontent.com/6549061/96621394-db02ec00-1308-11eb-8e80-6d861e003d5e.png) Issue #1023 technically would be very useful in such an situation as well. # TL;DR If DNS resolution fails inform instance owner and do not thread this situation as non existent DNS record.

kerem

2026-02-27 11:17:28 +03:00

closed this issue
added the
feedback-needed

stale
labels

kerem commented

2026-02-27 11:17:29 +03:00

Author

Owner

@tonioo commented on GitHub (Oct 21, 2020):

@MrGeneration Actually you can already disable tests for a specific domain. Is it not enough?

@tonioo commented on GitHub (Oct 21, 2020): @MrGeneration Actually you can already disable tests for a specific domain. Is it not enough?

kerem commented

2026-02-27 11:17:29 +03:00

Author

Owner

@MrGeneration commented on GitHub (Oct 21, 2020):

While this is true, this was temporary affecting 50% of my domains due a temporary route issue to the affected DNS servers.
So sadly, no this wouldn't be an option.

Personally I think that the DNS check should be robust enough to know the difference between a simple timeout or NXDOMAIN. Because this would also allow you to throw different errors.

I really love the domain check functionality and am using it where ever possible.

@MrGeneration commented on GitHub (Oct 21, 2020): While this is true, this was temporary affecting 50% of my domains due a temporary route issue to the affected DNS servers. So sadly, no this wouldn't be an option. Personally I think that the DNS check should be robust enough to know the difference between a simple timeout or `NXDOMAIN`. Because this would also allow you to throw different errors. I really love the domain check functionality and am using it where ever possible.

kerem commented

2026-02-27 11:17:29 +03:00

Author

Owner

@stale[bot] commented on GitHub (Dec 22, 2020):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale[bot] commented on GitHub (Dec 22, 2020): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

kerem commented

2026-02-27 11:17:29 +03:00

Author

Owner

@MrGeneration commented on GitHub (Dec 23, 2020):

I still believe that modoboa should handle not reachable DNS servers better. :x

@MrGeneration commented on GitHub (Dec 23, 2020): I still believe that modoboa should handle not reachable DNS servers better. :x

kerem commented

2026-02-27 11:17:29 +03:00

Author

Owner

@stale[bot] commented on GitHub (Feb 21, 2021):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale[bot] commented on GitHub (Feb 21, 2021): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.