On April 1, 2021, we are moving all of our QuotaGuard Support Documentation to
https://quotaguard.github.io/qg-docs/
Please Update Your Support Bookmarks
Documentation for this article will be maintained at
https://quotaguard.github.io/qg-docs/quickstart-ruby
Please click on the above link to ensure you are reading
the most recent and updated documentation.
The short answer is… it depends.
By default, QuotaGuard Static allows you to route outbound traffic from your app via a Static IP, for example, to access a database behind a firewall.
If you want to route inbound traffic via a static IP to your application, then you need to do a bit more configuration, and it comes with some caveats.
#1 - Creating a DNS record to point to a Heroku application
If you are doing this to try and setup DNS rules for your Heroku app (for example pointing myapp.com to your Heroku app) you should do this via a CNAME, not via an A record on the IP address.
You can find out more at this link about how to set up Inbound Proxies for your Heroku application.
#2 - Clients of your website have strict internal firewall controls and can only access websites with a specific IP address
If you have clients that can only access specific sites on the internet and you need a static IP address that they can add to their firewall then you can use QuotaGuard Static. Simply follow the instructions here to get started: http://support.quotaguard.com/solution/articles/5000633969
Caveat
- You cannot just enter in the Static IP address. Multiple accounts may be sharing the same IP address, so without using a hostname in your URL, we are unable to determine which account to route traffic to correctly.