problems with dns resolving

[Lora Ganeva]

I have a lot of records in my /var/adm/syslog/syslog.log :lame server resolving....
Does this mean that my dns performance is poor.

[Niraj Kumar Verma]

Hi,

Can you post few lines here ?

Niraj

[Lora Ganeva]

Nov 19 13:50:09 saturn named[10734]: lame server resolving 'images.rambler.bg' (
in 'bg'?): 192.16.202.11#53
Nov 19 13:50:09 saturn named[10734]: lame server resolving 'images.rambler.bg' (
in 'bg'?): 137.39.1.3#53
Nov 19 13:50:09 saturn named[10734]: lame server resolving 'counter.rambler.bg'
(in 'bg'?): 137.39.1.3#53
Nov 19 14:05:25 saturn named[10734]: lame server resolving 'ns1.btc-net.bg' (in
'bg'?): 192.16.202.11#53
Nov 19 14:18:18 saturn named[10734]: lame server resolving 'rd1.hitbox.com' (in
'hitbox.COM'?): 64.154.81.20#53
Nov 19 14:25:06 saturn named[10734]: lame server resolving 'www.wetterauer.bg' (
in 'bg'?): 192.16.202.11#53
Nov 19 14:25:06 saturn named[10734]: lame server resolving 'www.wetterauer.bg' (
in 'bg'?): 137.39.1.3#53
Nov 19 14:25:06 saturn named[10734]: lame server resolving 'www.wetterauer.bg' (
in 'wetterauer.bg'?): 193.254.29.10#53

[George_Dodds · Accepted solution]

Here's a couple of link with info on this

http://www.burningvoid.com/iaq/lame-server.html

http://www.menandmice.com/online_docs_and_faq/glossary/glossarytoc.htm?lame.server.htm

Cheers

George

[Berlene Herren]

lame server is one that is advertised to have authoritative information about a domain, but does not.

It should not affect your dns performance.

Berlene

[Ravi_8]

Hi,

lame:server

doesn't mean poor performance. you can ignore this error.

[Lora Ganeva]

thank You very much..but I have another problem with the sam mashine-large number of dropped tcp connections due to full queues.
Any help would be greatly appreciated.
Here is the output of netstat -p tcp command
saturn:/ >netstat -p tcp
tcp:
22733659 packets sent
16744831 data packets (993545771 bytes)
349198 data packets (390591212 bytes) retransmitted
6093893 ack-only packets (1123026 delayed)
0 URG only packets
3295 window probe packets
105343 window update packets
2144332 control packets
27097541 packets received
9641704 acks (for 993316673 bytes)
2269779 duplicate acks
0 acks for unsent data
14399129 packets (3446192415 bytes) received in-sequence
3549 completely duplicate packets (4430626 bytes)
14762 packets with some dup, data (20200449 bytes duped)
1242616 out of order packets (1597336419 bytes)
946 packets (1744714 bytes) of data after window
17 window probes
14251379 window update packets
11100 packets received after close
2052 segments discarded for bad checksum
0 bad TCP segments dropped due to state change
592233 connection requests
443565 connection accepts
1035798 connections established (including accepts)
1165274 connections closed (including 129476 drops)
127923 embryonic connections dropped
8438673 segments updated rtt (of 8438673 attempts)
289144 retransmit timeouts
33391 connections dropped by rexmit timeout
3295 persist timeouts
25061 keepalive timeouts
22797 keepalive probes sent
41 connections dropped by keepalive
142743 connect requests dropped due to full queue
20 connect requests dropped due to no listener

[George_Dodds]

your best bet is to start a new thread for the new problem.

Cheers

George