Hi, i have a requirement where i have several domains that i need to loopback to a local IP address. I have read that most decent enterprise routers can loop back the outgoing request to a local IP. Called NAT loopback or DNS rebinding.
I forgot to mention that i would like to send them to specific ports, is this possible?
When i tried the domain url internally over HTTPS, i get a certificate error, it shows its issued for www.captive-portal.peplink.com when the domain url has it’s own certificate that the request isn’t reaching.
Expand on this requirement please - perhaps an example?
That is the https cert for the inbuilt captive portal on the peplink. Add the local dns entries above to your router and flush your DNS cache on your PC and you should get redirected directly to the local LAN IP when you visit those URLs where the SSL cert would work as expected.
So i am after any internal any outbound request to those domains above gets routed back to a local IP with specific port (over a SSL connection) - I thought once i knew how to redirect it, i could work that bit out… but i’ve clearly failed.
I hadn’t flushed the DNS (forgot) but have since flushed it with ipconfig /flushdns and the issue persists.
So i have tried going to the domains above in a browser and i continue to get the SSL error (Edge) When i try in Chrome i get a 404 but with the routers MANGA address: https://subdomain.mydomain.com/cgi-bin/MANGA/index.cgi (also i cleared the browser caches)
If i ping the domain name from my computer it responds with the routers WAN IP address not the final destination IP
That’s a fault you need to track down. Check that the PC you are testing from has the Peplink set as its DNS server. You’ll know its working as expected when you ping the domain names and get a local IP.
Also. go and change the web admin port away from 443 on your peplink. Eg, make it 4443, just to get the web interface of the router itself out of the way.
If you have the local dns entries on your Peplink and you ping the dns name and it still brings back the public IP then first thing to try is a flush of your local resolver cache (ipconfig /flushdns) in windows.
Then do a nslookup from your PC against the dns name and check it returns the internal IP.
Turn on DNS caching on the Peplink and apply changes (you shouldn’t need it but maybe that will restart the DNS server internally). If that doesn’t fix it reboot the router.
