Event JSON
{
"id": "6a7803641a283e2c12d7c7d36d3150ce513248da6ba40db8b42417af21cd8fb0",
"pubkey": "af6872898e8bb1796ee32e4d1d9d49b35e9762741cfbf4cfa569ca0f14f4124f",
"created_at": 1685617948,
"kind": 1,
"tags": [
[
"p",
"c988135b30cb5273b10c9c3f775b766ce34ea11885ffb7a7044e6b7fdf97a608",
"wss://relay.mostr.pub"
],
[
"p",
"2b4282d4cac7f9c53d60a67892b459bf4ccfe927675d386664835485b04e43b0",
"wss://relay.mostr.pub"
],
[
"e",
"c129efa3686421b0bdd16f5f8802ebaa73b2e40789dd04aa7fe6a93dae875b3f",
"wss://relay.mostr.pub",
"reply"
],
[
"mostr",
"https://mastodon.social/users/cstrotm/statuses/110468657861371961"
]
],
"content": "nostr:npub1exypxkesedf88vgvnslhwkmkdn35aggcshlm0fcyfe4hlhuh5cyqx2366y The number of delegations NS records is not the problem. The problem is a parent-child delegation mismatch, see “WHEN PARENTS AND CHILDREN DISAGREE:\nDIVING INTO DNS DELEGATION INCONSISTENCY” https://ripe80.ripe.net/presentations/2-RIPE80-Sommese.pdf\n\nI still see the issue. All SOA serials are the same on all auth name server, with the TTL rather high, it does not look like a migration in progress.\n\nIt’s currently not an operational issue, but can create one down the road.",
"sig": "44a392a97e870cbe01199c743e3969caeeb395185c065a0badb332726febd43f40eafea83c430c1b4c1f1efd8f708964dcc3312f25216b7a3d2fe6a10033d309"
}