Search the Community
Showing results for tags 'mx record'.
Found 1 result
-
Ok here's a weird one that I can't figure out how to fix without breaking other things. My server is part of a wireguard network, so it has an interface with a private IP, and my home network resolves the server hostname to the wireguard IP. Since this breaks access to the default vhost (i.e. Froxlor itself), I added the internal IP to the IPs and Ports. This seems to work fine. However..apparently Froxlor is for some reason adding that IP as an A record for the MX server, which is causing some mail filters to reject mail for my hosted domains. So basically mx.mydomain.com is resolving to all IPs added to froxlor, including the private one. Doing some quick testing as I'm writing this..and it seems that it's actually resolving *.mydomain.com to all the IPs in Froxlor..so the issue is even weirder than I thought. Any ideas/suggestions? If all else fails I can remove the IP from Froxlor..but then I have to access Froxlor by public IP instead of hostname (and click through the cert screaming at me for that..if it even allows me to access...). Thanks!
