forked from mikhail-pridushchenko/sheerdns-ng
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathsheerdns-ng.html
711 lines (710 loc) · 21.8 KB
/
sheerdns-ng.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<meta name="generator" content="groff -Thtml, see www.gnu.org">
<meta name="Content-Style" content="text/css"><title>sheerdns</title>
</head>
<body>
<h1 align="center">sheerdns-ng<br>
<small style="font-style: italic;"><small>based on
sheerdns</small></small><br>
</h1>
<br>
<a href="#NAME">NAME</a><br>
<a href="#SYNOPSIS">SYNOPSIS</a><br>
<a href="#DESCRIPTION">DESCRIPTION</a><br>
<a href="#OPTIONS">OPTIONS</a><br>
<a href="#WILDCARDS">WILDCARDS</a><br>
<a href="#EXAMPLES">EXAMPLES</a><br>
<a href="#ENVIRONMENT%20VARIABLES">ENVIRONMENT VARIABLES</a><br>
<a href="#CONFIGURATION%20FILE">CONFIGURATION FILE</a><br>
<a href="#BUGS">BUGS</a><br>
<a href="#FILES">FILES</a><br>
<a href="#STANDARDS">STANDARDS</a><br>
<a href="#AVAILABILITY">AVAILABILITY</a><br>
<a href="#AUTHOR">AUTHOR</a><br>
<a href="#SEE%20ALSO">SEE ALSO</a><br>
<hr>
<!-- Creator : groff version 1.18.1 --><!-- CreationDate: Thu Feb 10 22:33:03 2005 --><a name="NAME"></a>
<h2>NAME</h2>
<!-- INDENTATION -->
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="10%"></td>
<td width="89%">
<p>sheerdns - master DNS server</p>
</td>
</tr>
</tbody>
</table>
</p>
<a name="SYNOPSIS"></a>
<h2>SYNOPSIS</h2>
<!-- INDENTATION -->
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="10%"></td>
<td width="89%">
<p><b>sheerdns</b> [<b>-ttl</b> <i>seconds</i>]
[<b>-p</b>
<i>port</i>] [<b>-i</b> <i>iface-ip</i>]
[<b>-d</b>]</p>
<!-- INDENTATION -->
<p><b>sheerdnshash</b> <i>string</i></p>
</td>
</tr>
</tbody>
</table>
</p>
<a name="DESCRIPTION"></a>
<h2>DESCRIPTION</h2>
<!-- INDENTATION -->
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="10%"></td>
<td width="89%">
<p><b>sheerdns</b> is a master DNS server whose
zone records
are stored on a One-Record-Per-File bases. Because of this,
<b>sheerdns</b> is the simplest of any DNS to
configure, the
easiest to update, and the most efficient for networks that
experience a lot of updates (for example master servers for
dynamic IP address ranges). You <i>never</i> have to
restart
<b>sheerdns</b>; any updates are available
immediately
without having to notify the <b>sheerdns</b> process.</p>
<!-- INDENTATION -->
<p><b>sheerdns</b> is secure. <b>sheerdns</b>
is fast
because Unix operating systems cache small files in
memory.</p>
<!-- INDENTATION -->
<p><b>sheerdns</b> is written in strict ANSI C.</p>
<!-- INDENTATION -->
<p><b>sheerdnshash</b> creates a directory
<b>/var/sheerdns/</b><i>XX</i><b>/</b><i>string</i><b>/</b>,
where <i>XX</i> is a hash of the string, and outputs
<i>XX</i> to stdout.<br>
<span style="font-weight: bold;">sheerdns</span>
creates a directory <span style="font-weight: bold;">/var/sheerdns/default</span>,
where you can put a default responses for any DNS queries.</p>
<!-- INDENTATION -->
<p>Note that <b>sheerdns</b> is <i>not</i>
a caching
nameserver for resolving queries about the rest of the
Internet. It is a master server for telling the rest of
Internet about the zones you are responsible for. No clients
anywhere should have a <b>/etc/resolv.conf</b>
"nameserver" entry that points to a
<b>sheerdns</b> server.</p>
<!-- INDENTATION -->
<p><b>sheerdns</b> works by looking up queries
from files of
the name:</p>
</td>
</tr>
</tbody>
</table>
</p>
<!-- INDENTATION -->
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="20%"></td>
<td width="79%">
<p><b>/var/sheerdns/default/</b>
</p>
<p><b>/var/sheerdns/</b><i>XX</i><b>/</b><i>full.doma.in</i><b>/</b><i>query-type</i>. </p>
</td>
</tr>
</tbody>
</table>
</p>
<!-- INDENTATION -->
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="10%"></td>
<td width="89%">
<p>These files are created by the administrator (or one of
his/her sh/perl/python/php scripts). You can write anything
to these files -- <b>sheerdns</b> will answer with their
contents even if they are bogus. The <i>XX</i> is an
upper-case two character hex number of the range <b>00</b>
to <b>FF</b>.</p>
<!-- INDENTATION -->
<p>Each of these files contains one or more newline
separated strings. There should be no leading newlines, and
zero or one trailing newline. In the case of A records, the
strings are IP addresses, for example <b>192.0.2.1</b>. If
there are several IP addresses in the file, they are
order-randomized before return.</p>
<!-- INDENTATION -->
<p>In the case of PTR, MX, NS, SOA, and CNAME records, the
strings are host-names. For MX and NS you can have multiple
hostnames per file, but for PTR, SOA, and CNAME records, you
must have only one entry in each file. TXT records can
contain anything---one record is returned for each line in
the file (TXT is not discussed again).</p>
<!-- INDENTATION -->
<p>For MX records, the first entry in the file is given a
priority of 10, the second 20, and so on.</p>
<!-- INDENTATION -->
<p>For SOA records, the modified time of the file counts as
the Serial-Number, and the contents as the name-server. The
administrator email address returned is just the name-server
prepended with "hostmaster", so you should make
sure this email address exists for that domain and is
reachable. The remaining fields are hardcoded to reasonable
default values. Note that time fields for SOA records are
only used for zone transfers hence are irrelevant here.</p>
<!-- INDENTATION -->
<p>For NS and SOA records, an entry for a domain is valid
for all domains below it. For example, if you create an NS
record for the domain <b>test.edu</b>, then that NS record
is returned for the domain <b>www.test.edu</b>,
<b>ftp.henry.test.edu</b>, as well as
<b>user1.lab.chemistry.test.edu</b>. On the other
hand a
separate NS record can be created for
<b>lab.chemistry.test.edu</b>, applying to all
domains
<b>*.lab.chemistry.test.edu</b>,
<b>*.*.lab.chemistry.test.edu</b> etc. This works
because
<b>sheerdns</b> searches for NS records by
iteratively
deleting the text up to the front most dot until a
nameserver is found. This gives the intuitively expected
behavior.</p>
<!-- INDENTATION -->
<p>There is a special case for using <b>sheerdns</b>
as a
root nameserver. See the example below.</p>
<!-- INDENTATION -->
<p><b>sheerdns</b> does lookups in lower case.
All filenames
and file contents must be in lower case. <b>sheerdns</b>
does no interpretation of any of the file contents except
for the characters \f\n\r\t\v and the dot character, so it
can probably manage UTF-8 domain names without a
problem.</p>
<!-- INDENTATION -->
<p><b>sheerdns</b> does not send TCP results
longer than
1024 bytes, neither does it set the TC bit if the response
ought to be longer. If there are too many records to fit in
the packet, then trailing records are omitted to keep within
the 1024 byte limit. The packet format will be valid
none-the-less. Administrators should ensure that their site
is not so complex that large packets need to be sent.</p>
</td>
</tr>
</tbody>
</table>
</p>
<a name="OPTIONS"></a>
<h2>OPTIONS</h2>
<!-- INDENTATION -->
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="10%"></td>
<td width="89%">
<p><b>-ttl</b> <i>seconds</i></p>
</td>
</tr>
</tbody>
</table>
</p>
<!-- INDENTATION -->
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="21%"></td>
<td width="77%">
<p>The Time-To-Live field to be set on outgoing packets.
Records that are likely to be fixed (not dynamic) are given
a 3-day ttl. Examples are the IP address of the NS record,
and the CNAME, MX, NS, and SOA records. All other records
are given the ttl specified in this option. The default is
86400 seconds (one day). This option should be set to 10
seconds for dynamic IP address ranges.</p>
</td>
</tr>
</tbody>
</table>
<!-- INDENTATION -->
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="10%"></td>
<td width="89%">
<p><b>-p</b> <i>port</i></p>
</td>
</tr>
</tbody>
</table>
</p>
<!-- INDENTATION -->
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="21%"></td>
<td width="77%">
<p>Listen port. Default is 53.</p>
</td>
</tr>
</tbody>
</table>
<!-- INDENTATION -->
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="10%"></td>
<td width="89%">
<p><b>-i</b> <i>iface-ip</i></p>
</td>
</tr>
</tbody>
</table>
</p>
<!-- INDENTATION -->
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="21%"></td>
<td width="77%">
<p><i>inface-ip</i> is the network card you
want to listen
on. If omitted, it defaults to 0.0.0.0 meaning <i>all</i>
interfaces.</p>
</td>
</tr>
</tbody>
</table>
<!-- TABS -->
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="4" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="13%"></td>
<td width="2%">
<p><b>-d</b></p>
</td>
<td width="5%"></td>
<td width="77%">
<p>Fork twice into the background (to run as a daemon
process); otherwise <b>sheerdns</b> runs in the
foreground.</p>
</td>
</tr>
</tbody>
</table>
</p>
<a name="WILDCARDS"></a>
<h2>WILDCARDS</h2>
<!-- INDENTATION -->
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="10%"></td>
<td width="89%">
<p>An entry such as <b>*.test.com</b> will
return results as
expected. This means you should</p>
</td>
</tr>
</tbody>
</table>
</p>
<!-- INDENTATION -->
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="20%"></td>
<td width="79%">
<pre>echo 192.0.2.1 > /var/sheerdns/‘sheerdnshash ’*’.test.com‘/’*’.test.com/A<br>dig @localhost A lsdjkfhalsdfkjh.test.com<br></pre>
</td>
</tr>
</tbody>
</table>
</p>
<!-- INDENTATION -->
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="10%"></td>
<td width="89%">
<p>Note that quotes around the asterisk. This means the
filename has an asterisk in it which is never a good idea on
Unix systems.</p>
</td>
</tr>
</tbody>
</table>
</p>
<a name="EXAMPLES"></a>
<h2>EXAMPLES</h2>
<!-- INDENTATION -->
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="10%"></td>
<td width="89%">
<p>These examples assume that you have already invoked
<b>sheerdns</b>, that you know what kind of records
are
appropriate to create, that you do not guess, and that you
realize that the examples are merely shown for demonstration
and not as a recommendation for the kinds of records really
required.</p>
<!-- INDENTATION -->
<p>Add mutiple A records for <b>test.com</b>
for round robin
sharing:</p>
</td>
</tr>
</tbody>
</table>
</p>
<!-- INDENTATION -->
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="20%"></td>
<td width="79%">
<pre>echo 192.0.2.1 > /var/sheerdns/‘sheerdnshash test.com‘/test.com/A<br>echo 192.0.2.2 >> /var/sheerdns/‘sheerdnshash test.com‘/test.com/A<br>echo 192.0.2.3 >> /var/sheerdns/‘sheerdnshash test.com‘/test.com/A<br>dig @localhost A test.com<br>dig @localhost A test.com<br>dig @localhost A test.com<br></pre>
</td>
</tr>
</tbody>
</table>
</p>
<!-- INDENTATION -->
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="10%"></td>
<td width="89%">
<p>Add a PTR records for <b>test.com</b>:</p>
</td>
</tr>
</tbody>
</table>
</p>
<!-- INDENTATION -->
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="20%"></td>
<td width="79%">
<pre>echo test.com > /var/sheerdns/‘sheerdnshash 192.0.2.1‘/192.0.2.1/PTR<br>echo test.com > /var/sheerdns/‘sheerdnshash 192.0.2.2‘/192.0.2.2/PTR<br>echo test.com > /var/sheerdns/‘sheerdnshash 192.0.2.3‘/192.0.2.3/PTR<br>echo ns.ispfortest.net > /var/sheerdns/‘sheerdnshash 192.0.2‘/192.0.2/NS<br>dig @localhost PTR 1.2.0.192.in-addr.arpa<br></pre>
</td>
</tr>
</tbody>
</table>
</p>
<!-- INDENTATION -->
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="10%"></td>
<td width="89%">
<p>Add an MX record for <b>test.com</b> with
(IMPORTANT)
<i>both</i> its forward, reverse, <i>and</i>
nameserver
lookups:</p>
</td>
</tr>
</tbody>
</table>
</p>
<!-- INDENTATION -->
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="20%"></td>
<td width="79%">
<pre>echo mail.test.com > /var/sheerdns/‘sheerdnshash test.com‘/test.com/MX<br>echo 192.0.3.99 > /var/sheerdns/‘sheerdnshash mail.test.com‘/mail.test.com/A<br>echo mail.test.com > /var/sheerdns/‘sheerdnshash 192.0.3.99‘/192.0.3.99/PTR<br>echo ns.ispfortest.net > /var/sheerdns/‘sheerdnshash test.com‘/test.com/NS<br>dig @localhost MX test.com<br></pre>
</td>
</tr>
</tbody>
</table>
</p>
<!-- INDENTATION -->
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="10%"></td>
<td width="89%">
<p>Add an SOA record for <b>test.com</b>. Note
that although
SOA records are only required for zone transfers, some
institutions may demand them. The only configurable data
item in the SOA record is the authoritative nameserver which
is inserted as follows:</p>
</td>
</tr>
</tbody>
</table>
</p>
<!-- INDENTATION -->
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="20%"></td>
<td width="79%">
<pre>echo ns.ispfortest.net > /var/sheerdns/‘sheerdnshash test.com‘/test.com/SOA<br>dig @localhost SOA test.com<br></pre>
</td>
</tr>
</tbody>
</table>
</p>
<!-- INDENTATION -->
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="10%"></td>
<td width="89%">
<p>Add an CNAME record for <b>www.test.com</b>.
If you use a
CNAME, you should only have one line in the CNAME file, and
it should be the only file in the domain’s directory,
and the CNAME should not appear anywhere as the text of any
other records. I repeat: "<i>If you use a CNAME, you
should only have one line in the CNAME file, and it should
be the only file in the domain’s directory, and the
CNAME should not appear anywhere as the text of any other
records.</i>". Do I need to say it a third time?</p>
</td>
</tr>
</tbody>
</table>
</p>
<!-- INDENTATION -->
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="20%"></td>
<td width="79%">
<pre>echo "I will not leave out the next command"<br>rm -f /var/sheerdns/‘sheerdnshash www.test.com‘/www.test.com/*<br>grep -w ’www[.]test[.]com’ ‘find /var/sheerdns/ -type f‘ && \<br> echo "This DNS setup is broken"<br>echo "I will not leave out the previous command"<br>echo test.com > /var/sheerdns/‘sheerdnshash www.test.com‘/www.test.com/CNAME<br>dig @localhost A www.test.com<br></pre>
</td>
</tr>
</tbody>
</table>
</p>
<!-- INDENTATION -->
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="10%"></td>
<td width="89%">
<p>Using <b>sheerdns</b> as a root nameserver.
Note that for
root domains, the hash is especially omitted:</p>
</td>
</tr>
</tbody>
</table>
</p>
<!-- INDENTATION -->
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="20%"></td>
<td width="79%">
<pre>> /var/sheerdns/NS<br>> /var/sheerdns/SOA<br>for i in \<br> a:198.41.0.4 h:128.63.2.53 c:192.33.4.12 g:192.112.36.4 \<br> f:192.5.5.241 b:128.9.0.107 j:192.58.128.30 k:193.0.14.129 \<br> l:198.32.64.12 m:202.12.27.33 i:192.36.148.17 e:192.203.230.10 ; do<br> N=‘echo $i | cut -f1 -d:‘.root-servers.net<br> echo $i | cut -f2 -d: > /var/sheerdns/‘sheerdnshash $N‘/$N/A<br> echo $N >> /var/sheerdns/NS<br> echo $N >> /var/sheerdns/SOA<br>done<br>dig @localhost SOA .<br>dig @localhost NS .<br></pre>
</td>
</tr>
</tbody>
</table>
</p>
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="10%"></td>
<td width="89%">
<p>Add <span style="font-weight: bold;">default responses</span> for any queries. Note
that if domain exist at <span style="font-style: italic;">/var/sheerdns/`sheerdnshash domain`/domain</span> and have A record then reply from<span style="font-style: italic;"> /var/sheerdns/default</span> will not happend:</p>
</td>
</tr>
</tbody>
</table>
</p>
<!-- INDENTATION -->
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="20%"></td>
<td width="79%">
<pre>echo 192.168.0.1 > /var/sheerdns/default/A<br>dig @localhost A google.com<br></pre>
</td>
</tr>
</tbody>
</table>
</p>
<a name="ENVIRONMENT VARIABLES"></a>
<h2>ENVIRONMENT VARIABLES</h2>
<!-- INDENTATION -->
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="10%"></td>
<td width="89%">
<p>There are no applicable environment variables.</p>
</td>
</tr>
</tbody>
</table>
</p>
<a name="CONFIGURATION FILE"></a>
<h2>CONFIGURATION FILE</h2>
<!-- INDENTATION -->
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="10%"></td>
<td width="89%">
<p><b>sheerdns</b> has no configuration file.
It just
works.</p>
</td>
</tr>
</tbody>
</table>
</p>
<a name="BUGS"></a>
<h2>BUGS</h2>
<!-- INDENTATION -->
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="10%"></td>
<td width="89%">
<p>No bugs are known at present.</p>
</td>
</tr>
</tbody>
</table>
</p>
<a name="FILES"></a>
<h2>FILES</h2>
<!-- INDENTATION -->
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="10%"></td>
<td width="89%">
<p><b>sheerdns</b> makes use of the directory
<b>/var/sheerdns/*/*</b> to lookup entries. These
directories are created on startup. No errors are reported
if the directories could not be created.</p>
</td>
</tr>
</tbody>
</table>
</p>
<a name="STANDARDS"></a>
<h2>STANDARDS</h2>
<!-- INDENTATION -->
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="10%"></td>
<td width="89%">
<p>Hmmm, more than I have time to read. Start with
RFC-1035.</p>
</td>
</tr>
</tbody>
</table>
</p>
<a name="AVAILABILITY"></a>
<h2>AVAILABILITY</h2>
<!-- INDENTATION -->
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="10%"></td>
<td width="89%">
<p>https://github.com/taraszka/sheerdns-ng will always have
links to the
latest sheerdns.tar.gz source file as well as this page.</p>
</td>
</tr>
</tbody>
</table>
</p>
<a name="AUTHOR"></a>
<h2>AUTHOR</h2>
<!-- INDENTATION -->
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="10%"></td>
<td width="89%">
<p>Krzysztof Taraszka
<[email protected]></p>
<p>Paul Sheer <[email protected]></p>
</td>
</tr>
</tbody>
</table>
</p>
<a name="SEE ALSO"></a>
<h2>SEE ALSO</h2>
<!-- INDENTATION -->
<p>
<table border="0" cellpadding="0" cellspacing="0" cols="2" frame="void" rules="none" width="100%">
<tbody>
<tr align="left" valign="top">
<td width="10%"></td>
<td width="89%">
<p><b>dig</b>(1), <b>nslookup</b>(8),
<b>BIND</b>,
<b>MyDNS</b>, <b>djbdns</b>, <b>tinydns</b>,
<b>Dents</b>.</p>
</td>
</tr>
</tbody>
</table>
</p>
<hr>
</body></html>