The djbdns-1.04-fwdzone.patch included in djbdns-1.05-r8 changes the way forwarding is done by dnscache: 1. environment variable FORWARDONLY (env/FORWARDONLY) is rendered useless 2. forwarding is only used for zones which file under root/servers/ have the sticky bit set (chmod +t ...) Reproducible: Always Steps to Reproduce: creating a new configuration using dnscache-setup Actual Results: When creating a forwarding only cache, dnscache-setup creates env/FORWARDONLY file and creates root/servers/@ _WITHOUT_ sticky bit set. Expected Results: 1. dnscache-setup MUST NOT create env/FORWARDONLY under any circumstance 2. dnscache-setup MUST set sticky bit on root/servers/@ IF it is configuring for a forwarding only DNS cache Portage 2.0.49-r15 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.6.0-test9-mm5) ================================================================= System uname: 2.6.0-test9-mm5 i686 AMD Duron(tm) Processor Gentoo Base System version 1.4.3.12 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=athlon -s -O3 -pipe -fomit-frame-pointer -ffast-math -ftracer" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/share/config /usr/kde/2/share/config /usr/kde/3/share/config /var/qmail/control /var/qmail/alias" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-march=athlon -s -O3 -pipe -fomit-frame-pointer -ffast-math -ftracer" DISTDIR="/usr/portage/distfiles" FEATURES="sandbox ccache autoaddcvs fixpackages" GENTOO_MIRRORS="http://ftp.snt.utwente.nl/pub/os/linux/gentoo http://gentoo.mirror.sdv.fr http://gentoo.inode.at/ http://ftp.lug.ro/gentoo http://ftp.gentoo.skynet.be/pub/gentoo/ http://sunsite.cnlab-switch.ch/ftp/mirror/gentoo/ http://trumpetti.atm.tut.fi/gentoo/ http://ftp.caliu.info/pub/gentoo/ http://gentoo.tiscali.nl/gentoo/ http://linux.rz.ruhr-uni-bochum.de/download/gentoo-mirror/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.de.gentoo.org/gentoo-portage" USE="x86 crypt cups foomaticdb gif imlib jpeg libwww ncurses nls png spell truetype xml2 zlib gdbm berkdb slang readline ruby postgres pam ssl 3dnow acpi acpi4linux apache2 clamav cscope curl ext-png ext-zlib fam gd gd-external icc icc-pgo imagemagick imlib2 jikes lcms maildir menu mmx mpi nocardbus nptl offensive parse-clocks passfile pic ruby18 samba threads type1 usb xml -oss -apm -arts -avi -encode -gpm -gtk -gtk2 -kde -gnome -libg++ -mad -mikmod -motif -mpeg -oggvorbis -opengl -pdflib -qt -quicktime -sdl -svga -X -xmms -xv -tcltk -tcpd -perl -python -ldap"
proposed fix: *** dnscache-setup 2003-09-22 12:39:54.000000000 +0200 --- dnscache-setup.fix 2003-11-27 10:57:30.942873080 +0100 *************** *** 127,133 **** if [ "$myforward" != "" ] then echo $myforward > ${mypath}/${mycachedir}/root/servers/\@ ! echo -n "1" > ${mypath}/${mycachedir}/env/FORWARDONLY read -p "enter forward-to IP [hit Enter to stop]> " myforward while [ "$myforward" != "" ] --- 127,133 ---- if [ "$myforward" != "" ] then echo $myforward > ${mypath}/${mycachedir}/root/servers/\@ ! chmod +t ${mypath}/${mycachedir}/root/servers/\@ read -p "enter forward-to IP [hit Enter to stop]> " myforward while [ "$myforward" != "" ]
In my opinion that patch should not be applied -- changing the behaviour of a program in a non-backwards-compatible fashion means that people's existing experience can not be used (I just wasted over an hour), and means existing on-line information can no longer be used. At the very least the ebuild should print a warning that this isn't really djbdns anymore, and explicitly mention that FORWARDONLY no longer works.
Added net-dns/djbdns-1.05-r12
