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

Use libc resolver inside of own DNS code #78

Closed
vincentbernat opened this issue Mar 26, 2015 · 2 comments
Closed

Use libc resolver inside of own DNS code #78

vincentbernat opened this issue Mar 26, 2015 · 2 comments

Comments

@vincentbernat
Copy link
Contributor

Hi!

I noticed that mtr is using its own DNS code instead of the libc resolver. This makes some resolution fails. For example, for IP in /etc/hosts, we get no names. The same applies for stuff that should be learned through mDNS.

It seems that some work has already been done, as mentioned in #56. I didn't test the "newdns" branch yet. I open a new issue since #56 is not totally related and is already closed. Is there any reason that this branch cannot be merged yet? How can I help?

@rewolff
Copy link
Collaborator

rewolff commented Mar 26, 2015

Vincent,
I got fed up with the umpty-th bugreport that would have been avoided if we'd used the libc resolver. So I wrote the "newdns" branch to "show" what that would look like.

In the "newdns" branch it now completely replaces the "olddns" system.

Instead of completely wiping the old dns stuff, for the main branch I would like to have "newdns" be the default, but "olddns" should be a configurable option by passing an argument on the "./configure" command.. (It is such a major change, that I'm afraid to leave people without options if the new stuff doesn't work properly for them.)

You can help by:

  • testing newdns
  • helping to merge "newdns" into master in a way that I think is acceptable.

@rewolff
Copy link
Collaborator

rewolff commented Aug 9, 2016

newdns has been merged into master now. Lets hope it gets a bit more testing.

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

No branches or pull requests

2 participants