| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Most important changes:
- full Y2038 compliance
- full support for DNS over TCP
- some changes in the zone format.
|
|
changelog:
maradns-1.0.39:
* Backport of memory leak fix to 1.0 branch of MaraDNS
(2006.07.24)
maradns-1.0.38:
Backport of MaraDNS 1.2.09 Microsoft.com fix to legacy 1.0 branch
(2006.06.16)
maradns-1.0.37:
This is an update for the 1.0 legacy branch of MaraDNS
* Removed all example mararc files which allow any IP on the
internet to perform recursive queries (these can be used for
denial of service attacks)
(2006.04.07)
maradns-1.0.36:
This is a bugfix release for the legacy 1.0 branch of MaraDNS.
* A backport of the 2-line patch recently posted to the mailing
list concerning incorrect dangling CNAME warnings
(2005.12.31)
maradns-1.0.35:
* Backport of 1.1.x fix of csv1 example in documentation
* Backport of 1.1.x fix of MINFO RR description
* Backport of 1.1.x security fix.
(2005.11.20)
maradns-1.0.34:
* Hotfix: recursion works again
* Regression procedure added.
(2005.10.26)
maradns-1.0.33:
* Fixed occassional crash that happens while reading zone files at
MaraDNS startup.
* Fixed occassional compression error which shows up in MaraDNS
logs.
* Update man page to point out some unimplemented features will be
in 1.2
(2005.10.24)
maradns-1.0.32:
Hotfix: RR rotation now works again.
(2005.08.08)
maradns-1.0.31:
Two patches by Albert Lee that improve Maras stability.
(2005.08.07)
maradns-1.0.30:
* Warn the user when they have dangling CNAME records
* Fix bug with MX records with preferences > 255 in getzone tool
(2005.06.30)
maradns-1.0.29:
This release improves how MaraDNS'recursive resolver parses
packets so that Mara can interoperate better with some stub
resolvers that dont bother looking past the header of a DNS
packet.
(2005.05.13)
|
|
Too many changes to list, see CHANGELOG within the source tarball.
This update was prompted by an issue with random number generator,
see the following url for details:
http://www.maradns.org/download/patches/maradns-1.0.26-rekey_rng
|
|
the RCD_SCRIPTS rc.d script(s) to the PLIST.
This GENERATE_PLIST idea is part of Greg A. Woods'
PR #22954.
This helps when the RC_SCRIPTS are installed to
a different ${RCD_SCRIPTS_EXAMPLEDIR}. (Later,
the default RCD_SCRIPTS_EXAMPLEDIR will be changed
to be more clear that they are the examples.)
These patches also remove the etc/rc.d/ scripts from PLISTs
(of packages that use RCD_SCRIPTS). (This also removes
now unused references from openssh* makefiles. Note that
qmail package has not been changed yet.)
I have been doing automatic PLIST registration for RC_SCRIPTS
for over a year. Not all of these packages have been tested,
but many have been tested and used.
Somethings maybe to do:
- a few packages still manually install the rc.d scripts to
hard-coded etc/rc.d. These need to be fixed.
- maybe remove from mk/${OPSYS}.pkg.dist mtree specifications too.
|
|
Changes:
Cleaned up and fixed a bug in the MaraDNS startup
script. Now, the only prorcesses that will be killed
will be bona fide MaraDNS processes.
Closes PR pkg/22963.
|
|
Package provided by pancake <pancake@phreaker.net> via pkgsrc-wip.
MaraDNS is a package that implements the Domain Name Service (DNS), an
essential internet service. MaraDNS is intended for environments where a DNS
server must be secure and where the server must use the absolute minimum
number of resources possible. MaraDNS was created in response to issues
people had with the DNS servers available in early 2001; and has the
following design goals:
Security-aware programming. A DNS server needs to be secure. I have a number
of security features in the code, including:
1. The code uses a special string library which is resistant to buffer
overflows.
2. The code, if started as root, mandates running as an unpriviledged user
in a chroot() jail.
Open-Source. The 1.0 release of the DNS server is public-domain code;
the 1.2 release will be released under a very liberal BSD-style license.
Simplicity. This DNS server has the minimum number of features needed to
correctly act as an authoritative and/or recursive name server.
|
