Ignore:
Timestamp:
10/14/15 17:54:51 (9 years ago)
Author:
Kris Deugau
Message:

/branches/stable

Merge bugfixes and enhancements needed for IPDB integration since 1.2.4
forward from /trunk

Location:
branches/stable
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • branches/stable

  • branches/stable/reverse-patterns.html

    r548 r690  
    1212    <div id="main">
    1313      <h2>Reverse DNS Template Reference</h2>
    14       <table class="container" cellpadding="2" cellspacing="2">
     14<!-- rdns pattern table -->
     15      <table class="container" cellpadding="2" cellspacing="2" style="max-width:850px;">
    1516        <tbody>
     17          <tr class="tableheader">
     18            <td colspan="3">Whole-IP patterns</td>
     19          </tr>
    1620          <tr class="tableheader">
    1721            <td></td>
    1822            <td>Substitution pattern</td>
    1923            <td>Example expansion using 192.168.23.45</td>
    20           </tr>
    21           <tr class="tableheader">
    22             <td colspan="3">Whole-IP patterns</td>
    2324          </tr>
    2425          <tr class="row0">
     
    4142            <td>%d</td>
    4243            <td>323241453</td>
     44          </tr>
     45          <tr class="row0">
     46            <td colspan="3">
     47              %i and %r also allow explicitly defining the separator; eg %.i or %_r.  Dot/period (.), dash (-),
     48              and underscore (_) are the only characters supported since DNS names may not contain most
     49              other non-alphanumerics.
     50            </td>
     51          </tr>
     52          <tr class="row0">
     53            <td colspan="3">
     54              %blank% may be used to specifically prevent template expansion on a segment of a block if
     55              desired;  eg, if 192.168.23.0/24 has "unused-%i.example.com" set, adding an A+PTR template
     56              for 192.168.23.48/30 of "%blank%" will leave 192.168.23.48 through .51 without PTR records
     57              unless specific entries exist for those IPs.
     58            </td>
    4359          </tr>
    4460          <tr class="tableheader">
     
    6783            <td>c0-168-023-2d</td>
    6884          </tr>
     85
     86          <tr><td colspan="3">&nbsp;</td></tr>
     87
     88          <tr class="tableheader">
     89            <td colspan="3">Extensions</td>
     90          </tr>
     91          <tr class="tableheader">
     92            <td></td>
     93            <td>Substitution pattern</td>
     94            <td>Example expansion using 192.168.23.40/29</td>
     95          </tr>
     96          <tr class="row0">
     97            <td>Network/<br />gateway/<br />broadcast</td>
     98            <td>%ngb%</td>
     99            <td>
     100              customer-%i%ngb%.example.com<br />
     101              192.168.23.40 -> customer-net.example.com<br />
     102              192.168.23.41 -> customer-gw.example.com<br />
     103              192.168.23.42 -> customer-192-168-23-42.example.com<br />
     104              192.168.23.43 -> customer-192-168-23-43.example.com<br />
     105              192.168.23.44 -> customer-192-168-23-44.example.com<br />
     106              192.168.23.45 -> customer-192-168-23-45.example.com<br />
     107              192.168.23.46 -> customer-192-168-23-46.example.com<br />
     108              192.168.23.47 -> customer-bcast.example.com
     109            </td>
     110          </tr>
     111          <tr class="row1">
     112            <td colspan="3">
     113              Any IP pattern component is blanked on the network, gateway, and broadcast IPs when this is
     114              used.<br />
     115              Each of n, g, or b can be prefixed with a dash, eg %-ng-b% or %n-g-b%, which will
     116              blank that entire entry instead of substituting <tt>net</tt>, <tt>gw</tt>, or <tt>bcast</tt>.
     117            </td>
     118          </tr>
     119          <tr class="row0">
     120            <td>n'th usable IP</td>
     121            <td>%c</td>
     122            <td>
     123              customer-%3d-%c.example.com<br />
     124              192.168.23.40 -> customer-23.example.com<br />
     125              192.168.23.41 -> customer-23.example.com<br />
     126              192.168.23.42 -> customer-23-1.example.com<br />
     127              192.168.23.43 -> customer-23-2.example.com<br />
     128              192.168.23.44 -> customer-23-3.example.com<br />
     129              192.168.23.45 -> customer-23-4.example.com<br />
     130              192.168.23.46 -> customer-23-5.example.com<br />
     131              192.168.23.47 -> customer-23.example.com
     132            </td>
     133          </tr>
     134          <tr class="row1">
     135            <td colspan="3">
     136              c can be prefixed with a dash (%-c), which starts the numbering from the conventional gateway IP
     137              instead.  (.41 above would be 1, .42 2, etc, finishing with 6 at .46).
     138            </td>
     139          </tr>
    69140        </tbody>
    70141      </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>
     142<!-- done rdns pattern table -->
     143
    81144    </div>
    82145  </body>
Note: See TracChangeset for help on using the changeset viewer.