To close this thread and for the sake of those who might see it later. 15261 was released which addresses a bug that incorrectly set dns server values if NONE responded. (this points to a problem with my dns servers which have yet to be determined)
On Wed, Sep 16, 2015 at 9:59 AM, K Post <nntp.p...@gmail.com> wrote: > Thanks Greyhat for chiming in and sorry for so many emails all! > > I'm using our 3 internal DNS servers. The ports are wide open between the > servers. There isn't a firewall issue. Nothing's changed on the DNS > servers or the firewall (I run them too). > > Notes (to summarize my many posts - sorry about that): > > 1) Things work just fine for a while after starting ASSP > > 2) After a couple of hours, the problem returns. RWL and RBL "bad file" > warnings, A and MX records don't resolve. > > 3) Using 3 local and fast dns servers. using persistent connection or > not, doesn't matter. I have DNSServerLimit set to 2 > > 4) *This was never a problem with 15167. As soon as we went to 15225, > the problem started*. > > 5) *After the problem shows its head*, *Infostats shows "0" for used dns > servers* instead of showing the 2 servers ASSP has selected to use. Once > I restart ASSP, the used DNS Servers line goes back to showing 2 of my 3 > servers as expected. > > Windows 2012 R2, fully patched. > > > > On Wed, Sep 16, 2015 at 9:50 AM, Grayhat <gray...@gmx.net> wrote: > >> :: On Wed, 16 Sep 2015 09:04:55 -0400 >> :: <CALhpkAkaSHBDm0zkjTpX0YNxp5izZzA1yYr=m-uap+ahz-v...@mail.gmail.com> >> :: K Post <nntp.p...@gmail.com> wrote: >> >> > DNSReuseSocket being unticked didn't help. Another 4 hours after >> > restarting and the RWL/RBL errors are back. >> >> first of all, are you using your own DNS resolvers or are you relying >> on some external (public, ISP, ...) DNS resolver ? In the latter case, >> keep in mind that, while using public resolvers for (say) surfing or >> the like, when it comes to mail routing and DNS list checking you >> *must* use your own recursive (no forwarding to external DNS !) >> full resolver; also, and since we're at DNS, ensure that your firewall >> allows both UDP *and* TCP traffic toward port 53 of whatever external >> DNS host (this is also needed if you run an internal resolver) *AND* >> ensure that UDP packets above 512 bytes (used by EDNS) won't be dropped >> by some dumb firewall rule >> >> >> >> ------------------------------------------------------------------------------ >> Monitor Your Dynamic Infrastructure at Any Scale With Datadog! >> Get real-time metrics from all of your servers, apps and tools >> in one place. >> SourceForge users - Click here to start your Free Trial of Datadog now! >> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 >> _______________________________________________ >> Assp-test mailing list >> Assp-test@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/assp-test >> > > ------------------------------------------------------------------------------ _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
