Were you running stock bind, bind-chroot, caching-nameserver packages, or had you modified them in some way? Which versions?

Phil Leinhauser wrote:
I just installed the djbdns package and ran a qmailctl doqueue and it looked like they were all delivered now. I had about 10 stuck.

Like I say, I'm not running something as old as the "long DNS name error" problem so it looks like something snuck back in and broke it again.

Thanks,
Phil


 > Phil Leinhauser wrote:
 >> I might not have the bleeding edge version of QMT but it isn't more
 >> than 3months since my last update.
 >>
 >> I'm seeing in Google a lot of problems with long names. The sure
 >> seems to be to run djbdbs. I'm not because I already have 2 inhouse
 >> caching DNS servers but I guess I'll try that.
 >>
 >> Thanks
 >>
 >
 > The patch would have been added a couple years ago and included the
 > long-hostnames, unless it accidentally got removed at some point.
 > I'll take a look into the spec file and patches today to make sure that
 > the patches were not removed at some point or forgotten.
 >
 >
> ---------------------------------------------------------------------------------
 > Managed Qmailtoaster servers are now available
 > Visit http://qmailtoaster.com/QMTManaged.html to order yours today!
 >
 > Qmailtoaster is sponsored by Vickers Consulting Group
 > (www.vickersconsulting.com)
 >
 > Please visit qmailtoaster.com for the latest news, updates, and
 > packages.
 >
 >
 > To unsubscribe, e-mail: [email protected]
 > For additional commands, e-mail: [email protected]
 >
 >
 >


--
-Eric 'shubes'


---------------------------------------------------------------------------------
                Managed Qmailtoaster servers are now available
      Visit http://qmailtoaster.com/QMTManaged.html to order yours today!

Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)

    Please visit qmailtoaster.com for the latest news, updates, and packages.


         To unsubscribe, e-mail: [email protected]
        For additional commands, e-mail: [email protected]


Reply via email to