Changes between Version 20 and Version 21 of ZoneLoadingRequirements


Ignore:
Timestamp:
Jan 2, 2013, 1:53:50 PM (5 years ago)
Author:
shane
Comment:

Clarify $ORIGIN are relative, and define warning for it. Specify ownername after $INCLUDE

Legend:

Unmodified
Added
Removed
Modified
  • ZoneLoadingRequirements

    v20 v21  
    174174[http://tools.ietf.org/html/rfc1035#section-5.1 RFC 1035], section 5.1, paragraph 3
    175175
     176$ORIGIN names that do not with a dot are usually interpreted as a warning, and should
     177be reported. $ORIGIN names that do not end with a dot are interpreted as a normal
     178name, relative to the current origin.
     179
    176180==== 3.3.7 $INCLUDE control entry ====
    177181The $INCLUDE inserts the named file into the current file, optionally
     
    358362
    359363[http://tools.ietf.org/html/rfc3597#section-5 RFC 3597], section 5
     364
     365==== 3.3.28 Ownername after $INCLUDE file ====
     366
     367The "previous name" after an $INCLUDE is the same as before the $INCLUDE.
     368For example with this:
     369
     370{{{
     371foo.example.com. IN A 192.0.2.1
     372$INCLUDE some_file ; which ends with "bar.example.com. IN A 192.0.2.2"
     373      IN AAAA 2001:db8::1
     374}}}
     375
     376We use foo.example.com for the AAAA record. Note that this is different
     377from some other implementations, and not fully specified in RFCs.
    360378
    361379=== 3.4 RFC implementation requirements: zone definition ===