Hi Patrik,
I don't see any SERVFAIL querying for this AAAA record. maybe your "internal-enp1s0f3" view is configured to bump this domain?
Kind Regards Peter
dig aax-eu.amazon-adsystem.com
aaaa
; <<>> DiG 9.10.2-P4 <<>>
aax-eu.amazon-adsystem.com aaaa
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id:
32650
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1,
ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;aax-eu.amazon-adsystem.com. IN AAAA
;; AUTHORITY SECTION:
aax-eu.amazon-adsystem.com. 60 IN SOA
ns-924.amazon.com. root.amazon.com. 1532498091 3600 900 7776000
60
;; Query time: 67 msec
;; SERVER: 205.166.94.20#53(205.166.94.20)
;; WHEN: Wed Jul 25 05:59:58 UTC 2018
;; MSG SIZE rcvd: 110
_______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-...@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Hi Patrik,
192.168.81.20 appears to be
matched to the internal-enp1s0f3 view.
This view might not be able to resolve these external dns
entries correctly
what do you get when you try
dig @192.168.81.20 com soa
and
dig @192.168.81.20 production.cloudflare.docker.com
+trace
Kind Regards Peter