I've been trying to figure out how to test this with dig instead, and I think I
found something. If you have a normal /etc/resolv.conf then you see this:
===
$ dig -t soa local.; echo $?
; <<>> DiG 9.11.3-1ubuntu1.1-Ubuntu <<>> -t soa local.
;; global options: +cmd
;; Got answer:
;; WARNING: .lo
Definitely a duplicate. @paelzer was suggesting in bug 1786261 that dig
be used instead, do you guys know if that's a reasonable possibility?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launch
** Also affects: strongswan (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1752411
Title:
bind9-host, avahi-daemon-check
*** This bug is a duplicate of bug 1752411 ***
https://bugs.launchpad.net/bugs/1752411
** This bug has been marked a duplicate of bug 1752411
bind9-host, avahi-daemon-check-dns.sh hang forever causes network
connections to get stuck
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1752411 ***
https://bugs.launchpad.net/bugs/1752411
Yes, this is definitely another symptom (duplicate) of bug 1752411 . The
folks on that bug might be people who will know if dig can be used
instead.
--
You received this bug notification because you are a
@paelzer, it is making an usual call to host and checking the return:
LC_ALL=C host -t soa local. 2>&1
and theoretically this maps to:
LC_ALL=C dig -t soa local. 2>&1
Practically, I don't think this works. I do not have a "local." start
of authority record and when I run these commands I get a 1
@cjwatson, I've been getting my work into the habit of deploying Debian
packages for all organization-wide system configuration files. So, when I
noticed the other day that openssh-client 7.3p1+ now supports include
directives I put together a new package that gives all of our internal users
n
Public bug reported:
It is not currently possible to deploy packages with system-specific SSH
configuration settings without modifying the ssh_config file. Ideally the
default ssh_config file would simply contain:
Include /etc/ssh/ssh_config.d/*
as this would allow packages to deploy such setti
8 matches
Mail list logo