1
23.7 Legacy Series / Re: NGINX and dynamic load balance using FQDN hosts
« on: December 07, 2023, 01:25:44 am »
I think I got my answer, never.
Thanks!
Thanks!
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
2
23.7 Legacy Series / NGINX and dynamic load balance using FQDN hosts
« on: November 29, 2023, 07:23:36 pm »
Hi all!
Today I faced an issue with AWS load balancer and OPNSense as WAF and it was about using FQDN hostnames (or DNS hosts as you wish).
Cloudfront passes through OPNSense NGINX to reach app servers.
It turns out that I can't get the full potential of AWS load balancer and autoscaling since NGINX will work with static IPs resolved at daemons initialization, restarting or reloading.
I've found out that setting a dns resolver and using domain name (upstream server) in a variable may provide DNS refreshing interval as the user wishes ignoring DNS record TTL (can be seen in https://www.nginx.com/blog/dns-service-discovery-nginx-plus/ topic Setting the Domain Name in a Variable).
The question then is if would be possible to work in NGINX plugin to admit such autoscaling scenario? It would be extremely useful to AWS users and containerization.
Thanks in advance!
Today I faced an issue with AWS load balancer and OPNSense as WAF and it was about using FQDN hostnames (or DNS hosts as you wish).
Cloudfront passes through OPNSense NGINX to reach app servers.
It turns out that I can't get the full potential of AWS load balancer and autoscaling since NGINX will work with static IPs resolved at daemons initialization, restarting or reloading.
I've found out that setting a dns resolver and using domain name (upstream server) in a variable may provide DNS refreshing interval as the user wishes ignoring DNS record TTL (can be seen in https://www.nginx.com/blog/dns-service-discovery-nginx-plus/ topic Setting the Domain Name in a Variable).
The question then is if would be possible to work in NGINX plugin to admit such autoscaling scenario? It would be extremely useful to AWS users and containerization.
Thanks in advance!
Pages: [1]