I'm a Linux system administrator and I've been tasked with exploring a solution for configuring a proxy DNS that can change the domain of requests. My company develops an App that we deploy as a SaaS for various clients, and it has a plugin to connect with Jira. Due to recent changes from Atlassian, this plugin will no longer work in three months. Our clients, some of whom host the App themselves, currently use our SaaS-hosted plugin. However, after three months, the plugin will solely rely on being listed in the Atlassian marketplace, meaning clients will need to manually add approved domains for the plugin to function. The developers are asking if it's feasible to set up a server that takes clients' URLs, rewrites them to our domain, and allows the plugin to operate correctly. For example, requests would flow like this: client (client.com) → DNS server → mycompany.com → plugin in Atlassian. I'm skeptical if this is possible as it seems like it would require special routing software rather than a traditional DNS server. Are there any open-source solutions for routing like this on a Debian server?
4 Answers
Definitely a tricky situation! You could use a method like a 301 redirect that changes users' requests to the new URI. In the past, Squid could handle URL rewriting, but I'm unsure if it's still reliable with modern setups. There could be compatibility issues with new generation firewalls or load balancers, so just keep that in mind.
You might want to look into using a proxy tool like Charles Proxy for this task. Apache could also be a suitable option for the configuration you’re considering. Plus, if the connections need to be secure, remember to discuss TLS requirements with the developers. It’s critical to avoid sending any sensitive data over HTTP, especially online.
What you're trying to do is definitely possible, though it might get complicated. You might want to explore load balancers like F5 or services like Cloudflare, which can handle URL rewrites, although managing client traffic through them can be tricky. But it's a solid direction to consider.
You can easily create subdomains like (client).mycompany.com, but you can't directly rewrite (client.com) since you don't control its DNS. If clients can point their DNS to your server, then you can issue a 301 redirect at the HTTP level. Just be sure they'll need to provide you with an SSL certificate since all browsers are moving to HTTPS.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures