dynamic dns issue

Anyone has any clue? I am doing as follows:

For the first, in web server I select my internal server and set the port to 80

Then in waf I select the wan address, I set  the port to 80 and in domains I enter the first dyndns hostname

For the second, in web server I select my internal server and set the port to 8090

Then in waf I select the wan address, I set  the port to 80 and in domains I enter the second dyndns hostname

Last for the third, in web server I select my internal server and set the port to 9090

Then in waf I select the wan address, I set  the port to 80 and in domains I enter the third dyndns hostname

After applying, no matter what dyndns address I enter in the browser, they all redirect to the first one..

I am at loss..

Make sure that in WAF rule you select the right webserver as well.

Hello and thanks for your reply!

In web server I add a name, the IP of my internal webserver (192.168.1.100), type is plainntext http and I enter the port 8090.

Then in WAF I give the rule a name, in hosted address I select my WAN port, listening port is 80. In the domains I add the dynamic dns hostname. Finally in Web Server I select the one I created.

Do you know if my above settings are correct? In any case I do select the correct server, yes. However all 3 dynamic dns addresses end up to the same path (192.168.1.100:80)

As a test, just in case the issue is happening somewhere due to the fact that all ddns hostnames connect to the same internal ip (but on different ports), I added a different internal server (192.168.1.110) in web server. Still the same. When I enter the dyndns address on the browser I end up again in the 192.168.1.100:80 website

Under ' Hosted server'

1. add the hosted address (WAN address)

2 Listening Port

3. Domain

Under ' Protected Servers'
Select the right web server (you should have defined three)

This is exactly what I have done..

Below is the webserver. The host is the name of the internal server (ip 192.168.1.100)

And this is the waf rule. As you can see the correct is selected

Am I doing something else wrong, perhaps ? Do my settings seem correct? 

If from inside the network I type http://IP_of_insomniamainsrv:8086 I go to the desired destination

But after saving the rule if I enter xxxxx.ddns.net (the specified dyndnshostname) I go to http://IP_of_insomniamainsrv:80

And does the actual webserver serve on the three different ports (vHosts)?

Did you test that these ports are serving to the ports as defined in the Webserver definition?

Sorry edited the message above

From inside the network if I go to  IP_of_insomniamainsrv:80 , it goes to the root of the webserver (let's say I use srv.ddns.net for this). Entering  srv.ddns.net I indeed see the website in port 80  (the address on the browser is srv.ddns.net )

 From inside the network if I go to  IP_of_insomniamainsrv:8086  it goes to motion (let's say I use motion.ddns.net for this). Entering  motion.ddns.net I see again the website in port 80  (the address on the browser is motion.ddns.net now)

From inside the network if I go to  IP_of_insomniamainsrv:8096  it goes to emby (let's say I use emby.ddns.net for this). Entering  emby.ddns.net I see again the website in port 80  (the address on the browser is emby.ddns.net now)

????

i would suspect that when testing on any computer in your network, when you enter IP_of_insomniamainsrv:8086, it serves you a page, same goes for the other two webserver addresses.
Did you test this happens?

i would suspect that when testing on any computer in your network, when you enter IP_of_insomniamainsrv:8086, it serves you a page, same goes for the other two webserver addresses.
Did you test this happens?

From inside the network from a computer if I go to

1. http:/IP of webserver --> goes to the page I want. The same happens when I enter http://srv.ddns.net

2.  http://IP of webserver:8086 --> goes to the page I want (the motioneye web interface). However entering http://motion.ddns.net goes again to the page above

3. http://IP of webserver:8096 --> goes to the page I want (the emby web interface). However entering http://emby.ddns.net goes again to the first above

These 3 dyndns hostnames were working as they should for years with sophos UTM.. I try to do the same now with XG and nope.. Apparently I am missing something but cannot understand what.. I mean If I got a "This site can't be reached error" it would mean that something is missing indeed, but the fact that all 3 redirect to the same site is something that I fail to understand.. All hostnames of course resolve to the same wan address, but this has always been the case.

As mentioned this scenario has been working for years with the UTM. The "real" webserver was the ip:port of the internal and the "virtual" was the dyddns hostname