This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/dns-wg@ripe.net/

[dns-wg] Syntax of the "nserver:" Attribute in Domain Objects

Previous message (by thread): [dns-wg] Syntax of the "nserver:" Attribute in Domain Objects
Next message (by thread): [dns-wg] Deprecation of DOMAIN object attributes

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Chris Thompson cet1 at cam.ac.uk
Thu Aug 23 14:10:18 CEST 2012

Apart from the argument about syntax, what are (or will be) the rules about
whether glue is required or not?

That is: are in-domain nserver attributes required to specify at least
one IP address? And are IP addresses for not-in-domain nserver attributes
illegal? or ignored?

In theory, at least, there is the always awkward question of "sibling glue",
as in

  domain: 1.168.192.in-addr.arpa
  nserver: ns.2.168,192.in-addr.arpa [an-IP-address?]

  domain: 2.168.192.in-addr.arpa
  nserver: ns.1.168.192.in-addr.arpa [an-IP-address?]

whose nserver attributes are individually not-in-domain.

-- 
Chris Thompson               University of Cambridge Computing Service,
Email: cet1 at ucs.cam.ac.uk    New Museums Site, Cambridge CB2 3QH,
Phone: +44 1223 334715       United Kingdom.

Previous message (by thread): [dns-wg] Syntax of the "nserver:" Attribute in Domain Objects
Next message (by thread): [dns-wg] Deprecation of DOMAIN object attributes

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ dns-wg Archives ]