What does list_stubs do?

Unbound
1

I noticed that there is an option named ‘list_stubs’ for unbound-control. Here is the introduction of it on manual pages for unbound-control:

       **list***_***stubs**
              List the stub zones in use.  These are printed one by one to the
              output.  This includes the root hints in use.

What does 'in use' mean? 
What will happen to the result after querying unbound for the exact RR records if I set stub_prime?

e.g.  stub-zone:

        name: "example"
        stub-addr: 10.53.0.1
        stub-prime: yes

RRset on [10.53.0.1](http://10.53.0.1/):
example. IN NS ns1
ns1 IN A 10.53.0.2

Thanks

Cathy
2

Hi Cathy,

I noticed that there is an option named 'list_stubs' for
unbound-control. Here is the introduction of it on manual pages for
unbound-control:

       *list*/_/*stubs*
              List the stub zones in use. These are printed one by one to the
              output. This includes the root hints in use.

What does 'in use' mean?

It prints the information for the stubs from memory, as unbound is using
the stub config. (it is not printing the stuff from cache, use 'lookup'
for that, it prints the servers in cache that have been probed).

What will happen to the result after querying unbound for the exact RR records if I set stub_prime?

The list_stubs command shows you your config. So it shows the initial
servers that it had primed from, but not the result of the prime. The
result of the prime can be seen with queries or 'lookup'.

e.g. stub-zone:

        name: "example"
        stub-addr: 10.53.0.1
        stub-prime: yes

RRset on 10.53.0.1 <http://10.53.0.1/&gt;:
example. IN NS ns1
ns1 IN A 10.53.0.2

list-stubs shows you 10.53.0.1. And the root-hints from the root-hints
file.

And unbound-control lookup example shows 10.53.0.2 (and its ping time).

Best regards,
   Wouter