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

Context in remote resolution #25

Closed
britram opened this Issue Oct 23, 2017 · 4 comments

Comments

Projects
None yet
3 participants
@britram
Contributor

britram commented Oct 23, 2017

Discussing Post Sockets with Benno Overeinder, we realized that since all context in the DNS is implicit, the interface on which a remote resolution occurs via DNS might influence the results of that resolution. Is there anything that the remote needs to do to compensate for this fact?

@britram britram added the question label Oct 23, 2017

@tfpauly

This comment has been minimized.

Show comment
Hide comment
@tfpauly

tfpauly Oct 23, 2017

Contributor

It's absolutely true that DNS results can only be cached/compared/etc when looking at one interface (or one DNS server access over that interface). That should be handled by the connection establishment process, which will do the resolution and set up the transients per-path, etc.

I'm going to be updating my 'guidelines' draft this week to make it just about racing during connection establishment, and it addresses isolation of resolution results per-interface. Perhaps once that's ready, we can reference or iterate from there.

Contributor

tfpauly commented Oct 23, 2017

It's absolutely true that DNS results can only be cached/compared/etc when looking at one interface (or one DNS server access over that interface). That should be handled by the connection establishment process, which will do the resolution and set up the transients per-path, etc.

I'm going to be updating my 'guidelines' draft this week to make it just about racing during connection establishment, and it addresses isolation of resolution results per-interface. Perhaps once that's ready, we can reference or iterate from there.

@csperkins

This comment has been minimized.

Show comment
Hide comment
@csperkins

csperkins Oct 27, 2017

Contributor

Resolve should take a Local?

Contributor

csperkins commented Oct 27, 2017

Resolve should take a Local?

@britram britram added the discuss label Nov 8, 2017

@tfpauly

This comment has been minimized.

Show comment
Hide comment
@tfpauly

tfpauly Nov 16, 2017

Contributor

The step of resolution must take Remote + Path, where Path includes DNS configuration (servers, search domains, etc, etc)

Contributor

tfpauly commented Nov 16, 2017

The step of resolution must take Remote + Path, where Path includes DNS configuration (servers, search domains, etc, etc)

@csperkins

This comment has been minimized.

Show comment
Hide comment
@csperkins

csperkins Nov 16, 2017

Contributor

See #19 for Remote interface

Contributor

csperkins commented Nov 16, 2017

See #19 for Remote interface

@britram britram closed this Nov 16, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment