<div dir="ltr"><span style="font-family:arial,sans-serif;font-size:13px">Will - The sole source of my zone data will be the nsd.conf file (as was the case previously). I will not be "importing" zones through "nsd-control. However, I still want to take advantage of patterns to define a common set of keywords and values in my nsd.conf zone definitions, thus avoiding lengthy repetitions. The slides (from 16-OCT-2013) show the use of patterns as "macro expansions" applied to "zone:" names within the nsd.conf file. That's what I want to do... and I've followed the exact examples shown in the slides. Again, the "patterns" work as long as I don't use substitutions (%s, %x, %y, %z, etc). Hence, I believe something is quirky with the patterns.</span><div style="font-family:arial,sans-serif;font-size:13px">
<br></div><div style="font-family:arial,sans-serif;font-size:13px">It would be great if you could check, using the example I provided (or I can zip up my working set).</div><div style="font-family:arial,sans-serif;font-size:13px">
<br></div><div style="font-family:arial,sans-serif;font-size:13px">Thanks!</div><div style="font-family:arial,sans-serif;font-size:13px">Lew Payne</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Mar 9, 2014 at 12:55 PM, Will Pressly <span dir="ltr"><<a href="mailto:will@edgecast.com" target="_blank">will@edgecast.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">I am not around a machine where I can poke at your substitution problem, but, from what you are saying about not wanting to do addzone, have you looked at reconfig? Nsd-control reconfig will find diffs in sequential revisions in your nsd.conf file and just apply changes to the running state of the daemon. Eg: it will detect zones that are in a newer rev of the nsd.conf (that were absent in an earlier revision) and add them automatically. This works with deletes as well. </p>
<p dir="ltr">This way your nsd.conf file is the sole source of config input for your daemon -- not nsd.conf and the zones.list file. This way you can just explicitly add the zone name and path to the zones section of your nsd.conf file without having to use patterns.</p>
<p dir="ltr">I will try to look at your pattern substitution problem later -- I have a hunch, but do not want to suggest it here for fear of looking like a fool :) That said, I assume you looked at your logs and checked for chroot presence/relativization, right? Also, you might just try reconfig as I suspect that will better satisfy your work flow requirements.</p>
<p dir="ltr">Regards,<br>
Will</p>
<div class="gmail_quote"><div><div class="h5">On Mar 9, 2014 11:25 AM, "Lew Payne" <<a href="mailto:lew.payne@gmail.com" target="_blank">lew.payne@gmail.com</a>> wrote:<br type="attribution"></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div class="h5">
<div dir="ltr">I'm upgrading to nsd v4.0.1 (from a six year old release). I've crafted a new nsd.conf by hand, and would like to take advantage of the "pattern" feature. I've read the man page, looked at the sample conf file, and even poured through the 16-OCT-2013 slide presentation. My nsd.conf conforms to the required standard, yet there seems to be a failure when using substitution patterns.<div>
<br></div><div>This fails...</div><div><br></div><div>pattern:</div><div>....name: "solozones"</div><div>....zonefile: "zones/db.%s"</div><div>....provide-xfr: 1.2.3.4 NOKEY</div><div><br></div><div>zone:</div>
<div>....name: "<a href="http://whatever.com" target="_blank">whatever.com</a>"</div><div>....include-pattern: "solozones"</div><div><br></div><div>producing a "could not find pattern solozones" error. I've also tried using "zones/db.%y.%z" as well as "zones/db.\%s" as the zonefile pattern, to no avail. The problem seems to be in substitution (it would help if it showed the substitution/expansion in the error output)... because the following works:</div>
<div><br></div><div>pattern:</div><div>....name: "solozones"</div><div>....zonefile: "zones/<a href="http://db.whatever.com" target="_blank">db.whatever.com</a>"</div><div>....provide-xfr: 1.2.3.4 NOKEY</div>
<div><br>
</div><div>Can someone please tell me what I'm doing wrong, and how to work around this problem? I want to hard-code (lock down) the zones into nsd.conf, rather than use nsd-control addzone (for PCI and HIPAA reasons).</div>
<div><br></div><div>I hope someone brighter than me can spot why this isn't working.</div><div><br></div></div>
<br></div></div>_______________________________________________<br>
nsd-users mailing list<br>
nsd-users@NLnetLabs.nl<br>
<a href="http://open.nlnetlabs.nl/mailman/listinfo/nsd-users" target="_blank">http://open.nlnetlabs.nl/mailman/listinfo/nsd-users</a><br>
<br></blockquote></div>
</blockquote></div><br></div>