In message <hadipa$o6...@sepe.rau.edu.uy>, Sergio Ramirez writes: > Hi, > > In the following example, the authoritive server for > zone .xx has configured the delegations of the zones example.xx > and otherexample.xx: > > example.xx NS ns1.example.xx > example.xx NS ns2.example.xx > ns1.example.xx A 11.22.33.44 > ns2.example.xx A 11.22.33.55 > otherexample.xx NS ns3.example.xx > otherexample.xx NS ns4.example.xx > > the bind report these messages: > > "ns3.example.xx has no SIBLING GLUE address records (A or AAAA)" > "ns4.example.xx has no SIBLING GLUE address records (A or AAAA)" > > because the glue records are not configured in the zone .xx, for > ns3.example.xx and ns4.example.xx > > Are these glue records requiered ? > > I understand that is not. Is this right ? > > Regards, > -- > Sergio R. > _______________________________________________ > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users
Whether SIBLING GLUE is needed or not depends on what other glue there is. Take this example. The sibling glue is required for the delegation to work. otherexample.xx NS ns3.example.xx otherexample.xx NS ns4.example.xx example.xx NS ns1.otherexample.xx example.xx NS ns2.otherexample.xx There are even more complicated examples that require out of zone glue to work. Working out which glue is accepted is a trade-off between being able to track down bad data and having a delegation work. Named accepts and returns glue that is under the parent. Bad glue is then traceable. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org _______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users