In the load tests, we see scads of DNS lookup warning messages that don't seem to be causing any problems.
These DNS messages are a side effect of having split the lookup into multiple threads. Look ups of _sip._tcp.rr.xxx and _sip._udp.rr.xxx (SRV and then A) records are successful. Look ups of rr.xxx (A) and _sip._tls.rr.xxx (SRV) records are unsuccessful. Questions: - Should the load test be configured with A records for rr.xxx names? - Does it make sense to change the log level of these messages? At the least, they should be dropped to INFO. Although even at DEBUG level they would still show up (and clog) the load test logs. - Does it make sense to remove these messages altogether? They could be replaced by a WARNING in the "caller" that is logged only if no records are returned. Details: ---- lookups on thread 1 succeed ---- '_sip._udp.rr.firstsoak.qantom.int', type = 33 (SRV)" 'firstsoak.qantom.int', type = 1 (A)" 'secondsoak.qantom.int', type = 1 (A)" ---- lookups on thread 2 succeed ---- '_sip._tcp.rr.firstsoak.qantom.int', type = 33 (SRV)" 'firstsoak.qantom.int', type = 1 (A)" 'secondsoak.qantom.int', type = 1 (A)" ---- lookups on thread 3 fail ---- '_sip._tls.rr.firstsoak.qantom.int', type = 33 (SRV)" ---- lookups on thread 4 fail ---- 'rr.firstsoak.qantom.int', type = 1 (A)" Scads of outbound messages do these lookups and each one logs two warning messages (on threads 3 & 4). -Kathy _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
