Skip to content

FYI: upstream cannot be forced - requires nginx plus #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
darylteo opened this issue Aug 4, 2024 · 0 comments
Open

FYI: upstream cannot be forced - requires nginx plus #5

darylteo opened this issue Aug 4, 2024 · 0 comments

Comments

@darylteo
Copy link

darylteo commented Aug 4, 2024

Based on my own research, unfortunately it does not seem to be possible to force dns lookup for upstream

https://nginx.org/en/docs/http/ngx_http_upstream_module.html

Dynamically configurable group with periodic health checks is available as part of our commercial subscription:

Which allows

upstream dynamic {
    zone upstream_dynamic 64k;

    server backend1.example.com      weight=5;
    server backend2.example.com:8080 fail_timeout=5s slow_start=30s;
    server 192.0.2.1                 max_fails=3;
    server backend3.example.com      **resolve**;
    server backend4.example.com      service=http resolve;

    server backup1.example.com:8080  backup;
    server backup2.example.com:8080  backup;
}

Additionally, the following parameters are available as part of our commercial subscription:

resolve
monitors changes of the IP addresses that correspond to a domain name of the server, and automatically modifies the upstream configuration without the need of restarting nginx (1.5.12). The server group must reside in the shared memory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant