Ignore:
Timestamp:
07/27/15 17:32:49 (9 years ago)
Author:
Kris Deugau
Message:

/trunk

Add some new template pattern options to autogenerate -net/-gw/-bcast
tags, and "n'th usable IP in range". Update online reference
reverse-patterns.html with the new patterns.

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/reverse-patterns.html

    r534 r685  
    1212    <div id="main">
    1313      <h2>Reverse DNS Template Reference</h2>
    14       <table class="container" cellpadding="2" cellspacing="2">
     14      <table class="container" cellpadding="2" cellspacing="2" style="max-width:850px;">
    1515        <tbody>
    1616          <tr class="tableheader">
    … …  
    4242            <td>323241453</td>
    4343          </tr>
     44          <tr class="row0">
     45            <td colspan="3">
     46              %i and %r also allow explicitly defining the separator; eg %.i or %_r.  Dot/period (.), dash (-),
     47              and underscore (_) are the only characters supported since DNS names may not contain most
     48              other non-alphanumerics.
     49            </td>
     50          </tr>
     51          <tr class="row0">
     52            <td colspan="3">
     53              %blank% may be used to specifically prevent template expansion on a segment of a block if
     54              desired;  eg, if 192.168.23.0/24 has "unused-%i.example.com" set, adding an A+PTR template
     55              for 192.168.23.48/30 of "%blank%" will leave 192.168.23.48 through .51 without PTR records
     56              unless specific entries exist for those IPs.
     57            </td>
     58          </tr>
    4459          <tr class="tableheader">
    4560            <td colspan="3">Per-octet patterns (1, 2, 3, or 4 specify
    … …  
    6782            <td>c0-168-023-2d</td>
    6883          </tr>
     84
     85          <tr class="row0"><td colspan="3">&nbsp;</td></tr>
     86
     87          <tr class="tableheader">
     88            <td colspan="3">Extensions</td>
     89          </tr>
     90          <tr class="tableheader">
     91            <td></td>
     92            <td>Substitution pattern</td>
     93            <td>Example expansion using 192.168.23.40/29</td>
     94          </tr>
     95          <tr class="row0">
     96            <td>Network/<br />gateway/<br />broadcast</td>
     97            <td>%ngb%</td>
     98            <td>
     99              customer-%i%ngb%.example.com<br />
     100              192.168.23.40 -> customer-net.example.com<br />
     101              192.168.23.41 -> customer-gw.example.com<br />
     102              192.168.23.42 -> customer-192-168-23-42.example.com<br />
     103              192.168.23.43 -> customer-192-168-23-43.example.com<br />
     104              192.168.23.44 -> customer-192-168-23-44.example.com<br />
     105              192.168.23.45 -> customer-192-168-23-45.example.com<br />
     106              192.168.23.46 -> customer-192-168-23-46.example.com<br />
     107              192.168.23.47 -> customer-bcast.example.com
     108            </td>
     109          </tr>
     110          <tr class="row1">
     111            <td colspan="3">
     112              Any IP pattern component is blanked on the network, gateway, and broadcast IPs when this is
     113              used.<br />
     114              Each of n, g, or b can be prefixed with a dash, eg %-ng-b% or %n-g-b%, which will
     115              blank that entire entry instead of substituting <tt>net</tt>, <tt>gw</tt>, or <tt>bcast</tt>.
     116            </td>
     117          </tr>
     118          <tr class="row0">
     119            <td>n'th usable IP</td>
     120            <td>%c</td>
     121            <td>
     122              customer-%3d-%c.example.com<br />
     123              192.168.23.40 -> customer-23.example.com<br />
     124              192.168.23.41 -> customer-23.example.com<br />
     125              192.168.23.42 -> customer-23-1.example.com<br />
     126              192.168.23.43 -> customer-23-2.example.com<br />
     127              192.168.23.44 -> customer-23-3.example.com<br />
     128              192.168.23.45 -> customer-23-4.example.com<br />
     129              192.168.23.46 -> customer-23-5.example.com<br />
     130              192.168.23.47 -> customer-23.example.com
     131            </td>
     132          </tr>
     133          <tr class="row1">
     134            <td colspan="3">
     135              c can be prefixed with a dash (%-c), which starts the numbering from the conventional gateway IP
     136              instead.  (.41 above would be 1, .42 2, etc, finishing with 6 at .46).
     137            </td>
     138          </tr>
    69139        </tbody>
    70140      </table>
    71       <p> %i and %r also allow explicitly defining the separator; eg %.i
    72         or %_r. '.', '-', and '_' are the only characters<br />
    73         supported since DNS names may not contain most other
    74         non-alphanumerics.</p>
    75       <p>%blank% may be used to specifically prevent template expansion on
    76         a segment of a block if desired;  eg, if<br />
    77         192.168.23.0/24 has "unused-%i.example.com" set, adding an A+PTR
    78         template for 192.168.23.48/30 of<br />
    79         "%blank%" will leave 192.168.23.48 through .51 without PTR records
    80         unless specific entries exist for those IPs.<p>
     141
    81142    </div>
    82143  </body>
Note: See TracChangeset for help on using the changeset viewer.