Hi Thomas, FWIW: I can resolve peak.ag from 8.8.8.8 just fine now:
❯ ~ dig peak.ag @8.8.8.8 +dnssec ; <<>> DiG 9.10.6 <<>> peak.ag @8.8.8.8 +dnssec ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16486 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags: do; udp: 512 ;; QUESTION SECTION: ;peak.ag. IN A ;; ANSWER SECTION: peak.ag. 3599 IN A 153.92.198.115 ;; Query time: 66 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Fri Nov 27 12:16:32 CET 2020 ;; MSG SIZE rcvd: 52 Frank > On 27 Nov 2020, at 12:09, Thomas Mieslinger <mi...@mail.com> wrote: > > Hi, > > I received customer complaints that quad8 and some german broadband > resolvers were unable to resolve .ag secondlevel domains. > > peak.ag > hoevelmann.ag > sonnenschein.ag > hostedoffice.ag > > I run the authoritatives serving the first three examples and we've had > no outage. > > I don't understand the DNSEC keys in .ag and the intended change carried > out with the current setup. > > https://dnsviz.net/d/hoevelmann.ag/dnssec/ > > Do you also see problems with .ag? > > Cheers > > Thomas > > _______________________________________________ > dns-operations mailing list > dns-operations@lists.dns-oarc.net > https://lists.dns-oarc.net/mailman/listinfo/dns-operations
_______________________________________________ dns-operations mailing list dns-operations@lists.dns-oarc.net https://lists.dns-oarc.net/mailman/listinfo/dns-operations
