"
Not exactly sure if it's the same issue, but it feels very much related:
With Unbound DNS enabled (blocklist disabled) some of my client devices resolved non-existent FQDNs to CloudFront IP addresses. For example, opening http://xxxxxxxxxxthisdoesntexistxxxxxxxxx.com in a browser (http not https!) showed a CloudFront page saying: 403 ERROR The request could not be satisfied. (attached screenshot)
In my case I managed to solve the issue by adjusting the following OPNsense settings under System -> Settings -> General (not sure which one it was, likely the first):
* Domain: home.arpa (had it set to "house" before)
* Prefer IPv4 over IPv6: yes
Then restarted the firewall, reconnected all clients (renew DHCP leases) and the issue was gone.
With Unbound DNS enabled (blocklist disabled) some of my client devices resolved non-existent FQDNs to CloudFront IP addresses. For example, opening http://xxxxxxxxxxthisdoesntexistxxxxxxxxx.com in a browser (http not https!) showed a CloudFront page saying: 403 ERROR The request could not be satisfied. (attached screenshot)
In my case I managed to solve the issue by adjusting the following OPNsense settings under System -> Settings -> General (not sure which one it was, likely the first):
* Domain: home.arpa (had it set to "house" before)
* Prefer IPv4 over IPv6: yes
Then restarted the firewall, reconnected all clients (renew DHCP leases) and the issue was gone.
