Hi Mark,
>Given the message says "ran out of space” it indicates that a fixed buffer was
>too small. The lookup also works with current versions of BIND so I would
>say the solution is to stop running EoL’d software and upgrade.
I have upgraded to 9.14.3 and that has solved the issue.
>There is
Given the message says "ran out of space” it indicates that a fixed buffer was
too small. The lookup also works with current versions of BIND so I would
say the solution is to stop running EoL’d software and upgrade.
There is also a ridiculous number of DNSKEYs and signatures. I suspect that
the
s-boun...@lists.isc.org] On Behalf Of
> Carl Byington via bind-users
> Sent: Thursday, 27 June 2019 11:17 AM
> To: bind-users@lists.isc.org
> Subject: Re: SERVFAIL when looking up TXT from particular domain
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On Wed, 2019-06-2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Wed, 2019-06-26 at 13:16 +, Dennis via bind-users wrote:
> dig TXT cleanmail4.capgeminioutsourcing.nl @localhost
dig TXT cleanmail4.capgeminioutsourcing.nl +nodnssec
@ns1.capgeminioutsourcing.nl.
;; MSG SIZE rcvd: 124
dig TXT cleanmail4.c
There's a huge amount of DNSSEC verbiage in the response to that query
(4931-byte response from the authoritative nameservers), when querying
with +dnssec. I'm guessing the resolver function of BIND might be having
trouble with DNSSEC validation. At least, that's a hypothesis. I'm not
familiar enou
Hi List,
When I try to resolve a TXT record cleanmail4.capgeminioutsourcing.nl I'll get
a SERVFAIL. Asking Google seems to work though:
rndc flush
dig TXT cleanmail4.capgeminioutsourcing.nl @localhost
; <<>> DiG 9.10.3-P4-Debian <<>> TXT cleanmail4.capgeminioutsourcing.nl
@localhost
;; global
6 matches
Mail list logo
