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/[email protected]/
[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] Syntax of the "nserver:" Attribute in Domain Objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Chris Thompson
cet1 at cam.ac.uk
Mon Aug 20 21:03:06 CEST 2012
On Aug 20 2012, Peter Koch wrote: >On Fri, Jul 27, 2012 at 02:57:57PM +0200, Anand Buddhdev wrote: [...snip...] >> If glue records are required, they would be written like this: >> >> nserver: ns1.2.0.192.in-addr.arpa 192.0.2.1 >> nserver: ns1.2.0.192.in-addr.arpa 2001:db8::1 >> nserver: ns2.2.0.192.in-addr.arpa 192.0.2.2 >> nserver: ns2.2.0.192.in-addr.arpa 2001:db8::2 > >While I agree with the first move, I do not see the beauty in the second. >It would appear more natural to me to list all IP addresses on a single line >after the name server's name. AOL :-) Although I have never had to use glue in our reverse domain delegations (it is perhaps a bit perverse to give NSs names in the reverse tree at all), I have been trying to nudge our forward zone providers towards thinking of the glue IPs for one NS as a *set*, rather than denormalised in the style of Anand's text. Without any notable success so far... :-( -- 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] Syntax of the "nserver:" Attribute in Domain Objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]