Bind9 team consider this behavior as normal.
See this issue for more details.
https://gitlab.isc.org/isc-projects/bind9/issues/917
** Bug watch added: gitlab.isc.org/isc-projects/bind9/issues #917
https://gitlab.isc.org/isc-projects/bind9/issues/917
--
You received this bug notification be
I have a the same kind of errors. DNS resolution sometimes fails due to
cache issues.
Is you bug similar to mine
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818527 ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
I have a the same systemd version and DNS resolution sometimes fails due
to cache issues.
Is you bug similar to mine
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818527 ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
** Package changed: systemd (Ubuntu) => bind9 (Ubuntu)
** Description changed:
- I am facing really strange issues with systemd-resolved.
+ I am facing really strange issues with bind9.
Local cache of DNS replies seems to be unreliable.
For example, when a try to get ANY record for gith
** Summary changed:
- Systemd Resolve cache handling issues
+ Bind9 cache handling issues for dig ANY request
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818217
Title:
Bind9 cache handling issu
** Description changed:
I am facing really strange issues with systemd-resolved.
-
Local cache of DNS replies seems to be unreliable.
For example, when a try to get ANY record for github.com, I get A, ,
MX, CAA, TXT and NS records.
- When the TTL of entries expires, the same
Public bug reported:
It seems that when systemd-resolve cache an non-existent CNAME record
for a domain, any attempt to resolve A record for the same domain fail.
systemd version the issue has been seen with
Installed: 237-3ubuntu10.13
Used distribution
Distributor ID: Ubuntu
Description: Ubuntu
Public bug reported:
I am facing really strange issues with systemd-resolved.
Local cache of DNS replies seems to be unreliable.
For example, when a try to get ANY record for github.com, I get A, ,
MX, CAA, TXT and NS records.
When the TTL of entries expires, the same request is this ignor
