6

Without too much info about your network, or your knowledge we can only take a guess at how to go about this, my guess was using the hostname to service entry and unchecking filter-private.

This is how it works on my network since I also host many sites and want to access them without using a port. I will spare you the technical headache of my setup, and try and simplify a basic example:

Usually if you want to access your local site it requires a local IP and a port number. When you try to perform a query to your Web Server behind your firewall it won’t let you reach it by DNS name because it is blocked by default as a security measure upstream.

So let’s say you run your company Web server behind the firewall locally @ 192.168.1.x and you want to access the main page/service which is usually port 80/443 you would put in http://192.168.1.30:80 or https://192.168.1.x:443 That should work regardless when on site. Your outside IP will also work as long as you are port forwarding that service like http://youroutsideIP:80 or https://youroutsideIP:443

Now if you are hosting this with an A record on a web host like Godaddy it will have a dns entry for your website at that static outside IP address: youroutsideIP = yourwebsite.com.
If you have cnames that are being redirected to other ports of that site, then you would have them located at something like http//:192.168.1.x:9670 points to a cname http://service1.yourwebsite.com
^This example assumes that the Web Server is doing redirects with something like nginx, which let’s you define the ports of the service being redirected.

This is all well and good if you can access the main site page locally, but if you can’t get there with the DNS name from inside then that means the firewall is blocking the upstream WAN entry loopback, or there is a port forwarding issue to the outside world.