Hello, Is there a know issue with 8.5.3 build 6126 outbound Domain Name firewall rules? All of our outbound rules that had a domain name in stopped working since the upgrade.
Thanks
Hello @litmount ,
We are not seeing anything on our customers’ systems. We suggest raising a Peplink Support Ticket (Peplink Ticketing System) and having them review it.
Please post your support ticket number here once it has been raised.
Have a good week,
Marcus 
I have had this issue also on a Balance 710 in our datacenter. In the end it turned that in order to get these rules to work you also need to use the Balance as DNS host. That’s not what we did, our domain controller used Cloudflare as forwarder. After changing that the forwarder to the Balance the rules started to work again.
This all sounds reasonably, but what I do not understand is why it started to be an issue after upgrading to 8.5.3. This DNS configuration has been there for a far longer time.
1 Like
Thanks for sharing. We have the SDX and we are using it to host the DNS and still have this issue. I will probably end up rolling back to previous version.
I have seen a couple of recent changes in the behavior of my home network.
- YouTube has become accessible at all hours on a VLAN where it had previously been limited by scheduled firewall rules. My content-blocking rules exempt YouTube traffic (by host name) from general A/V blocking, but my outbound firewall rules restrict YouTube (by host name) on specific VLANs. In the past, the firewall rules appeared to take precedence.
- Outbound https connections from a GitLab runner have been failing frequently, but not quite 100% of the time. After exempting the runner’s VLAN from content blocking this evening, the next three jobs worked. My outbound firewall rules include a rule that I would expect to allow this traffic; in the past, it appeared to work.
I have not had much time to experiment, but my working hypothesis is that 8.5.3 gives higher precedence to content blocking rules than to outbound firewall rules.