On Tue, Oct 21, 2008 at 12:49:06PM +0000, martin f krafft wrote: > Package: nsd3 > Version: 3.0.7-2 > Severity: wishlist > > It seems like nsd3 does not deal with % sign in zones.
hmm, I don't know who uses %, but it's not documented in bind. http://linux.thomason.homeip.net/CIS2556/DNS/Bv9ARM.ch06.html#AEN3536 > > E.g., instead of a zone definition for my.local.zone of > > % IN NS ns.% > ns.% IN A 1.2.3.4 > > I have to specify: > > my.local.zone. IN NS ns.my.local.zone. > ns.my.local.zone. IN A 1.2.3.4 YOu can use: $ORIGIN my.local.zone. @ IN NS ns ns IN A 1.2.3.4 Note that "$ORIGIN @" may even work (straight @ are supposed to be replaced with the root-anchored zone name your zone file is supposed to implement). > It would be nice if % were replaced by the root-anchored zone name, > which would also allow reuse of zone files for similar domains. In the worst case scenario you can do that using $ORIGIN in a small header file that would not be shared (and probably easy to generate) plus $INCLUDE. [some lurking in the source later] Yeah it seems that $ORIGIN @ do what you mean, at least zparser.y allows it it seems. @ will be replaced with the zone name you put in your nsd.conf. Though you cannot use DOMAIN.@ it won't work, you can only use straight @'s. FWIW I don't think NSD will ever implement what you want given [0] [0] http://www.nlnetlabs.nl/projects/nsd/documentation.html -- ·O· Pierre Habouzit ··O [EMAIL PROTECTED] OOO http://www.madism.org
pgpHLyiTd5Jmj.pgp
Description: PGP signature
