Hello.
I wanted to inform you that after the 4.6.4 update I am experiencing problems with the DNS part of our internal email server application called "MailCow". It seems like I can no longer resolve addresses correctly. I tried downgrading to 4.6.2 while keeping the settings but the problem persists. Putting the email server DNS resolutions on another router does not cause problems. I'm sure it's due to the update because this DNS verification problem also blocked email reception and it happened immediately after upgrading to 4.6.4.
Hi,
When you downgrade the firmware, please without 'keep settings', if the DNS resolutions work?
1 Like
Do you have vpn? Is there anything special for your settings?
1 Like
Did the router enable the VPN Killswitch and AGH?
1 Like
Thank you for the replies.
Unfortunately the system is in production and I cannot reset the router.
To answer your questions:
- I use wireguard VPN (I tried both activating and deactivating the blocking of traffic outside the VPN)
- I don't use AGH or KILL SWITCH
I solved the problem by simply telling my company router to forward mailcow's DNS requests to another router and now everything works.
The Mailcow component that no longer started and blocked the entire email server is this: NLnet Labs - Unbound - About
1 Like
So is this an Unbound issue?
I would not know. Mailcow is updated in August. The problem appeared immediately after I updated the router from 4.6.2 to 4.6.4. Of course, it could also be a BUG in this component triggered by the router update. For now, however, I have solved the problem by turning the DNS requests to a second router by managing the TRUNKS of my company router which on WAN1 has the Glinet router with VPN on a VPS in Wireguard and on WAN2 something similar but with Zyxel router and VPS managed by a local internet operator.