Re: SERVFAIL when looking up TXT from particular domain

2019-06-27 Thread Dennis via bind-users
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 also a ridiculous number of DNSKEYs and signatures. I suspect that
>the operators are forgetting to remove old keys at the end of the ZSK key
>roll.  Eventually, if they keep this up, they will exceed the DNS/TCP message 
>size
>limits at which point all lookups will fail.  At the moment almost all lookups
>from DNSSEC aware resolvers are being retried using TCP as the UDP response is
>bigger that almost all EDNS UDP buffers sizes in use.

I have sent this to the operators with a link to this post. 

Thanks,
Dennis



% dig dnskey capgeminioutsourcing.nl +dnssec
;; BADCOOKIE, retrying.
;; Truncated, retrying in TCP mode.

; <<>> DiG 9.15.1+hotspot+add-prefetch+marka <<>> dnskey 
capgeminioutsourcing.nl +dnssec
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32208
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 32, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags: do; udp: 4096
; COOKIE: 2a6e6fd5aa9f72ee316bd1b35d141cead6bdc8ea9ffcc457 (good)
;; QUESTION SECTION:
;capgeminioutsourcing.nl.    IN    DNSKEY

;; ANSWER SECTION:
capgeminioutsourcing.nl. 171829    IN    DNSKEY    257 3 5 
AwEAAdl6guTPSdcNju0yBB1Co9aK6eTZRBHVIS6r8jzaLwdbqz29/8SX 
wUJYpQTZkl6ymhJJoGNCuTetGBBinSw3syJHg+8rKN8zure+q/3l1XdF 
BqRpgV6C2Gwznxx/T28HcQhh14LvPTfV0KTO3UDF+Ajn4VbpxdHAqKdk 
hbL3hhzWPAxEvUtafWn4ciKtuwlPesIO45SMFwgS2q3sh62D3Fqcddsl 
S9se15IbziJxwYjrY+EsMVuEr0TQw6awv3vuiPQv9aYxQ54ofG51eeoO 
YpvcYn6BN0JTtfpCkBIu3mp74IkzJ5w4Tlxh37D5bqZuOKV+IuFsmURa x1AP9xynygM=
capgeminioutsourcing.nl. 171829    IN    DNSKEY    257 3 5 
AwEAAZri/HxDrwsM6/WwdiIvQ6o3ejG/uPr7xvYxWcFipjo2rDHPdTO8 
ogvwsxPa0/nNKzjUzFcfMfdP1dScXUgL6CDajOM8mdcKaOXWyhx4gdCW 
9W8rQLIVBVHnWkNZ9LTlgw6lsMvu/NkBFGNh+Y2KV6o2G0rh28Y5s2gh 
8aqha2OMQ3td6fDKjSKJwngMC1OdowKMPalliaeXZh4EMZXAaynrtzZ0 
rh57pUaiPXk3FssoUBLckWGeUypKEDM/88w+y1/mQiPBLtMS/xEo/ygD 
X1YtQmvT+7hr/FjlqLKHUTL4Ag4UyTbcwTgV5OYS+DUQONER7bWBRPHT ZV1k8y8oJ/s=
capgeminioutsourcing.nl. 171829    IN    DNSKEY    257 3 5 
AwEAAcaIcFtcMdX9gsRSHymm1UhX4FDyzQBN+gSvdZ3zcqJkPVEBeS0l 
VxAtq+CF5nr5lKwL4m+yx8lMFOJxraJWcCQJRYoSiW6cY/Di/AJQ9Fa3 
YwK/443/JfgR785tTwmOGF2ITxIZo68y/Iaa/yxjjO1DlcTO9yycguAm 
vU/nTxMIx/8710waKOWcDEvdg80EEPJiL/XiR3cH9b+O+VaYSRq9EatF 
bRPeIjKEaHqJM1600gCgrlxGCzlI574uUJVYPwrDsjSIFuuOR31ZIrp9 
7mMDYPi0AO+cSDPUGIIapBVlBf2c6Jt0e8lCWj6JJBpsyaMZlYpxpcQq grxEQ0rXcCc=
capgeminioutsourcing.nl. 171829    IN    DNSKEY    256 3 5 
AwEAAdX7RZYcX8dYd2A502dN2GouKK7yLhbNcI7qXk0zl4EycG3HgDz+ 
PgjfLemaPPSOXJ2SfPG1huZuQ3VCTrZoew5UjSdnJkZZrjp7tTe+su9/ 
9csHOZMzpmlr4N6v8MxC4ldDWxVXWj5zur+MLzLtahChPQpftceA+HkY 4lQp5TN9
capgeminioutsourcing.nl. 171829    IN    DNSKEY    256 3 5 
AwEAAZ8RTy1CgiIk7VgjkqfNQJnEzqc1xN8SxZgm/f+V3zRvU+ScB76q 
BuSsaRhlvDbmctJ4x1QaPa/3Xo5ws7Gt80zw8LQtjh//d5gCF8BImzmq 
JLAlZ5osad7HS6/d+oDKh/kOB92h1dPjh0QOATdC4a4z3DVo6v7eodwb Lg4eaevN
capgeminioutsourcing.nl. 171829    IN    DNSKEY    256 3 5 
AwEAAdoG2gQ/uE4m+1Kk2A1Rae4d3Fyz75ru2qmfVDNc7MYOPIwsMuJo 
GxJ+cCEuI5jNyiOgLZmDX87Deuj5bW1pUleNzbZegUB77C4ho+r2JAM1 
7SM8jMemQAMHR7OWfgmJvxTGlD0OLObgMtHj1zkaIleqBIUxQVYIC/Bp lAVPSCzt
capgeminioutsourcing.nl. 171829    IN    DNSKEY    256 3 5 
AwEAAb7deXB4jJ8LP9SyoDIQgMIb06QHeCV7wODVLMvQIBKYIoyE0Z2M 
CkFp/aPDGgwQY65ZQm9g9SgHT+KBHVsguGfY6JxVus3lUXewJHtwqz9S 
bZRfu/P13mW4s/3BAdA4a+5QktNTvUapp9ROc2L/56bEhGDSAloGFo4P B8Wd92rx
capgeminioutsourcing.nl. 171829    IN    DNSKEY    256 3 5 
AwEAAdQTk0UbPeC366qpj0/KhyH0xnJ0o8BLuggBw0tvtcbh/Dm62fpy 
tlu8jzhQ1BxElYbt0jT4zceur+qObH1gJt6b+hnxyY2yJ+MjTI0p9bUM 
UMp+n66mT3Kqj3KBOUBgXPSU2sSRHpSXgmcQcNvNy7/FWwMtD0aErX1M FfKGMAKN
capgeminioutsourcing.nl. 171829    IN    DNSKEY    256 3 5 
AwEAAb/ahg1GVqXy97t5W+RI16XCu8/Jf1QfhE/oe2EQV6C2VOsrmcSK 
Fp6COdVcCIaYv3gNQs59lG737JnbopiJik4YlcxBgFZ61wkzuM87a3ab 
6ta1QVXxPixqMdP9hUiSNcr7f27eeW57kgjwmfFAwLhvx3lUtFNwlqCs KUA2xcaX
capgeminioutsourcing.nl. 171829    IN    DNSKEY    256 3 5 
AwEAAbxHYQ92nWwB48WdeuL12RtyHUi5/g6Ukn/Gvegp5gxF+XjkOdHs 
pBykxKf+PgNzenEJJNppdAOPlwGVgDNzvX63NjLF/3juVKLD2KzTxBm9 
4JJeaE0FnGmTyhAfklVK0GkseomuSkBdnWEyLwZm5FKZLAdARuwci8dM 4ir78gPF
capgeminioutsourcing.nl. 171829    IN    DNSKEY    256 3 5 
AwEAAdzVD6HLAePyWKbnLZaaQO3xI4KPJGbjmuw62GiU7YiPpE+bWI68 
nrAbW6iWQvxQJIDSY0akLRV12U3rhJfsWVdG1Qmt/XA5tKet7VaUyFmL 
woLE0a9jkyG8T7S3go5oa9wvDtAfvDNS0KJstPZGAtYRYKv5E5l+9oNI w19ObRZZ
capgeminioutsourcing.nl. 171829    IN    DNSKEY    256 3 5 
AwEAAZ5M8n3CSSK4zlwy7RJGbmeSDdIqrRV086TWjLw8hvf8mX2mBEiy 
P6K5qvLrAmAgffzu1PboiRo+QjZDXL4qruV1Sf/8jPFaGEkrjosgRtZn 
APG/ivSux07e/34BJa8BBKbjIt64KOJnzlh27WSghHzwhto+8KW2EAf2 E6qDiY6J
capgeminioutsourcing.nl. 171829    IN    DNSKEY    256 3 5 
AwEAAe9cpo9TeXC1XNsLmqStFRVK8tg3kJJQW3AQpY8RbQNsbPviMtgF 

