Hello,
As far as I recall, the NGINX resolver does not support search domains,
and thus, the resolver_conf_parsing patch[1] doesn't either.
I am not sure if NGINX Plus supports it. Possibly, considering the
resolver bundled with it supports SRV records[2], but I don't have
access to an NGINX Plus instance to try it.
My suggestion would be to run dnsmasq[3] alongside OpenResty and
configure the NGINX 'resolver' directive to point to it, like so:
resolver
127.0.0.1:53
Or using a pure Lua-land DNS resolver, such as:
https://github.com/Kong/lua-resty-dns-client
It supports search domains and various resolv.conf options (see 'man 5
resolv.conf'), even if specified as environment variables.
Best,
Thibault
[1]:
https://github.com/openresty/openresty/blob/master/patches/nginx-1.15.8-resolver_conf_parsing.patch
[2]:
https://www.nginx.com/blog/dns-service-discovery-nginx-plus/
[3]:
http://thekelleys.org.uk/dnsmasq/doc.html
> --
> You received this message because you are subscribed to the Google
> Groups "openresty-en" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to
openresty-en...@googlegroups.com
> <mailto:
openresty-en...@googlegroups.com>.
> For more options, visit
https://groups.google.com/d/optout.