resolv.conf #55

New issue

Closed

opened 2026-03-07 22:18:24 +03:00 by kerem · 5 comments

kerem commented

2026-03-07 22:18:24 +03:00

Owner

Originally created by @bbigras on GitHub (Mar 27, 2017).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/109

Is there an helper or something to to a query using the system's dns servers that would also handle if the first one fails.

Right now it seems I need to hardcode the dns server ip.

Originally created by @bbigras on GitHub (Mar 27, 2017). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/109 Is there an helper or something to to a query using the system's dns servers that would also handle if the first one fails. Right now it seems I need to hardcode the dns server ip.

kerem

2026-03-07 22:18:24 +03:00

closed this issue
added the
enhance

ops
labels

kerem commented

2026-03-07 22:18:25 +03:00

Author

Owner

@bluejekyll commented on GitHub (Mar 27, 2017):

By "system" do you mean read /etc/resolv.conf or equivalent?

@bluejekyll commented on GitHub (Mar 27, 2017): By "system" do you mean read /etc/resolv.conf or equivalent?

kerem commented

2026-03-07 22:18:26 +03:00

Author

Owner

@bbigras commented on GitHub (Mar 27, 2017):

Yes.

@bbigras commented on GitHub (Mar 27, 2017): Yes.

kerem commented

2026-03-07 22:18:26 +03:00

Author

Owner

@bluejekyll commented on GitHub (Mar 27, 2017):

This is something I plan to include in the Resolver. I thought I had an issue open for that, but I didn't, so I opened a new one: #110

Basically, the Client is supposed to be a dumb DNS client. I decided this after some concerns around the DNSSec solving logic, which will probably migrate to the Resolver package in time. I plan on starting this work after I finish some work on mTLS.

@bluejekyll commented on GitHub (Mar 27, 2017): This is something I plan to include in the Resolver. I thought I had an issue open for that, but I didn't, so I opened a new one: #110 Basically, the Client is supposed to be a dumb DNS client. I decided this after some concerns around the DNSSec solving logic, which will probably migrate to the Resolver package in time. I plan on starting this work after I finish some work on mTLS.

kerem commented

2026-03-07 22:18:26 +03:00

Author

Owner

@bluejekyll commented on GitHub (Mar 27, 2017):

Depends on #110

@bluejekyll commented on GitHub (Mar 27, 2017): Depends on #110

kerem commented

2026-03-07 22:18:26 +03:00

Author

Owner

@bluejekyll commented on GitHub (May 23, 2017):