Re: SERVFAIL when looking up TXT from particular domain

2019-06-26 Thread Mark Andrews
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 operators are forgetting to remove old keys at the end of the ZSK key
roll.  Eventually, if they keep this up, they will exceed the DNS/TCP message 
size
limits at which point all lookups will fail.  At the moment almost all lookups
from DNSSEC aware resolvers are being retried using TCP as the UDP response is
bigger that almost all EDNS UDP buffers sizes in use.

Mark

% dig dnskey capgeminioutsourcing.nl +dnssec
;; BADCOOKIE, retrying.
;; Truncated, retrying in TCP mode.

; <<>> DiG 9.15.1+hotspot+add-prefetch+marka <<>> dnskey 
capgeminioutsourcing.nl +dnssec
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32208
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 32, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags: do; udp: 4096
; COOKIE: 2a6e6fd5aa9f72ee316bd1b35d141cead6bdc8ea9ffcc457 (good)
;; QUESTION SECTION:
;capgeminioutsourcing.nl.   IN  DNSKEY

;; ANSWER SECTION:
capgeminioutsourcing.nl. 171829 IN  DNSKEY  257 3 5 
AwEAAdl6guTPSdcNju0yBB1Co9aK6eTZRBHVIS6r8jzaLwdbqz29/8SX 
wUJYpQTZkl6ymhJJoGNCuTetGBBinSw3syJHg+8rKN8zure+q/3l1XdF 
BqRpgV6C2Gwznxx/T28HcQhh14LvPTfV0KTO3UDF+Ajn4VbpxdHAqKdk 
hbL3hhzWPAxEvUtafWn4ciKtuwlPesIO45SMFwgS2q3sh62D3Fqcddsl 
S9se15IbziJxwYjrY+EsMVuEr0TQw6awv3vuiPQv9aYxQ54ofG51eeoO 
YpvcYn6BN0JTtfpCkBIu3mp74IkzJ5w4Tlxh37D5bqZuOKV+IuFsmURa x1AP9xynygM=
capgeminioutsourcing.nl. 171829 IN  DNSKEY  257 3 5 
AwEAAZri/HxDrwsM6/WwdiIvQ6o3ejG/uPr7xvYxWcFipjo2rDHPdTO8 
ogvwsxPa0/nNKzjUzFcfMfdP1dScXUgL6CDajOM8mdcKaOXWyhx4gdCW 
9W8rQLIVBVHnWkNZ9LTlgw6lsMvu/NkBFGNh+Y2KV6o2G0rh28Y5s2gh 
8aqha2OMQ3td6fDKjSKJwngMC1OdowKMPalliaeXZh4EMZXAaynrtzZ0 
rh57pUaiPXk3FssoUBLckWGeUypKEDM/88w+y1/mQiPBLtMS/xEo/ygD 
X1YtQmvT+7hr/FjlqLKHUTL4Ag4UyTbcwTgV5OYS+DUQONER7bWBRPHT ZV1k8y8oJ/s=
capgeminioutsourcing.nl. 171829 IN  DNSKEY  257 3 5 
AwEAAcaIcFtcMdX9gsRSHymm1UhX4FDyzQBN+gSvdZ3zcqJkPVEBeS0l 
VxAtq+CF5nr5lKwL4m+yx8lMFOJxraJWcCQJRYoSiW6cY/Di/AJQ9Fa3 
YwK/443/JfgR785tTwmOGF2ITxIZo68y/Iaa/yxjjO1DlcTO9yycguAm 
vU/nTxMIx/8710waKOWcDEvdg80EEPJiL/XiR3cH9b+O+VaYSRq9EatF 
bRPeIjKEaHqJM1600gCgrlxGCzlI574uUJVYPwrDsjSIFuuOR31ZIrp9 
7mMDYPi0AO+cSDPUGIIapBVlBf2c6Jt0e8lCWj6JJBpsyaMZlYpxpcQq grxEQ0rXcCc=
capgeminioutsourcing.nl. 171829 IN  DNSKEY  256 3 5 
AwEAAdX7RZYcX8dYd2A502dN2GouKK7yLhbNcI7qXk0zl4EycG3HgDz+ 
PgjfLemaPPSOXJ2SfPG1huZuQ3VCTrZoew5UjSdnJkZZrjp7tTe+su9/ 
9csHOZMzpmlr4N6v8MxC4ldDWxVXWj5zur+MLzLtahChPQpftceA+HkY 4lQp5TN9
capgeminioutsourcing.nl. 171829 IN  DNSKEY  256 3 5 
AwEAAZ8RTy1CgiIk7VgjkqfNQJnEzqc1xN8SxZgm/f+V3zRvU+ScB76q 
BuSsaRhlvDbmctJ4x1QaPa/3Xo5ws7Gt80zw8LQtjh//d5gCF8BImzmq 
JLAlZ5osad7HS6/d+oDKh/kOB92h1dPjh0QOATdC4a4z3DVo6v7eodwb Lg4eaevN
capgeminioutsourcing.nl. 171829 IN  DNSKEY  256 3 5 
AwEAAdoG2gQ/uE4m+1Kk2A1Rae4d3Fyz75ru2qmfVDNc7MYOPIwsMuJo 
GxJ+cCEuI5jNyiOgLZmDX87Deuj5bW1pUleNzbZegUB77C4ho+r2JAM1 
7SM8jMemQAMHR7OWfgmJvxTGlD0OLObgMtHj1zkaIleqBIUxQVYIC/Bp lAVPSCzt
capgeminioutsourcing.nl. 171829 IN  DNSKEY  256 3 5 
AwEAAb7deXB4jJ8LP9SyoDIQgMIb06QHeCV7wODVLMvQIBKYIoyE0Z2M 
CkFp/aPDGgwQY65ZQm9g9SgHT+KBHVsguGfY6JxVus3lUXewJHtwqz9S 
bZRfu/P13mW4s/3BAdA4a+5QktNTvUapp9ROc2L/56bEhGDSAloGFo4P B8Wd92rx
capgeminioutsourcing.nl. 171829 IN  DNSKEY  256 3 5 
AwEAAdQTk0UbPeC366qpj0/KhyH0xnJ0o8BLuggBw0tvtcbh/Dm62fpy 
tlu8jzhQ1BxElYbt0jT4zceur+qObH1gJt6b+hnxyY2yJ+MjTI0p9bUM 
UMp+n66mT3Kqj3KBOUBgXPSU2sSRHpSXgmcQcNvNy7/FWwMtD0aErX1M FfKGMAKN
capgeminioutsourcing.nl. 171829 IN  DNSKEY  256 3 5 
AwEAAb/ahg1GVqXy97t5W+RI16XCu8/Jf1QfhE/oe2EQV6C2VOsrmcSK 
Fp6COdVcCIaYv3gNQs59lG737JnbopiJik4YlcxBgFZ61wkzuM87a3ab 
6ta1QVXxPixqMdP9hUiSNcr7f27eeW57kgjwmfFAwLhvx3lUtFNwlqCs KUA2xcaX
capgeminioutsourcing.nl. 171829 IN  DNSKEY  256 3 5 
AwEAAbxHYQ92nWwB48WdeuL12RtyHUi5/g6Ukn/Gvegp5gxF+XjkOdHs 
pBykxKf+PgNzenEJJNppdAOPlwGVgDNzvX63NjLF/3juVKLD2KzTxBm9 
4JJeaE0FnGmTyhAfklVK0GkseomuSkBdnWEyLwZm5FKZLAdARuwci8dM 4ir78gPF
capgeminioutsourcing.nl. 171829 IN  DNSKEY  256 3 5 
AwEAAdzVD6HLAePyWKbnLZaaQO3xI4KPJGbjmuw62GiU7YiPpE+bWI68 
nrAbW6iWQvxQJIDSY0akLRV12U3rhJfsWVdG1Qmt/XA5tKet7VaUyFmL 
woLE0a9jkyG8T7S3go5oa9wvDtAfvDNS0KJstPZGAtYRYKv5E5l+9oNI w19ObRZZ
capgeminioutsourcing.nl. 171829 IN  DNSKEY  256 3 5 
AwEAAZ5M8n3CSSK4zlwy7RJGbmeSDdIqrRV086TWjLw8hvf8mX2mBEiy 
P6K5qvLrAmAgffzu1PboiRo+QjZDXL4qruV1Sf/8jPFaGEkrjosgRtZn 
APG/ivSux07e/34BJa8BBKbjIt64KOJnzlh27WSghHzwhto+8KW2EAf2 E6qDiY6J
capgeminioutsourcing.nl. 171829 IN  DNSKEY  256 3 5 
AwEAAe9cpo9TeXC1XNsLmqStFRVK8tg3kJJQW3AQpY8RbQNsbPviMtgF 
6kWewilV8D++XQ7eMqpQrYCjw7yLT4oMSHNVs6Nks+1wa9+Yf9n3qw8s 
v/PzqJbQW72e97aZ9/WPMNnMjq668jnCqkyIsOt57tz7NInGF4gOuRLM MZeQnCEJ
capgeminioutsourcing.nl. 171829 IN  DNSKEY  256 3 5 

