>I'm testing DNSServerLimit is set to ONE.

Set this value at least to TWO.

Thomas





Von:    K Post <nntp.p...@gmail.com>
An:     ASSP development mailing list <assp-test@lists.sourceforge.net>
Datum:  14.06.2015 16:11
Betreff:        [Assp-test] NO_NAME_SERVER_GIVEN



We've got 3 local (relatively fast, very stable) windows dns servers.

In an effort to reduce network traffic internally and externally by
limiting DNS queries where reasonable, I'm testing DNSServerLimit is set 
to
ONE.  I feel like this will generally be sufficient, if for some reason a
DNS server is temporarily down, assp should be smart enough to use another
(right?) - I don't think this will be a problem in our environment.  I'm
taking the weekend to confirm that suspicion.

The 3 dns servers are listed in DNSServers in ASSP, use local DNS is
unchecked, DNSResponseLog is checked, and DebugSPF is checked (for testing
purposes).

Things >>appear<< to be working fine, but when I applied these changes, I
got this in the logs:

Jun-14-15 09:57:42 Info: DNSResolverSend: caller: 
Net::DNS::Resolver::Base,
468, sourceforge.net
Jun-14-15 09:57:42 Info: Name Server x.x.x.53: ResponseTime = 2 ms for
sourceforge.net
Jun-14-15 09:57:42 Info: DNSResolverSend: caller: 
Net::DNS::Resolver::Base,
468, sourceforge.net
Jun-14-15 09:57:42 Info: Name Server x.x.x.52: ResponseTime = 2 ms for
sourceforge.net
Jun-14-15 09:57:42 Info: DNSResolverSend: caller: 
Net::DNS::Resolver::Base,
468, sourceforge.net
Jun-14-15 09:57:42 Info: Name Server x.x.x.51: ResponseTime = 1 ms for
sourceforge.net
*Jun-14-15 09:57:42 Info: DNSresolverTimeS timed out*
*Jun-14-15 09:57:42 Info: NO_NAME_SERVER_GIVEN - closing existing DNS
sockets*
*Jun-14-15 09:57:42 Info: DNSresolverTimeS timed out*
*Jun-14-15 09:57:42 Info: NO_NAME_SERVER_GIVEN - closing existing DNS
sockets*
*Jun-14-15 09:57:42 Info: DNSresolverTimeS timed out*
*Jun-14-15 09:57:42 Info: NO_NAME_SERVER_GIVEN - closing existing DNS
sockets*

So ASSP is testing all 3 servers as it should to decide which one should 
be
used until the next test or failure.  But what does "DNSresolverTimeS 
timed
out" mean?
Why does it say NO_NAME_SERVER_GIVEN?


And I am now seeing:
Jun-14-15 10:01:06 Info: DNSresolverTimeS timed out
Jun-14-15 10:01:06 Info: NO_NAME_SERVER_GIVEN - closing existing DNS 
sockets
frequently.
------------------------------------------------------------------------------
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test






DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally 
privileged and protected in law and are intended solely for the use of the 

individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no 
known virus in this email!
*******************************************************

------------------------------------------------------------------------------
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test

Reply via email to