You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do we have a way to update the DNS server addresses for AsyncResolver at runtime ? Ex. for each query, it could use different DNS servers if no record is found in the cache.
My use case is that the resolver service could learn DNS server address from different sources such as DHCP client, NDP and default ones. So the DNS server addresses are updated dynamically.
I did a code search and did not find an obvious way to do that or I miss something?
The text was updated successfully, but these errors were encountered:
No, we currently don't support this. I've wanted to do this, I think it will be needed for things like changing networks etc.
I don't currently have a design for it as I think it's a somewhat complex and possibly OS specific operation. My guess is that we want to have a high-level API that can be called to perform the update, and then each OS can have a wrapper that would update the connections via whatever mechanism it needs to implement...
As a temporary workaround for me, whenever the DNS name server address configuration update, a new AsyncResolver instance will be created. Meanwhile I may look into how to make dynamic configuration of DNS name servers work for trust-dns-resolver.
Ben,
Do we have a way to update the DNS server addresses for AsyncResolver at runtime ? Ex. for each query, it could use different DNS servers if no record is found in the cache.
My use case is that the resolver service could learn DNS server address from different sources such as DHCP client, NDP and default ones. So the DNS server addresses are updated dynamically.
I did a code search and did not find an obvious way to do that or I miss something?
The text was updated successfully, but these errors were encountered: