Use hostname or fqdn file unbound.conf

Unbound
1

Hi Guys,

Umbound not start when using hostname or fqdn unbound.conf file (interface).
How to tell the developer to include this option in next version?

Thank you.

lamoura.

2

I am not sure I understand what you are asking for?

Which option in unbound.conf do you want to use a hostname or fqdn for?

And if the unbound server is using 127.0.0.1 to resolve, do you have a
/etc/hosts entry for when unbound is not running yet?

Paul

3

Quoting Paul Wouters (paul@nohats.ca):

>Umbound not start when using hostname or fqdn unbound.conf file (interface).
>How to tell the developer to include this option in next version?

I am not sure I understand what you are asking for?
Which option in unbound.conf do you want to use a hostname or fqdn for?

I think he means the 'interface' option.
Like so:

    interface: my.fqdn.example.tld

instead of:

    interface: 2007:db8::1

I highly doubt that'll work and don't think it is what one should want.

Regards,
-Sndr.

4

[ Quoting <ssmeenk@freshdot.net> in "Re: [Unbound-users] Use hostname or..." ]

I think he means the 'interface' option.
Like so:

    interface: my.fqdn.example.tld

instead of:

    interface: 2007:db8::1

I highly doubt that'll work and don't think it is what one should want.

Interesting, using a fqdn in a startup file for a resolver.

grtz Miek

5

Yes, it is the 'interface'.

My / etc / hosts is configured as follows:

127.0.0.1 localhost localhost.srv
xxx.xxx.xxx.xx external externo.srv

6

Quoting Miek Gieben (miek@miek.nl):

> interface: my.fqdn.example.tld
> instead of:
> interface: 2007:db8::1
> I highly doubt that'll work and don't think it is what one should want.
Interesting, using a fqdn in a startup file for a resolver.

Yes. Well, it *could* work if you put that entry in /etc/hosts, but then
what is the difference to putting IPs in your unbound.conf :wink:

Again, not what one should want.

-Sndr.

7

My / etc / hosts is configured as follows:
xxx.xxx.xxx.xx external externo.srv

I need to configure in unbound.conf

interface: external

Even if it worked, which it oughtn't to IMO, what's the difference
between adding an /etc/hosts entry and directly configuring Unbound to
use the IP address? Just configure

        interface: xxx.xxx.xxx.xx

and you'll be right.

        -JP

8

You could distribute a packaged unbound with pre-configuration, and
you only have to distribute /etc/hosts uniquely using something like
puppet. So I can see why it would be nice to have.

However, roughly the same can be accomplished using:

   interface: 0.0.0.0
   interface: ::0
   interface-automatic: yes

Paul

9

Paul,

You could distribute a packaged unbound with pre-configuration, and
you only have to distribute /etc/hosts uniquely using something like
puppet. So I can see why it would be nice to have.

Nice idea, indeed.

Then of course, somebody starts messing with /etc/hosts and/or
/etc/nsswitch.conf whereupon Unbound no longer does what it should. :slight_smile:

        -JP

10

I did not ...

I use puppet to publish the configuration and have 60 servers dns.

is simple!

I would like to use the conf unbound as follows:

interface: External (outside is a configuration of / etc / hosts)

I tested does not work.

I wonder how will I tell the developers to add this feature if there
is a possibility. Other applications allow this configuration.

This configuration will not change the way you use the conf would be
just another option.

I'm not worried that someone will change the hosts, the puppet takes
care of that. We have the organization and standardization on our
servers. :slight_smile:

11

I use puppet to publish the configuration and have 60 servers dns.

Considering you use Puppet for configuration management, it should be
trivial to use it to create/modify your `unbound.conf' to set
corresponding interface addresses. (FWIW, I'd suggest Puppet's Hiera
from which you obtain external data, or ENC.)

I wonder how will I tell the developers to add this feature if there
is a possibility.

The Unbound development team read this list, so don't worry: if they
think it's a good idea, they'll chip in. :slight_smile:

Other applications allow this configuration.

Other applications: yes; most DNS servers: no.

        -JP

12

optimum

Thanks for the information.

13

Also,

Consider using the include: directive:

Files can be included using the include: directive. It can appear any-
       where, and takes a single filename as an argument. Processing
contin-
       ues as if the text from the included file was copied into the
config
       file at that point.

/S

From: unbound-users-bounces@unbound.net [mailto:unbound-users-
bounces@unbound.net] On Behalf Of Leandro Anjos Moura
Sent: Monday, July 02, 2012 2:31 PM
To: Unbound-users@unbound.net
Subject: Re: [Unbound-users] Use hostname or fqdn file unbound.conf

optimum

Thanks for the information.

>> I use puppet to publish the configuration and have 60 servers dns.
>
> Considering you use Puppet for configuration management, it should

be

> trivial to use it to create/modify your `unbound.conf' to set
> corresponding interface addresses. (FWIW, I'd suggest Puppet's Hiera
> from which you obtain external data, or ENC.)
>
>> I wonder how will I tell the developers to add this feature if

there