Since it's working after the configuration change, I'm going to mark
this bug as invalid, as the software is working as intended.
** Changed in: bind9 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
systemd upstream isn't a fan of the ndots approach:
https://github.com/systemd/systemd/issues/4821
** Bug watch added: github.com/systemd/systemd/issues #4821
https://github.com/systemd/systemd/issues/4821
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I've added "options ndots:2" and indeed it works now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771304
Title:
host don't use search domain for service record
To manage notifications about this
I can see that behavior with normal queries. What triggers it is if the
name you are requesting has a subdomain component or not.
host foo <--- searches for foo and foo.
host foo.bar <--- only searches for foo.bar
That is also the behavior in xenial 16.04.
The resolv.conf manpage has this to sa
