-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
request help: APISIX retuen error 3 name error with multi Consul DNS #8345
Comments
hi @Fabriceli , I eventually tracked it down here: https://github.com/openresty/lua-resty-dns/blob/master/lib/resty/dns/resolver.lua#L870-L896
in your scenario, yes |
How to fix it ? |
I don't think it needs to be fixed. I think this is a new feature. I don't have any good ideas to implement it at the moment. |
When can add this new feature? or make a discussion about this feature at next Community Weekly Meeting |
@tzssangglass I think a good way to support this is to let users define multiple DNS service registries, and for each registry, one can define a group of DNS servers, which are the same for the domain resolving. While for different DNS service registries, the resolve result might be different. |
I think on a high level, this requires APISIX discovery mode to support multiple clusters and orchestrate query rules. |
Yes, if there is a community meeting in the near future, we will let you know in the discussion and on the mailing list. |
Right. |
@tokers |
That's cool. Welcome to submit PR! |
@tokers please assign it to me |
We can create another issue to track the new consul service discovery. |
closing this as completed by #8380 |
Discussed in #8338
Originally posted by Fabriceli November 16, 2022
Version info:
ERROR:
with
/usr/local/apisix/conf/config.yaml
:service A is only valid in Consul y.y.y.y:8600. APISIX is not support multi Consul DNS?
The text was updated successfully, but these errors were encountered: