YADIFA is a lightweight authoritative Name Server with DNSSEC capabilities.
Developed by the passionate people behind the .eu top-level domain, YADIFA has
been built from scratch to face today?s DNS challenges, with no compromise on
security, speed and stability, to offer a better and safer Internet experience.
YADIFA has a simple configuration syntax and can handle more queries per second
while maintaining one of the lowest memory footprints in the industry. YADIFA
also has one of the fastest zone file load times ever recorded on a name
server.
YADIFA was developed on FreeBSD and a GNU/Linux. It works on OSX and will be
soon ported to other Unix flavours like OpenBSD and Solaris. A Microsoft
Windows version is also on the cards.
===> The following configuration options are available for yadifa-3.0.2:
CTRL=off: Remote control
DDNS=on: Dynamic DNS support (DDNS)
DNSSECTOOLS=on: DNSSEC module
DOCS=on: Build and/or install documentation
ECDSA=on: Elliptic Curve (ECDSA)
EXAMPLES=on: Build and/or install examples
KEYGEN=on: Keygen tool
LARGEFILE=on: Support for largefiles
MASTER=on: Use as primary nameserver
NSID=on: Name Server Identifier Option
RRL=on: Response Rate Limiting
RRSIG=on: RRSIG management
TCL=off: Tcl scripting language support
ZONESIGN=on: Zonesign tool
===> Use 'make config' to modify these settings
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
dns/yadifa: fix build on GCC architectures
In file included from /usr/include/openssl/bn.h:20,
from /usr/include/openssl/engine.h:18,
from
/wrkdirs/usr/ports/dns/yadifa/work/yadifa-2.4.1-9916/lib/dnscore/include/dnscore/digest.h:53,
from
/wrkdirs/usr/ports/dns/yadifa/work/yadifa-2.4.1-9916/lib/dnscore/include/dnscore/dnskey.h:50,
from
/wrkdirs/usr/ports/dns/yadifa/work/yadifa-2.4.1-9916/lib/dnscore/include/dnscore/tsig.h:48,
from
/wrkdirs/usr/ports/dns/yadifa/work/yadifa-2.4.1-9916/lib/dnscore/include/dnscore/message.h:64,
from src/acl.c:57:
/usr/include/openssl/crypto.h:322: error: expected ')' before '__attribute__'
/usr/include/openssl/crypto.h:322: error: expected identifier or '(' before ')'
token
MFH: 2021Q1
dns/yadifa: update to 2.4.1
* YADIFA 2.4.1-public:
- Fixes an issue in dnscore where a DNS TCP query would not return the real
DNS error code.
- Fixes an issue that could happen when a network model isn't supported.
- Fixes the propagation of sendmmsg/recvmmsg function availability detection.
- Fixes an issue where yadifad would issue a warning when a key with
algorithm > 7 is used with an NSEC zone.
- Fixes an issue that will occur on a chrooted environment where a
managed-path would be used incorrectly.
- Fixes CNAME answers not following the aliases chain.
- Fixes CNAME recursion not returning the same answer as named in NXDOMAIN
cases (reported by https://github.com/SivaKesava1, see
https://github.com/yadifa/yadifa/issues/11)
(Only the first 15 lines of the commit message are shown above )
Ensure that there is only one variable definition per each object, as
the C (and C++) standards mandated for years and compilers started to
enforce as of recently (Clang 11, GCC 10).
Reported by: pkg-fallout
Bump PORTREVISION for ports depending on the canonical version of GCC
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.
PR: 231590
Bump PORTREVISION for ports depending on the canonical version of GCC
in the ports tree (via Mk/bsd.default-versions.mk and lang/gcc) which
has now moved from GCC 6 to GCC 7 by default.
This includes ports
- featuring USE_GCC=yes or USE_GCC=any,
- featuring USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and those
- with USES=compiler specifying one of openmp, nestedfct, c11, c++0x,
c++11-lib, c++11-lang, c++14-lang, c++17-lang, or gcc-c++11-lib.
PR: 222542
Bump PORTREVISION for ports depending on the canonical version of GCC
(via Mk/bsd.default-versions.mk and lang/gcc) which has moved from
GCC 5.4 to GCC 6.4 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c++11-lib, c++11-lang,
c++14-lang, c++0x, c11, or gcc-c++11-lib.
PR: 219275
Bump PORTREVISIONs for ports depending on the canonical version of GCC and
lang/gcc which have moved from GCC 4.9.4 to GCC 5.4 (at least under some
circumstances such as versions of FreeBSD or platforms).
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using using Mk/bsd.octave.mk which in turn has USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c++11-lib, c++14-lang,
c++11-lang, c++0x, c11, or gcc-c++11-lib.
PR: 216707
Bump PORTREVISIONS for ports depending on the canonical version of GCC and
lang/gcc which have moved from GCC 4.8.5 to GCC 4.9.4 (at least under some
circumstances such as versions of FreeBSD or platforms).
In particular that is ports with USE_GCC=yes, USE_GCC=any, or one of
gcc-c++11-lib, openmp, nestedfct, c++11-lib as well as c++14-lang,
c++11-lang, c++0x, c11 requested via USES=compiler.
- Fix plist to have proper 'rmdir DIR' ordering.
Pkgng will not detect the directory otherwise. This was due to
incorrectly advise in the check-stagedir.sh script, fixed in
r351587
With hat: portmgr
