I doubt the engineering would add this feature. NAT hairpinning is not a standardized feature recommended by any RFCs, and using this feature adds inefficiencies to a network.
You have not answered on my previous question. When you can establish a straight forward link connection, why do you want to add a third device to route the traffic?
Did you ever figure this out. I have 2 test domains through NO-IP and externally if I use the URL no problems. Internally with the url no luck.
I did what was instructed which is add a DNS Server entries for my sites, and add NO-IP info for the sites in Dynamic DNS. Everything else I have tried does not work. Hoping you have more insight.
Where did you add that DNS entry? On G3100? Or on your computer?
Could you screenshot the Static DNS page on G3100? With your URL partially blurred out to protect privacy.
Something weird I just noticed today. If I go on my phone I have no issue connecting to my internal website, but on my wired machine there is an issue. I am going to have to check on other devices but see if you use a mobile device if the site opens.