source: trunk/rDNS.html@ 798

Last change on this file since 798 was 778, checked in by Kris Deugau, 9 years ago

/trunk

Build a quick hack to import the rDNS pattern table into rDNS.html from
the DNSAdmin source file instead of hand-copying it. Still committing
rDNS.html to SVN for convenience since it shouldn't change much.
File size: 6.4 KB
Line 
1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
2<html>
3<head>
4 <title>IP Database Reverse DNS Help</title>
5 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
6 <link rel="stylesheet" type="text/css" href="ipdb.css">
7 <link rel="stylesheet" type="text/css" href="local.css">
8</head>
9<body>
10
11<!--
12 This file is generated, and should not be edited directly. Edit gen-rDNS.pl to edit the header below, and
13 see https://secure.deepnet.cx/svn/dnsadmin/trunk/reverse-patterns.html for the tables.
14-->
15
16<p>The IP Database can pass reverse DNS information back and forth to a DNS management backend to simplify
17maintenance of the reverse DNS records associated with the IPs being managed.</p>
18
19<p>Several shortcuts can be used when specifying a pattern for an IPv4 netblock, which will be expanded to
20actual DNS records by the DNS management system.</p>
21
22<p>Entries should generally only be present in the "Per-IP reverse entries" section if they are different from
23the block pattern.</p>
24
25<p>Template patterns are not supported for IPv6 allocations due to the size of the address space and typical
26size of allocations.</p>
27
28<p>"(cached)" or "[local]" indicates the rDNS information shown came from IPDB records,
29and not the DNS management utility. It may be out of date, or DNS
30management integration may be missing or incomplete for this block.</p>
31
32<!-- rdns pattern table -->
33 <table class="container" cellpadding="2" cellspacing="2" style="max-width:850px;">
34 <tbody>
35 <tr class="tableheader">
36 <td colspan="3">Whole-IP patterns</td>
37 </tr>
38 <tr class="tableheader">
39 <td></td>
40 <td>Substitution pattern</td>
41 <td>Example expansion using 192.168.23.45</td>
42 </tr>
43 <tr class="row0">
44 <td>Dashed IP</td>
45 <td>%i</td>
46 <td>192-168-23-45</td>
47 </tr>
48 <tr class="row1">
49 <td>Reverse dashed IP</td>
50 <td>%r</td>
51 <td>45-23-168-192</td>
52 </tr>
53 <tr class="row0">
54 <td>Hex-coded IP</td>
55 <td>%h</td>
56 <td>c0a8172d</td>
57 </tr>
58 <tr class="row1">
59 <td>Decimal IP</td>
60 <td>%d</td>
61 <td>323241453</td>
62 </tr>
63 <tr class="row0">
64 <td colspan="3">
65 %i and %r also allow explicitly defining the separator; eg %.i or %_r. Dot/period (.), dash (-),
66 and underscore (_) are the only characters supported since DNS names may not contain most
67 other non-alphanumerics.
68 </td>
69 </tr>
70 <tr class="row0">
71 <td colspan="3">
72 %blank% may be used to specifically prevent template expansion on a segment of a block if
73 desired; eg, if 192.168.23.0/24 has "unused-%i.example.com" set, adding an A+PTR template
74 for 192.168.23.48/30 of "%blank%" will leave 192.168.23.48 through .51 without PTR records
75 unless specific entries exist for those IPs.
76 </td>
77 </tr>
78 <tr class="tableheader">
79 <td colspan="3">Per-octet patterns (1, 2, 3, or 4 specify
80 the octet; d, h or 0 specify decimal, hexidecimal, or
81 0-padded decimal)</td>
82 </tr>
83 <tr class="row0">
84 <td>First octet, decimal</td>
85 <td>%1d</td>
86 <td>192</td>
87 </tr>
88 <tr class="row1">
89 <td>Third octet, 0-padded</td>
90 <td>%30</td>
91 <td>023</td>
92 </tr>
93 <tr class="row0">
94 <td>Fourth octet, hexidecimal</td>
95 <td>%4h</td>
96 <td>2d</td>
97 </tr>
98 <tr class="row1">
99 <td>All octets, different expansions</td>
100 <td>%1h-%2d-%30-%4h</td>
101 <td>c0-168-023-2d</td>
102 </tr>
103
104 <tr><td colspan="3">&nbsp;</td></tr>
105
106 <tr class="tableheader">
107 <td colspan="3">Extensions</td>
108 </tr>
109 <tr class="tableheader">
110 <td></td>
111 <td>Substitution pattern</td>
112 <td>Example expansion using 192.168.23.40/29</td>
113 </tr>
114 <tr class="row0">
115 <td>Network/<br />gateway/<br />broadcast</td>
116 <td>%ngb%</td>
117 <td>
118 customer-%i%ngb%.example.com<br />
119 192.168.23.40 -> customer-net.example.com<br />
120 192.168.23.41 -> customer-gw.example.com<br />
121 192.168.23.42 -> customer-192-168-23-42.example.com<br />
122 192.168.23.43 -> customer-192-168-23-43.example.com<br />
123 192.168.23.44 -> customer-192-168-23-44.example.com<br />
124 192.168.23.45 -> customer-192-168-23-45.example.com<br />
125 192.168.23.46 -> customer-192-168-23-46.example.com<br />
126 192.168.23.47 -> customer-bcast.example.com
127 </td>
128 </tr>
129 <tr class="row1">
130 <td colspan="3">
131 Any IP pattern component is blanked on the network, gateway, and broadcast IPs when this is
132 used.<br />
133 Each of n, g, or b can be prefixed with a dash, eg %-ng-b% or %n-g-b%, which will
134 blank that entire entry instead of substituting <tt>net</tt>, <tt>gw</tt>, or <tt>bcast</tt>.
135 </td>
136 </tr>
137 <tr class="row0">
138 <td>n'th usable IP</td>
139 <td>%c</td>
140 <td>
141 customer-%3d-%c.example.com<br />
142 192.168.23.40 -> customer-23.example.com<br />
143 192.168.23.41 -> customer-23.example.com<br />
144 192.168.23.42 -> customer-23-1.example.com<br />
145 192.168.23.43 -> customer-23-2.example.com<br />
146 192.168.23.44 -> customer-23-3.example.com<br />
147 192.168.23.45 -> customer-23-4.example.com<br />
148 192.168.23.46 -> customer-23-5.example.com<br />
149 192.168.23.47 -> customer-23.example.com
150 </td>
151 </tr>
152 <tr class="row1">
153 <td colspan="3">
154 c can be prefixed with a dash (%-c), which starts the numbering from the conventional gateway IP
155 instead. (.41 above would be 1, .42 2, etc, finishing with 6 at .46).
156 </td>
157 </tr>
158 </tbody>
159 </table>
160<!-- done rdns pattern table -->
161
162</body>
163</html>
Note: See TracBrowser for help on using the repository browser.