-
Cchadwicka
hi
-
unit86
I'm not sure where the problem is here, if this is a network issue or db corruption.
-
unit86
2026-10-12 07:07:02.106 W Invalid DNSSEC A record signature for seeds.moneroseeds.se: validation failure <seeds.moneroseeds.se. A IN>: key for validation . is marked as invalid because of a previous signature for expected key and algorithm missing
-
unit86
2026-10-12 07:07:02.109 W Invalid DNSSEC A record signature for seeds.moneroseeds.ae.org: validation failure <seeds.moneroseeds.ae.org. A IN>: key for validation . is marked as invalid because of a previous signature for expected key and algorithm missing
-
unit86
2026-10-12 07:07:02.149 W Invalid DNSSEC TXT record signature for updates.moneropulse.fr: validation failure <updates.moneropulse.fr. TXT IN>: key for validation . is marked as invalid because of a previous signature for expected key and algorithm missing
-
unit86
2026-10-12 07:07:02.546 W Invalid DNSSEC TXT record signature for updates.moneropulse.net: validation failure <updates.moneropulse.net. TXT IN>: key for validation . is marked as invalid because of a previous signature for expected key and algorithm missing
-
unit86
2026-10-12 07:07:02.552 W Invalid DNSSEC TXT record signature for updates.moneropulse.se: validation failure <updates.moneropulse.se. TXT IN>: key for validation . is marked as invalid because of a previous signature for expected key and algorithm missing
-
unit86
2026-10-12 07:07:04.771 W Invalid DNSSEC A record signature for seeds.moneroseeds.ch: validation failure <seeds.moneroseeds.ch. A IN>: key for validation . is marked as invalid because of a previous signature for expected key and algorithm missing
-
unit86
2026-10-12 07:07:04.777 W Invalid DNSSEC TXT record signature for updates.moneropulse.ch: validation failure <updates.moneropulse.ch. TXT IN>: key for validation . is marked as invalid because of a previous signature for expected key and algorithm missing
-
unit86
2026-10-12 07:07:05.109 W Invalid DNSSEC TXT record signature for updates.moneropulse.co: validation failure <updates.moneropulse.co. TXT IN>: key for validation . is marked as invalid because of a previous signature for expected key and algorithm missing
-
unit86
2026-10-12 07:07:05.181 W Invalid DNSSEC A record signature for seeds.moneroseeds.li: validation failure <seeds.moneroseeds.li. A IN>: key for validation . is marked as invalid because of a previous signature for expected key and algorithm missing
-
unit86
2026-10-12 07:07:05.212 W Invalid DNSSEC TXT record signature for updates.moneropulse.de: validation failure <updates.moneropulse.de. TXT IN>: key for validation . is marked as invalid because of a previous signature for expected key and algorithm missing
-
unit86
sry for the spam
-
unit86
It worked after i set dns to google from cloudflare
-
br-m
<neromonero1024> try using DNS_PUBLIC=tcp://1.1.1.1 ./monerod and see if the error persists
-
br-m
<321bob321> No records in those DNS
-
br-m
<321bob321> seeds.moneroseeds.se 0 records
-
br-m
<321bob321> seeds.moneroseeds.ae.org 0 records
-
br-m
<321bob321> seeds.moneroseeds.ch 0 records
-
br-m
<321bob321> seeds.moneroseeds.li 0 records
-
br-m
<kevino:tchncs.de> i got the same logs in monerod , but this ain't unusual i think
-
br-m
<kevino:tchncs.de> its a warning not an error btw
-
jane
Maybe the new DNSSEC root key rollover?
-
unit86
from my cursory google search that makes so much sense
-
jane
"11 October 2026 | KSK-2024 is now signing the zone; KSK-2017 is no longer signing the zone. Validating resolvers must have updated trust anchors to continue validating the root zone." Seems to make sense that it started just today/yesterday
-
jane
Probably a bad handling by your resolver not returning that entry
-
br-m
<albertlarsan68:albertlarsan.fr> I think the built-in resolver in monerod does not know of the new root key and rejects it
-
br-m
<gingeropolous> i am llm