The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: unbound (Ubuntu Precise)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
RFC 4033, 4034 and 4035 are on the IETF Standards track. Any recursive
DNS server not supporting 10-yo standards is broken.
If we keep dancing around non-standard compliant devices, the situation
won't ever improve. Go yell at your vendors for sticking their heads
into sand. Or vote with your m
@ondrey: Since when is a dns resolver without dnssec support 'broken'? I
believe that DNSSEC is a good thing: it will improve security and
everybody using it will benefit, even when most people don't understand
what it is or that it is there. But since most home (and business-grade)
DSL routers don
> that impossible, because the /etc/default/unbound file is part of the
package.
That's actually not true - you can create /etc/default/unbound before
installing the package and the package will not overwrite the configfile
by default:
root@lettie:/# touch /etc/default/unbound
root@lettie:/# ls
So unbound since 1.5.7-2 (which is in xenial and on) no longer ships a
/etc/default/unbound by default. It would appear, based upon the change
in that release:
+RESOLVCONF_FORWARDERS
+
+ This variable controlled whether or not the upstream nameservers
+ supplied by resolvconf were co
I agree with the statement in the bug report that the default should be
safer.
However, you can work around the problem in config management by
installing the defaults file before installing the package. In our
Puppet config we have the unbound package require the defaults file:
https://review.op
@Simon: that impossible, because the /etc/default/unbound file is part
of the package. You can only set this after the package is installed,
and DNS resolving is broken at the moment the package is installed
(Unbound is started automatically during post-install).
Anyway, the puppet issue only illu
@Tom, have you tried telling Puppet to set RESOLVCONF_FORWARDERS=false
in /etc/default/unbound ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/988513
Title:
unbound defaults break DNS resolution whe
Lately, we found out that this issue makes it virtually impossible to deploy
unbound using automated tools (specifically: puppet), since this issue requires
you to:
- install unbound (daemon gets started)
- edit config file
- restart unbound
- continue doing other stuff
When the daemon gets star
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unbound (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/988513
Title:
unb
10 matches
Mail list logo
