Thanks. I think I understand the problem you're reporting, and your
expected behaviour seems reasonable to me. Unless there's some special
new expected behaviour I don't know about.
If this affects ping (I haven't verified myself) then I don't think it'd
related to the bind package.
However if bind9-host is providing host then is this two separate bugs?
I don't get exactly the same behaviour you see however. I tried, in a
fresh Cosmic container, making /etc/resolv.conf exactly:
search quantopian.com kamens.us
nameserver 127.0.0.53
and then:
# getent hosts jik5.quantopian.com.
# getent hosts jik5.kamens.us.
146.115.43.199 jik5.kamens.us
# ping jik5
PING jik5.kamens.us (146.115.43.199) 56(84) bytes of data.
...
Are there any other special steps needed to reproduce what you're
seeing, perhaps DNSSEC related on my network?
This does however fail as you describe:
# host jik5
#
So perhaps this is a bind9-only bug after all, but it doesn't explain
how your ping command fails.
** Changed in: bind9 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717014
Title:
host stops searching domains when it gets back NSEC record
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1717014/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
