I have unbound running and clients using dig seem not to be able to trace?
dig +trace www.amiga.com
; DiG 9.6.2-P2 +trace www.amiga.com
;; global options: +cmd
;; Received 12 bytes from MY-UNBOUND-IP#53(MY-UNBOUND-IP) in 0 ms
However if I hit Google's lookup servers with the same command
# control which clients are allowed to make (recursive) queries
# to this server. Specify classless netblocks with /size and action.
# By default everything is refused, except for localhost.
# Choose deny (drop message), refuse (polite error reply),
# allow (recursive ok),
Fongaboo via Unbound-users writes:
I have unbound running and clients using dig seem not to be able to trace?
dig +trace www.amiga.com
; DiG 9.6.2-P2 +trace www.amiga.com
;; global options: +cmd
;; Received 12 bytes from MY-UNBOUND-IP#53(MY-UNBOUND-IP) in 0 ms
On Tue, 28 Jul 2015, Edward Lewis via Unbound-users wrote:
unbound-anchor, by default, pulls DNSSEC trust anchors from data.iana.org.
I am trying to test RFC 5011 capabilities by following these websites:
http://keyroll.systems
and
http://icksk.dnssek.info/fauxroot.html
Goal is to run
Edward Lewis via Unbound-users wrote:
unbound-anchor, by default, pulls DNSSEC trust anchors from data.iana.org.
I am trying to test RFC 5011 capabilities by following these websites:
http://keyroll.systems
and
http://icksk.dnssek.info/fauxroot.html
Goal is to run unbound-anchor as a