Re: SERVFAIL on IPv6 tunnelbroker network

root@server:~# dig aax-eu.amazon-adsystem.com @ns-911.amazon.com +dnssec +norec ; <<>> DiG 9.11.3-2-Debian <<>> aax-eu.amazon-adsystem.com @ ns-911.amazon.com +dnssec +norec ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49254 ;; flags: qr aa;

Re: SERVFAIL on IPv6 tunnelbroker network

So what do you get to this command when run on the recursive server? dig aax-eu.amazon-adsystem.com @ns-911.amazon.com +dnssec +norec -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org _

Re: SERVFAIL on IPv6 tunnelbroker network

Hello! Thank you very much. So what do you mean "internal-enp1s0f3" view is configured to bump this domain? Is this a setting? It looks like this for my views: view "internal-enp1s0f3" { match-clients { "internal-enp1s0f3"; }; match-recursive-only yes; recursion yes; allow-recursio

Re: SERVFAIL on IPv6 tunnelbroker network

Hi Patrik, I don't see any SERVFAIL querying for this record.  maybe your"internal-enp1s0f3" view is configured to bump this domain? Kind Regards Peter dig aax-eu.amazon-adsystem.com ; <<>> DiG 9.10.2-P4 <<>> aax-eu.amazon-adsystem.com ;; global options: +cmd ;; Got answer: ;;

SERVFAIL on IPv6 tunnelbroker network

Hello! How are you? I started having a problem with BIND9. Something must have changed, because I start getting SERVFAIL a lot. Looks like this: 25-Jul-2018 07:44:09.647 client @0x7fa268223c10 192.168.78.30#56577 ( aax-eu.amazon-adsystem.com): view internal-enp1s0f3: query failed (SERVFAIL) for aa