15
2
We use a (poorly-designed) application that requires the IP address of our corporate office which has a static public IP address. However, when our failover internet kicks in, it obviously has a different static public IP address and then remote connections fail.
If the application would accept a domain name, I would use that with dynamic DNS, but it doesn't accept a domain name.
Is there any way to input an IP address but get to our domain name? I had two thoughts that I haven't tried yet.
Set up a local IP address that redirects to our domain name (e.g. 10.0.1.99 goes to local.ourdomain.com). However, I'm not quite sure how I would do this. Set up a Raspberry Pi with a web server maybe.
Purchase web hosting with a dedicated IP address and have it redirect to our domain which then could get updated as needed.
Any thoughts on how to achieve this?
1What kind of application? You mean something hosted internally? Like some kind of Ruby or Java or even JavaScript framework? – JakeGould – 2017-12-04T02:54:58.277
1Reverse proxy. Stick it at a fixed address and have it forward packets to the appropriate address. – Ignacio Vazquez-Abrams – 2017-12-04T02:55:27.107
Just a Windows program that a vendor has provided to us which sends and retrieves data from our corporate office. – MrPeanut – 2017-12-04T02:56:05.717
@IgnacioVazquez-Abrams Something like a Raspberry Pi running Nginx as a reverse proxy? – MrPeanut – 2017-12-04T03:07:29.927
Nginx, netfilter, ebtables, whatever you need. – Ignacio Vazquez-Abrams – 2017-12-04T03:08:32.433
Ok, thanks. I've never configured Nginx but there seem to be plenty of tutorials on setting it up as a reverse proxy and a RPi is easy enough. I'll look into this more. – MrPeanut – 2017-12-04T03:14:17.453
2You’re going to have to host a reverse proxy somewhere with an IP address that never changes. That will cost money. Have you considered just moving the service to the cloud where redundancy is built in anyways? The cost is probably similar. The other suggestion of using a VPN makes a lot of sense. I don’t see how a reverse proxy is a good solution to this at all. – Appleoddity – 2017-12-04T05:51:41.687
Are you using Reverse DNS and referring to PTR records? I'm guessing probably not (that's a bit more advanced). That is how "IP address that redirects to our domain name (e.g. 10.0.1.99 goes to local.ourdomain.com)." I find it much more likely that you have an A record, so local.example.com goes to 10.0.1.99. Being able to keep that straight may be essential to being able to craft a working solution. If your software app communicates through a firewall, NAT might be useful. – TOOGAM – 2017-12-04T06:09:23.530
@Appleoddity The cost of "host a reverse proxy somewhere with an IP address that never changes" is "buy a raspberry pi and configure it". The device after all needs nothing but a static IP address in the local network (and if that one fails no solution will work). Moving to the cloud is a repeated cost every month, just as a VPN is. – Voo – 2017-12-04T12:47:58.910
@Voo either I’m misunderstanding the question or you are. The problem here that I see is that there are external clients trying to connect to a server on-premise. If the company’s public IP changes due to a failover event, the external clients can’t connect. So you tell me how a reverse proxy hosted on premise is going to solve that? – Appleoddity – 2017-12-04T13:17:11.950
1@Appleoddity The reverse proxy is simply the implementation of bullet point 1 of the OP. You don't have the raspberry in the corporate office but in the local network where the application is being run. Since that's feasible in the given scenario according to the OP, it's probably the simplest and cheapest solution. – Voo – 2017-12-04T13:49:01.020