On 6/20/12 7:35 AM, Eric Shubert wrote:
On 06/19/2012 05:51 PM, Casey James Price wrote:
Just to make sure I've got this right, you are saying to change line 56
in qtp-get-pkg-list to what you have listed above, right? I tried this
and then ran qtp-ami-up2date again and am still getting an error.
Oops. Also delete the line containing:
djbdns \
just a little before that. I did that in the script already, but
forgot to tell you. If that doesn't do it, try grabbing the script
from the qtp site. You can see it at
http://qtp.qmailtoaster.com/trac/browser/bin/qtp-get-pkg-list and
download it using the "Original Format" link at the bottom of that page.
So, needless to say, I'm hoping to stick with djbdns for a bit at least
on some of these boxes. Q2 and my "vcluster1" box (yes, the name does
in-fact say it all...its built following the guidelines from Jake's QMT
ISP Array video series) both run QMT and bind as the resolver if I
remember correctly, but my old Solaris boxes and their latest
re-incarnations on the Linux side of things are using tinydns to provide
DNS for the customers. Anyways, sorry to ramble on...these last two
paragraphs or so don't really have much relevance in this whole issue,
but I just wanted to explain where I was coming from.
Thanks, nice to know. I wouldn't necessarily change from djbdns to
something else if it's being used for authoritative dns (ie you have
zones coded with it). Then again, I wouldn't put an authoritative DNS
server on a QMT host either, but that's just me. I do however
recommend using pdns-recursor (powerdns) or caching-nameserver (bind9)
on a QMT host.
Thanks Eric. That did the trick.
Casey James Price
Smile Global Technical Support
Submit or check trouble tickets http://billing.smileglobal.com
www.smileglobal.com <http://www.smileglobal.com>
Follow us on Twitter <https://twitter.com/#%21/SmileInternet>
Find us on Facebook <https://www.facebook.com/smileglobal>
