.
From: Mark Andrews
Sent: Friday, January 6, 2023 2:57 PM
To: Justin Krejci
Cc: bind-users@lists.isc.org
Subject: Re: DNS Cookies Causing FORMERR
Really there are very few servers that are broken and the numbers are
decreasing. They are well under 1%. Just contact the
DNS Servers that do not properly support or properly ignore DNS cookies and
instead return FORMERR is annoying. This is not new. However I have been seeing
more or perhaps just have more users that are finding more domains that are
hosted on authoritative servers with this unfortunate behavior.
I do not understand why I did not get similar test and log results as
you indicate below but I appreciate your feedback!
Thank you!!
On Thu, 2011-04-14 at 17:39 +0100, Tony Finch wrote:
> Justin Krejci wrote:
> >
> > So I am wondering if this is normal/expected behavior for
er.domain.com." instead BIND serves the records as expected.
So I am wondering if this is normal/expected behavior for BIND and if so
should debug logging or named-checkzone with debugging be able to
identify this as the problem. Or am I missing something else altogether?
Thank
On Wed,
Hello List,
When troubleshooting a particular reverse delegated zone to us we used
the normal "d/26.c.b.a.in-addr.arpa" naming for the zone. A couple of
zones did not get served correctly (tried on BIND 9.7.0-P2 and 9.7.3)
and any query for a record within these zones always came back with a
SERVF
you own supernet.com, this problem is not your fault and not for you
> to fix. You can work around it with conditional forwarding, or a zone of type
> static-stub if you're using BIND 9.8 already, but that's strictly a
> workaround and subject to breakage if the zone is moved.
SERVFAIL response comes back in <2 ms according to dig.
On Thu, 2011-03-03 at 16:29 -0600, Justin Krejci wrote:
> When doing a recursive query for MX supernet.com against a caching BIND
> server, the BIND server responds back with the answer. The TTL is 300.
>
> After the TTL expire
When doing a recursive query for MX supernet.com against a caching BIND
server, the BIND server responds back with the answer. The TTL is 300.
After the TTL expires the following recursive query for the same record
returns a SERVFAIL from the caching server.
If I do a +trace on the same query to
8 matches
Mail list logo
