220
220
32. I am transferring a zone from another
221
221
server, but the NS records are these strange "synth-ip" records.
222
223
33. Where is the root.hints file?
223
225
34. Are there any plans to use autoconf to build
225
228
35. How do I change the compiler or compile-time flags
226
229
with MaraDNS\(aq build process?
227
231
36. Will you make a package for the particular Linux
228
232
distribution I am using?
234
37. I am using the native Windows port of MaraDNS,
235
and some features are not working.
237
38. MaraDNS isn\(aqt starting up
239
39. You make a lot of releases of MaraDNS; at our
240
ISP/IT department, updating software is non-trivial.
614
632
\fB20. Is MaraDNS portable?\fR
617
MaraDNS will only compile on FreeBSD, Mac OS X, Cygwin, Linux, and
618
partially on MinGW32 systems. If you are interested in porting MaraDNS
619
to another system, please let me know.
635
MaraDNS is developed on a CentOS 3 and Windows XP dual boot laptop.
636
MaraDNS may compile or run on other systems--there are official MaraDNS
637
ports for Debian/Ubuntu, Slackware, FreeBSD, and NetBSD. Note that
639
needs a system with a robust threading library, which some systems do
622
644
\fB21. Can I use MaraDNS in Windows?\fR
1087
1109
is needed in the Linux compile or MaraDNS will have problems with
1090
<h2>Will you make a package for the particular Linux
1091
distribution I am using?
1114
\fBWill you make a package for the particular Linux distribution I am
1092
1117
No. OK, let me qualify that: I won\(aqt do it unless you pay
1093
1118
me enough money.
1095
1120
There are MaraDNS packages for a number of different distributions of
1096
Linux and other operating systems. On there MaraDNS site, there is
1121
Linux and other operating systems. On the MaraDNS site, there is
1097
1122
a MaraDNS package for CentOS/Red Hat Enterprise Linux available. There
1098
1123
is also usually an up-to-date Slackware package available. In addition,
1099
1124
there is a Debian package in the Debian packages collection, a FreeBSD
1116
1141
are out of date. Please make sure, that if you get a third-party
1118
from the internet, the package is for either MaraDNS 1.0.39, MaraDNS
1119
1.2.12.05, or MaraDNS 1.3.03. Older versions of MaraDNS are not
1143
from the internet, the package is for either MaraDNS 1.0.40, MaraDNS
1144
1.2.12.05, or MaraDNS 1.3.04. Older versions of MaraDNS are not
1148
\fBI am using the native Windows port of MaraDNS, and some features are
1151
Since Windows 32 does not have some features that *NIX OSes have, the
1153
Windows port does not have all of the features of the *NIX version of
1154
MaraDNS. In particular, the following features are disabled:
1157
ipv6 (this is actually a mingw32, not a Windows deficiency)
1160
The chroot_dir mararc variable
1163
The maradns_gid and maradns_uid mararc variables
1166
The maxprocs mararc variable
1169
The synth_soa_serial variable can not have a value of 2
1171
If any of the above features are desired, try compiling MaraDNS using
1172
Cygwin. Note that the Cygwin port of MaraDNS does not have ipv6
1174
and that while chroot_dir works in Cygwin, it does not have
1175
the security that the *NIX chroot() call has.
1178
\fBMaraDNS isn\(aqt starting up\fR
1180
This is usually caused by a syntax error in one\(aqs mararc file, or by
1181
another MaraDNS process already running. To see what is happening, look
1182
at your system log (/var/log/messages in Centos 3) to see what
1183
errors MaraDNS reports. If you do not know how to look at a system
1184
log, you can also invoke MaraDNS from the command line as root; any
1186
will be visible when starting MaraDNS.
1189
\fBYou make a lot of releases of MaraDNS; at our ISP/IT department,
1190
updating software is non-trivial.\fR
1192
The number of releases seen in the changelog
1193
is not an accurate reflection of how often someone using a stable
1194
branch of MaraDNS will need to update.
1196
There were only three updates to the 1.0 legacy branch in 2006. The 1.2
1198
was updated frequently in the first half of 2006, since I felt MaraDNS
1200
needed some features that didn\(aqt make it in to 1.2.00. During this
1202
cycle, there was always a stable bugfix-only branch of MaraDNS.
1204
In August of 2006, I stabilized the 1.2 branch and only three updates
1205
have been done since then. Unless there is a critical bug, I only
1207
the 1.2 branch approximately once every three months or so.
1209
I go to a great deal of effort to make sure MaraDNS releases are as
1210
painless to update as possible. I ensure configuration file format
1211
compatibility, even between major versions of MaraDNS. With the
1213
of configuration file parser bugfixes, MaraDNS 1.0 configuration files
1214
are compatible with MaraDNS 1.2 and 1.3.
1216
It is impossible to make code that is bug-free or without security
1217
problems. This is especially true with code that runs on the public
1218
internet.<sup><font size=-2>1</font></sup> Code has to be updated from
1219
time to time. What I do in order to minimize the disruption caused by
1221
update is to always have a stable bugfix-only branch of MaraDNS (right
1225
bugfix-only branches), and to, as much as possible, evenly
1226
space out the bugfix updates.
1228
Footnote 1: Even DJB\(aqs code has security problems. Both Qmail and
1230
have known security problems, and need to be patched before put on a
1124
1236
In the unusual case of having a csv2 zone file with Macintosh-style
added
removed
doc/en/man/maradns.8
