[GH-ISSUE #436] Have server get answers from upstream DNS server? #487

New issue

Closed

opened 2026-03-15 22:45:49 +03:00 by kerem · 3 comments

kerem commented

2026-03-15 22:45:49 +03:00

Owner

Originally created by @phpdave11 on GitHub (Apr 28, 2018).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/436

I am trying to switch my BIND9 setup to trust-dns server. I have everything working with my local domains, but when I try to resolve a public domain, I get no answers.

On the server that is running trust-dns server, I have upstream DNS servers defined in /etc/resolv.conf:

nameserver 208.67.222.222
nameserver 208.67.220.220

Here's what I get when I try to query trust-dns for a public domain:

$ dig @10.42.0.25 github.com

; <<>> DiG 9.12.1 <<>> @10.42.0.25 github.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 5828
;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags: do; udp: 4096
; OPT=6: 08 0d 0e 0f ("....")
; OPT=5: 08 0d 0e 0f ("....")
;; QUESTION SECTION:
;github.com.                    IN      A

;; Query time: 0 msec
;; SERVER: 10.42.0.25#53(10.42.0.25)
;; WHEN: Sat Apr 28 10:58:00 CDT 2018
;; MSG SIZE  rcvd: 55

I started with the example named configuration files. Am I missing some configuration, or is this not supported?

Thanks!

Originally created by @phpdave11 on GitHub (Apr 28, 2018). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/436 I am trying to switch my BIND9 setup to trust-dns server. I have everything working with my local domains, but when I try to resolve a public domain, I get no answers. On the server that is running trust-dns server, I have upstream DNS servers defined in `/etc/resolv.conf`: ``` nameserver 208.67.222.222 nameserver 208.67.220.220 ``` Here's what I get when I try to query trust-dns for a public domain: ``` $ dig @10.42.0.25 github.com ; <<>> DiG 9.12.1 <<>> @10.42.0.25 github.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 5828 ;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags: do; udp: 4096 ; OPT=6: 08 0d 0e 0f ("....") ; OPT=5: 08 0d 0e 0f ("....") ;; QUESTION SECTION: ;github.com. IN A ;; Query time: 0 msec ;; SERVER: 10.42.0.25#53(10.42.0.25) ;; WHEN: Sat Apr 28 10:58:00 CDT 2018 ;; MSG SIZE rcvd: 55 ``` I started with the example named configuration files. Am I missing some configuration, or is this not supported? Thanks!

kerem

2026-03-15 22:45:49 +03:00

closed this issue
added the
enhance

crate:server
labels

kerem commented

2026-03-15 22:46:05 +03:00

Author

Owner

@bluejekyll commented on GitHub (Apr 28, 2018):

You are missing something, and it's a very important feature we still need to build! Please see #55

Forwarding support is not yet complete. With the Resolver (limited to stub resolution at-the-moment) work in a pretty decent state at this point, I do see us in a position now to integrate the Resolver into the server for forwarding support. Right now, the trust-dns server is only capably of acting as an authority.

I'm gearing up to work on the resolver integration soon, but I don't anticipate that work being complete for a while. It's going to require some refactoring of the Resolver and the Server before such a thing will be ready.

I hope this wasn't wasted effort for you!

@bluejekyll commented on GitHub (Apr 28, 2018): You are missing something, and it's a very important feature we still need to build! Please see #55 Forwarding support is not yet complete. With the Resolver (limited to stub resolution at-the-moment) work in a pretty decent state at this point, I do see us in a position now to integrate the Resolver into the server for forwarding support. Right now, the trust-dns server is only capably of acting as an authority. I'm gearing up to work on the resolver integration soon, but I don't anticipate that work being complete for a while. It's going to require some refactoring of the Resolver and the Server before such a thing will be ready. I hope this wasn't wasted effort for you!

kerem commented

2026-03-15 22:46:10 +03:00

Author

Owner

@phpdave11 commented on GitHub (Apr 28, 2018):

No problem, thanks for the explanation -- can't wait for forwarding support!

Nice job on this whole project by the way! It was definitely not wasted effort on my part, as I too am trying to learn rust and get more familiar with programs written in rust.

@phpdave11 commented on GitHub (Apr 28, 2018): No problem, thanks for the explanation -- can't wait for forwarding support! Nice job on this whole project by the way! It was definitely not wasted effort on my part, as I too am trying to learn rust and get more familiar with programs written in rust.

kerem commented

2026-03-15 22:46:15 +03:00

Author

Owner

@bluejekyll commented on GitHub (Apr 9, 2019):

fixed in #674

@bluejekyll commented on GitHub (Apr 9, 2019): fixed in #674

kerem referenced this issue

2026-03-15 22:50:20 +03:00

[GH-ISSUE #483] Resolver binary #501

kerem referenced this issue

2026-03-16 02:08:23 +03:00