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 #53(MY-UNBOUND-IP) in 0 ms
>
# 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), *al
On 28/07/15 15:17, Jaap Akkerhuis via Unbound-users wrote:
> > However if I hit Google's lookup servers with the same command from the
> > same client machine, I get the expected response...
>
> The +trace option causes dig not to use the local resolver. From the
> dig manual:
Not quite. If y
Thanks for everyone's responses. An enlightening thread, and I fully
understand now.
FONG
On Tue, 28 Jul 2015, Anand Buddhdev via Unbound-users wrote:
On 28/07/15 15:17, Jaap Akkerhuis via Unbound-users wrote:
> However if I hit Google's lookup servers with the same command from the
>
