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
Generally, we configure multiple DNS resolver servers in Stubby and if round robin is unset then stubby tries to use the same address until it encounter any issues. In such scenario where the stubby does not switch to different resolver, do we have any API exposed by Stubby or getDNS to know which IP address are in use?
Thanks
Amit.
The text was updated successfully, but these errors were encountered:
That's not yet available no. I suppose we could make a meta query that would expose that information in stubby, paired with get that information from getdns_context_get_api_information().
Also - depending on your environment/setup you may be able to enable full logging by passing the -l or -v flag to Stubby which will show you the connections Stubby is making:
-l Enable logging of all logs (same as -v 7)
-v Specify logging level (overrides -l option). Values are
0: EMERG - System is unusable
1: ALERT - Action must be taken immediately
2: CRIT - Critical conditions
3: ERROR - Error conditions
4: WARN - Warning conditions
5: NOTICE - Normal, but significant, condition
6: INFO - Informational message
7: DEBUG - Debug-level message
Generally, we configure multiple DNS resolver servers in Stubby and if round robin is unset then stubby tries to use the same address until it encounter any issues. In such scenario where the stubby does not switch to different resolver, do we have any API exposed by Stubby or getDNS to know which IP address are in use?
Thanks
Amit.
The text was updated successfully, but these errors were encountered: