[db-wg] Re: [dns-wg] Proposal to change the syntax of "nserver:" attribute
- Previous message (by thread): [dns-wg] Re: [db-wg] Proposal to change the syntax of "nserver:" attribute
- Next message (by thread): [db-wg] Re: [dns-wg] Proposal to change the syntax of "nserver:" attribute
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Peter Koch
pk at DENIC.DE
Mon May 15 10:30:20 CEST 2006
Mornin' On Mon, May 15, 2006 at 09:02:50AM +0200, Katie Petrusha wrote: > We plan to automate management of DNS delegation in the e164.arpa zone (ENUM). good! > nserver: [domain_name] /or/ > nserver: [domain_name] [ipv4_address] /or/ > nserver: [domain_name] [ipv6_address] What's the reason not to use one line per server and list all v4 an/or v6 addresses within that one line? > If [domain_name] is followed by an IP address, it must be inside the zone > that is being delegated. Any level of a glue name is supported within the > valid domain name syntax. <nitpick>s/inside the zone/inside the domain</nitpick>, since one might have a name server even in a deeper zone. _Unless_ however this was meant as a requirement, but then I can't understand the second sentence. > domain: example.com > nserver: ns1.test.net 168.0.0.1 > nserver: ns1.test.net 0::0 > nserver: ns1.example.com > nserver: ns1.d1.example.com That should probably read 'domain: test.net' (or better s/test/example/). > Consequences for the delegation checks: > > DNS checks applicable to glue records will be added to the Zone Delegation > Checker (http://www.ripe.net/rs/reverse/delcheck/delcheck_descr.html) Since I've not found the keyword glue on this page, could these checks be circulated to the dns-wg in advance, please? Thanks, Peter
- Previous message (by thread): [dns-wg] Re: [db-wg] Proposal to change the syntax of "nserver:" attribute
- Next message (by thread): [db-wg] Re: [dns-wg] Proposal to change the syntax of "nserver:" attribute
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]