generated from nginx/template-repository
-
Notifications
You must be signed in to change notification settings - Fork 120
Labels
product/nginx-plusIssues related to NGINX Plus (and NGINX Open Source in docs.nginx.com)Issues related to NGINX Plus (and NGINX Open Source in docs.nginx.com)
Description
Describe the bug
On this page, https://docs.nginx.com/nginx/admin-guide/load-balancer/udp-health-check/#example-test-for-dns
The send
and expect
parameters are confusing and misleading. They cannot (and should not) be used to create a working DNS health check.
To reproduce
Steps to reproduce the behavior:
- Configure NGINX Plus with the example
match
configuration. - Watch all health checks fail
- Notice that NGINX Plus is requesting a DNS lookup for *stlu.msl.edu which is bad for the servers in the upstream group and bad for any subsequent DNS server that will handle this request. And it's bad for Massachusetts School of Law.
Expected behavior
- Docs should explain that DNS health checks require configuration to be made on the DNS server.
- Docs should provide a means for creating the hex string to send a DNS lookup
- Docs should explain what the
expect
value should be based on 1 & 2
Metadata
Metadata
Assignees
Labels
product/nginx-plusIssues related to NGINX Plus (and NGINX Open Source in docs.nginx.com)Issues related to NGINX Plus (and NGINX Open Source in docs.nginx.com)