Lars Vogdt wrote:
Am May 11, 2021 9:20:41 PM UTC schrieb Per Jessen <per@opensuse.org>:
Lars, there is an open ticket on why and what was done. Check out 92089.
Would you mind reverting to the using the setup with iodine.enidan.com ?
Fine with me (but at the moment, your server is just added to the list, so it might not receive that much traffic).
Yup, I see it - it's a pretty complex setup you have :-)
But I wonder why you don't collect stats directly on anna/elsa and instead try to work on symptoms?
Do we have anything to go on? looking at my own mailservers, I never have this issue, so why we have it on anna/elsa must be something in the environment.
Note: With relying on just one external DNS server, you make the redundancy of anna/elsa obsolet. If there is a problem with - or in the way to - your server, the whole setup is broken.
True - I certainly didn't want to keep it going for more than a few days.
You are ruining my stats. It has been working a lot better for the last 4-5 days, and using those dodgy cloudflare and google resolvers is not going to help.
Quad9 is marked as privacy friendly and GDPR conform. The Google and Cloudflare ones are the usual suspects of reliable (while privacy unfriendly) DNS with quick round-turn times. I'm happy to discuss which forwarding DNS we can/should use for our internal hosts.
I only said 'dodgy' because one of them seems to cause the problems.
Worst case, we can even skip forwarding and always ask the root DNS. What's your opinion?
That would be my suggestion now - get rid of the forwarders. You have eliminated dnsmasq, but there are still 'no host found' in the log. -- Per Jessen, Zürich (11.9°C) Member, openSUSE Heroes