RE: SERVFAIL when looking up TXT from particular domain

2019-06-26 Thread Browne, Stuart via bind-users
Trying with +cd, +noedns and +tcp elicits a similar result; a SERVFAIL.

As these work fine if querying the authoritative servers directly (or using 
+trace), it appears to be a quirk in the resolver code.

Stuart

> -Original Message-
> From: bind-users [mailto:bind-users-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-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.capgeminioutsourcing.nl +dnssec
> @ns1.capgeminioutsourcing.nl.
> ;; MSG SIZE  rcvd: 4931
> 
> 
> Check your ability to receive fragmented ip packets.
> 
> 
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.14 (GNU/Linux)
> 
> iEYEAREKAAYFAl0UGRIACgkQL6j7milTFsFh1gCfcny3HFKDxUH8p9bxF6vVeSZm
> 0rIAn3rUK0pCmDeQeStpakHQaldlvoN8
> =cOJV
> -END PGP SIGNATURE-
> 
> 
> ___
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to
> unsubscribe from this list
> 
> bind-users mailing list
> bind-users@lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


Re: SERVFAIL when looking up TXT from particular domain

2019-06-26 Thread Carl Byington via bind-users
-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.capgeminioutsourcing.nl +dnssec
@ns1.capgeminioutsourcing.nl.
;; MSG SIZE  rcvd: 4931


Check your ability to receive fragmented ip packets.


-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (GNU/Linux)

iEYEAREKAAYFAl0UGRIACgkQL6j7milTFsFh1gCfcny3HFKDxUH8p9bxF6vVeSZm
0rIAn3rUK0pCmDeQeStpakHQaldlvoN8
=cOJV
-END PGP SIGNATURE-


___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


Re: SERVFAIL when looking up TXT from particular domain

2019-06-26 Thread Kevin Darcy
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 enough with the current BIND code to confirm/deny it.

   - Kevin




On Wed, Jun 26, 2019 at 9:19 AM Dennis via bind-users <
bind-users@lists.isc.org> wrote:

> 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 options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 3652
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
>
> ;; OPT PSEUDOSECTION:
> ; EDNS: version: 0, flags:; udp: 1024
> ;; QUESTION SECTION:
> ;cleanmail4.capgeminioutsourcing.nl. INTXT
>
> ;; Query time: 176 msec
> ;; SERVER: ::1#53(::1)
> ;; WHEN: Wed Jun 26 07:57:59 CDT 2019
> ;; MSG SIZE  rcvd: 63
>
> named -v
> BIND 9.10.3-P4-Debian 
>
> This shows up in the log:
>
> fetch completed at ../../../lib/dns/resolver.c:5082 for
> cleanmail4.capgeminioutsourcing.nl/TXT in 0.176478: ran out of
> space/success [domain:capgeminioutsourcing.nl
> ,referral:2,restart:1,qrysent:2,timeout:0,lame:0,neterr:0,badresp:0,adberr:0,findfail:0,valfail:0]
>
>
> BIND is running in a debian 9 VM in default config. I spun up that vm
> after we discovered a BIND machine elsewhere with the same problem.
>
> Google gives an answer:
>
> ; <<>> DiG 9.10.3-P4-Debian <<>> TXT cleanmail4.capgeminioutsourcing.nl @
> 8.8.8.8
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58950
> ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
>
> ;; OPT PSEUDOSECTION:
> ; EDNS: version: 0, flags:; udp: 512
> ;; QUESTION SECTION:
> ;cleanmail4.capgeminioutsourcing.nl. INTXT
>
> ;; AUTHORITY SECTION:
> capgeminioutsourcing.nl. 899INSOAns1.capgeminioutsourcing.nl.
> dns\.bnl.capgemini.com. 189324 28800 2880 2419200 900
>
> ;; Query time: 45 msec
> ;; SERVER: 8.8.8.8#53(8.8.8.8)
> ;; WHEN: Wed Jun 26 08:04:51 CDT 2019
> ;; MSG SIZE  rcvd: 124
>
> There is no record but Google does not fail. I've checked the SOA and can
> resolve the NS records. I'm overlooking something, but what?
>
>
>
> Cheers,
>
> Dennis
>
>
> ___
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to
> unsubscribe from this list
>
> bind-users mailing list
> bind-users@lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
>
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users