Skip to content

setting namespaces in prepare_for_resolution does not work on per query basis #8

Closed

Description

@glenwiley

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:

  1. having two unbound contexts, one that does local names and one that does dns only.
  2. Or lift local name lookup out of unbound and put it in getdns.

I prefer the second. (Willem & Neel)

(#106 from private repo)

Activity

  1. wtoorop commented on Jun 30, 2014

    @wtoorop
    Contributor

    I also prefer second.

    b.t.w. it is the other way around. getdns_address uses namespaces and getdns_general dns only

  2. saradickinson commented on Sep 26, 2014

    @saradickinson
    Contributor

    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.

  3. wtoorop commented on Sep 30, 2014

    @wtoorop
    Contributor

    I believe the asynchronous methods can be addressed similarly.

  4. wtoorop commented on Oct 15, 2014

    @wtoorop
    Contributor

    Since async and sync follow the same code path, this is done and implemented.

  5. added a commit that references this issue on Mar 20, 2017
  6. added a commit that references this issue on Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions