@@ -9,7 +9,7 @@ has a rather large number of internal changes and also some new features, which
9
9
I am rather pleased with, even if I say so myself. I think the changes are
10
10
significant enough to warrant increasing the minor version number from 1.1 to
11
11
1.2. The differences between my previous "official" release 1.1.11 and Thomas'
12
- last release 1.1.7a are described in my previous REAME , which I have renamed
12
+ last release 1.1.7a are described in my previous README , which I have renamed
13
13
REAME.par.old. In this README I restrict myself to describing changes between
14
14
1.1.11 and 1.2.
15
15
@@ -19,7 +19,7 @@ version because the (compressed) patch file is barely smaller than the
19
19
(compressed) tar archive.
20
20
21
21
Here follows a list of some of changes in version 1.2 from a user's perspective.
22
- For a more technical description of some the changes in the code see the ChangeLog.
22
+ For a more technical description of some of the changes in the code see the ChangeLog.
23
23
For a short history about recent releases have a look at doc/html/index.html.
24
24
25
25
- First of all, two potentially rather nasty bugs have been fixed in the code
@@ -29,14 +29,73 @@ For a short history about recent releases have a look at doc/html/index.html.
29
29
statements, which could cause pdnsd to abort in a controlled fashion, but
30
30
completely unnecessarily.
31
31
32
- - Sampo Lehtinen has remarked that pdnsd sometimes fails to resolve classless
32
+ - Sampo Lehtinen has remarked that pdnsd sometimes failed to resolve classless
33
33
reversed-delegated IP addresses, and that this has something to do with the
34
34
fact that pdnsd didn't accept '/' characters in domain names. After reading
35
- some of the relevant RFC's I decided to remove all restrictions on the types
35
+ some of the relevant RFCs I decided to remove all restrictions on the types
36
36
of characters that pdnsd accepts in domain names. Of course for most
37
- applications, many characters don't make sense in domain names, but I feel
38
- that it is the responsibility of the client applicaton to reject these, not
39
- the proxy server.
37
+ applications, there are many characters which don't make sense in domain
38
+ names, but I feel that it is the responsibility of the client application to
39
+ reject these, not the proxy server.
40
+
41
+ - At the suggestion of Dan Tihelka, I have expanded to the server_ip= option
42
+ to allow the name of an interface to be specified instead of an IP address.
43
+ Presently this works for Linux only. Can someone running pdnsd on *BSD
44
+ tell me if the code for getting the address of an interface is different
45
+ for Linux and BSD-type systems?
46
+
47
+ - At the suggestion of Juliusz Chroboczek I've added an new server availability
48
+ test which can be specified with uptest=query. This can be useful as an
49
+ alternative to "uptest=ping" in case the remote server does not respond to
50
+ ICMP_ECHO requests at all, which unfortunately is quite common these days.
51
+ "uptest=query" causes pdnsd to send an empty query to remote name servers. Any
52
+ well-formed response (apart from SERVFAIL) within the timeout period will be
53
+ interpreted as a sign that the server is "up".
54
+
55
+ - Instead of specifying the IP addresses of the name servers that pdnsd should
56
+ query in a server section of the config file, you may also specify a
57
+ resolv.conf-style file. Preferably this should not be /etc/resolv.conf. If the
58
+ contents of the resolv.conf type file changes while pdnsd is running, you can
59
+ make pdnsd aware of the changes with the "pdnsd-ctl config" command, see
60
+ below. Example:
61
+
62
+ server {
63
+ label=myisp;
64
+ file=/etc/ppp/resolv.conf;
65
+ timeout=10;
66
+ }
67
+
68
+ - There is a new option for "server" sections in the config file:
69
+ root_server=on/off.
70
+ In case a server section contains only addresses of root servers, which
71
+ usually only give the name servers of top level domains in their reply,
72
+ setting root_server=on will enable certain optimizations. This involves using
73
+ cached information to reduce queries to the root servers, thus speeding up the
74
+ resolving of new names.
75
+
76
+ - New option for "rr" sections in the config file: reverse=on/off.
77
+ If you want a locally defined name to resolve to a numeric address and vice
78
+ versa, you can now achieve this by setting reverse=on before defining the A
79
+ record, making it unnecessary to define a separate PTR record for the reverse
80
+ resolving.
81
+ Example:
82
+
83
+ rr {
84
+ name = localhost;
85
+ reverse = on;
86
+ a = 127.0.0.1;
87
+ }
88
+
89
+ has the same effect as:
90
+
91
+ rr {
92
+ name = localhost;
93
+ a = 127.0.0.1;
94
+ }
95
+ rr {
96
+ name = 1.0.0.127.in-addr.arpa;
97
+ ptr = localhost;
98
+ }
40
99
41
100
- In rr sections it is now possible to specify a wildcard name, i.e. a name
42
101
starting with the label *. The * in a wildcard can match one or more labels in
@@ -56,23 +115,16 @@ For a short history about recent releases have a look at doc/html/index.html.
56
115
a = 192.168.1.10;
57
116
}
58
117
59
- - Instead of specifying the IP addresses of the name servers that pdnsd should
60
- query in a server section of the config file, you may also specify a
61
- resolv.conf type file. Preferably this should not be /etc/resolv.conf. If the
62
- contents of the resolv.conf type file changes while pdnsd is running, you can
63
- make pdnsd aware of the changes with the "pdnsd-ctl config" command, see
64
- below. Example:
65
-
66
- server {
67
- label=myisp;
68
- file=/etc/ppp/resolv.conf;
69
- timeout=10;
70
- }
118
+ - There is a slight backwards compatibility problem which involves the name= and
119
+ owner= options in rr sections. The new version does not allow you to place
120
+ owner= before name=. On the other hand, you may now freely mix the owner
121
+ option with the a,ptr,cname,mx and soa options and define as many records of
122
+ this type as you like (including zero).
71
123
72
124
- pdnsd-ctl has three new commands:
73
125
74
126
config: Reloads pdnsd's configuration file. This is more efficient than
75
- restarting pdnsd, and should not cause only noticable interuption in DNS
127
+ restarting pdnsd, and should not cause only noticeable interruption in DNS
76
128
service. However, some types of configuration changes cannot be put into
77
129
effect this way, and you will be prompted to restart pdnsd instead.
78
130
@@ -82,3 +134,17 @@ For a short history about recent releases have a look at doc/html/index.html.
82
134
83
135
dump: Prints information about all the names stored in the cached. This is
84
136
mainly useful for diagnostic purposes.
137
+
138
+ - There is now a pdnsd.conf(5) man page, describing pdnsd's configuration file.
139
+ The man page has been generated from the html documentation using a customized
140
+ Perl script.
141
+
142
+
143
+ The new features are described in greater detail in the manual doc/html/doc.html
144
+ or doc/txt/manual.txt.
145
+
146
+ Enjoy!
147
+
148
+ If you have any questions about my version of pdnsd, you can send these
149
+ to <
[email protected] >. Questions about the original (unmaintained) pdnsd
150
+ version should be sent to <
[email protected] > or <
[email protected] >.
0 commit comments