Skip to content
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

Research and possibly remove recursion logic from external resolver (forwarder) #301

Closed
tsenart opened this issue Oct 6, 2015 · 3 comments

Comments

@tsenart
Copy link
Contributor

tsenart commented Oct 6, 2015

Talking to @discordianfish brought some light to the weird practice that we're undertaking here. Usually a DNS server won't be both a forwarder and a unorthodox recurser. I'll have to do some code archeology to understand the rationale behind this.

@tsenart
Copy link
Contributor Author

tsenart commented Oct 6, 2015

Read this: https://tools.ietf.org/html/rfc5625

@tsenart
Copy link
Contributor Author

tsenart commented Oct 6, 2015

It turns out that this logic came from the first commit in the repo, so no real explanation.

@discordianfish
Copy link
Contributor

To sum up what I said: mesos-dns should be an authoritative nameserver for .mesos and it should simply forward queries for all other zones to a recursive resolving nameserver (aka something like 8.8.8.8 or everything that end up in resolv.conf). It shouldn't do any other logic beside forwarding, similar to the bind option 'forwarders'. This is also what tools like consul are doing.

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

No branches or pull requests

2 participants