Re: bind vs glue records (fwd)

[Robert Elz <kre%munnari.OZ.AU@localhost>]

    Date:        Thu, 24 Mar 2016 17:07:02 +0000 (GMT)
    From:        Stephen Borrill <netbsd%precedence.co.uk@localhost>
    Message-ID:  <Pine.NEB.4.64.1603241706100.524%ugly.internal.precedence.co.uk@localhost>

  | BTW, the reason I referred to glue records is because of warnings from:
  | http://mxtoolbox.com/SuperTool.aspx?action=dns%3astatic.acer.com&run=toolpage

What they are referring to there is the perennial problem with glue.
That is, the same data (supposedly) is recorded in more than one place,
and it gets inconsistent.

And that will (or can) cause all kinds of problems as well, but again
it is the delegated domain's problem to fix, not the resolvers.

The parent domain could also help (perhaps should also help) by verifying
the glue data they have from time to time (once a week would usually be
enough, but perhaps aside from .com it should be possible to do daily).
If they find the auth servers returning different answers to the glue they
have, they should just update the glue.

But none of them will do that, they all wait for the delegated domain's
operators to tell them to update the glue records - and many server operators
have no idea what they are supposed to do, and just change things without
informing anyone...

kre