@Eli,
Ah ok, yes, disabling IPv6 probably breaks some default configuration
stuff -- maybe similar to
https://bbs.archlinux.org/viewtopic.php?id=128725. I'm guessing you
could disable ipv6 again and just properly configure tftpd-hpa.
Marking as invalid.
** Changed in: tftp-hpa (Ubuntu)
St
** Changed in: cyrus-sasl2 (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1672941
Title:
FTBFS with older versions of OpenSSL
To manage no
I must be missing something obvious, as well.
When I run `service unbound restart` after specifying a forwarder with
`unbound-control` first, `unbound-control forward` reports 'off (using
root hints)' afterwards. This is in a VM using DHCP for its IP address.
Is there some additional configuration
I uploaded the fix today to 16.04 and 16.10, will need to go through the
SRU process.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1639776
Title:
dnsmasq fails to send queries out af
Also, I note that in 17.04 (unlike 16.04), there is a unbound-
resolvconf.service which has:
[Unit]
Description=Unbound DNS server via resolvconf
After=unbound.service
PartOf=unbound.service
ConditionFileIsExecutable=/sbin/resolvconf
[Service]
RemainAfterExit=yes
ExecStart=/usr/lib/unbound/packag
** Description changed:
+ [Impact]
+
+ * suspend/resume (which involves disconnection of network devices)
+ leads to dnsmasq failures.
+
+ [Test Case]
+
+ * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see failures
+ upon resume.
+
+ [Regression Potential]
+
+ * The fix was NMU
