Hello Mukund,
On Fri, May 06, 2016 at 07:01:22PM +0530, Mukund Sivaraman wrote:
> These queries are sent by 81.209.177.155 to 192.12.94.30 with UDP
> payload size set to 512. This caused the reply to be truncated:
>
> [muks@jurassic ~]$ dig +bufsize=512 +dnssec @192.12.94.30 -t A
> foaf-search.
Hi Michael
On Fri, May 06, 2016 at 02:57:59PM +0200, Michael Brunnbauer wrote:
> I tried running bind with dnssec-enable no and still the exchanges with
> tld nameservers involved many packets and TCP sessions. Why?
See below:
> > 07:25:08.157974 IP (tos 0x0, ttl 64, id 22351, offset 0, flags [n
hi all,
As I expected, setting the TTL of nameserver related RRs to 86400 instead of
600 drastically reduces the probability for this error (the A-records for which
the error occurs still have TTL 600). This is something I should have done long
before.
IMO, this problem should still be investig
hi all,
On Thu, May 05, 2016 at 09:31:06AM +0200, Michael Brunnbauer wrote:
> after upgrading from bind 9.10.3-P2 to 9.10.4, I have intermittent DNS lookup
> errors on one of my servers with low DNS load. The server is not
> authoritative
> for the affected zones but the authoritative servers a
hi all,
after upgrading from bind 9.10.3-P2 to 9.10.4, I have intermittent DNS lookup
errors on one of my servers with low DNS load. The server is not authoritative
for the affected zones but the authoritative servers are under my control and
show no problems. So far, I have not been able to rep
5 matches
Mail list logo
