Things were going great for the .ie 8 -> 13 rollover, but
now the algorithm 8 KSK appears to be gone prior to the
removal of the algorithm 8 DS...
Most resolvers will let this slide, but there could be some
spots of trouble...
--
Viktor.
Hi everyone,
I thought it polite to also mention it here, especially since my parting
post comes with some thoughts on DNS: I am leaving DNS and PowerDNS.
Although I do grumble a bit in the post, it has been an honour for me to be
part of the DNS community. I leave the scene a lot wiser about
> That is fine if you do not want DNSSEC.
>
> > Do you also see problems with .ag?
>
Yesterday morning I noticed it was bogus but that is fixed by now.
jaap
___
dns-operations mailing list
dns-operations@lists.dns-oarc.net
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,
--- Begin Message ---
> On 20201127, at 13:40, Matthew Richardson wrote:
>
> DNSvis has recorded two entries for hoevelmann.ag. Whilst the latest one
> looks OK, the previous one:-
>
> https://dnsviz.net/d/hoevelmann.ag/X8DXeQ/dnssec/
>
> is showing an amount of
On Fri, Nov 27, 2020 at 12:09:08PM +0100,
Thomas Mieslinger wrote
a message of 28 lines which said:
> I received customer complaints that quad8 and some german broadband
> resolvers were unable to resolve .ag secondlevel domains.
It works for me:
% dig @8.8.8.8 peak.ag
; <<>> DiG
DNSvis has recorded two entries for hoevelmann.ag. Whilst the latest one
looks OK, the previous one:-
https://dnsviz.net/d/hoevelmann.ag/X8DXeQ/dnssec/
is showing an amount of bogusness.
This previous one may be a clue...
Best wishes,
Matthew
--
>From: Thomas Mieslinger
>To:
--- Begin Message ---
> On 20201127, at 12:09, Thomas Mieslinger wrote:
>
> Hi,
>
> I received customer complaints that quad8 and some german broadband
> resolvers were unable to resolve .ag secondlevel domains.
Any outputs from 'dig' that show the problem?
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
