[dns-operations] Glue NS inconsistency for .SE? (x.ns.se only at the zone apex)

[Anand Buddhdev]

Hi Viktor,

This probably means that IIS is in the process of adding x.ns.se. They
have to start by adding it to the apex, and then updating the
delegation. This can all take some time, of course, and you're observing
things in the middle of this change.

Regards,
Anand

On 15/12/2016 02:18, Viktor Dukhovni wrote:
> 
> $ dig +noall +ans +auth +nocl +nottl +norecur -t ns se. @a.root-servers.net | sort
> se.                     NS      a.ns.se.
> se.                     NS      b.ns.se.
> se.                     NS      c.ns.se.
> se.                     NS      d.ns.se.
> se.                     NS      e.ns.se.
> se.                     NS      f.ns.se.
> se.                     NS      g.ns.se.
> se.                     NS      i.ns.se.
> se.                     NS      j.ns.se.
> 
> $ dig +noall +ans +auth +nocl +nottl +norecur -t ns se. @a.ns.se. | sort
> se.                     NS      a.ns.se.
> se.                     NS      b.ns.se.
> se.                     NS      c.ns.se.
> se.                     NS      d.ns.se.
> se.                     NS      e.ns.se.
> se.                     NS      f.ns.se.
> se.                     NS      g.ns.se.
> se.                     NS      i.ns.se.
> se.                     NS      j.ns.se.
> se.                     NS      x.ns.se.
>