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
{{ message }}
Repository navigation
setting namespaces in prepare_for_resolution does not work on per query basis #8
getdns_general uses namespaces and getdns_address does not, so one can choose to use namespaces on a per query basis. However, currently namespaces are set in the prepare_for_resolution function, which initializes the "context" for those namespaces.
Solution that comes to mind:
having two unbound contexts, one that does local names and one that does dns only.
Or lift local name lookup out of unbound and put it in getdns.
Commit df02aee in the features/gldns branch modifies the behaviour of the synchronous methods to correctly use the namespaces (vs DNS only) per query. Although note that the namespaces may still only be changed on the context before the first query.
Activity
wtoorop commentedon Jun 30, 2014
I also prefer second.
b.t.w. it is the other way around. getdns_address uses namespaces and getdns_general dns only
saradickinson commentedon Sep 26, 2014
Commit df02aee in the features/gldns branch modifies the behaviour of the synchronous methods to correctly use the namespaces (vs DNS only) per query. Although note that the namespaces may still only be changed on the context before the first query.
wtoorop commentedon Sep 30, 2014
I believe the asynchronous methods can be addressed similarly.
wtoorop commentedon Oct 15, 2014
Since async and sync follow the same code path, this is done and implemented.
Merge pull request getdnsapi#8 from wtoorop/features/mdns-client
Merge pull request getdnsapi#8 from saradickinson/bugfix/fix_logging