Part 6 - Access from internal networksIf you try to access your URL "your_service.your_subdomain.dedyn.io" from a device in your internal network, it should fail.There are two ways of fixing this. I will cover both options but keep in mind that Option B is the suggested way of doing it.NAT reflection is an inferior solution since you lose the ability to track originating source IP in HAProxy when going through NAT. (@sorano)Option A - NAT Reflection (https://docs.opnsense.org/manual/nat.html)Option B - Split DNS (https://docs.opnsense.org/manual/unbound.html#overrides)Option A - NAT Reflection In your OPNsense go to: Firewall --> Rules --> WAN Here you will have to edit the two rules (HAProxy HTTP and HAProxy HTTPS) we created in Part 4 - Step 3 of this tutorial. At the bottom of each rule there is a setting called "NAT reflection = Use system default". You will want to change this to "NAT reflection = Enable". Access from internal networks should now be working.Option B - Split DNS (DNS Overrides)Since you are using OPNsense you are probably also using the Unbound DNS plugin as your local DNS server.Because of that you can easily set up DNS overrides. In your OPNsense go to: Services --> Unbound DNS --> Overrides Here you will need to create "Host Overrides" for each of your services. At least if you are using 2nd level subdomains "your_service.your_subdomain.dedyn.io" for you services. If you are running all of your services on your 1st level subdomain "your_subdomain.dedyn.io" than you will just need to override this one. The IP address can be any interface IP of your OPNsense, I am using the LAN IP on which the "SNI_frontend" is also listening on because we set it to "0.0.0.0". Access from internal networks should now be working.