Re: Help understanding lame server error

2008-11-20 Thread bsfinkel
>20-Nov-2008 00:36:38.470 lame-servers: info: lame server resolving >'szi.szi.sv.gov.yu' (in 'szi.sv.gov.yu'?): 195.178.32.2#53 This message means that your DNS server sent a query for szi.szi.sv.gov.yu and through recursion was directed to the nameserver at IP address 195.178.32.2

Re: Help understanding lame server error

2008-11-20 Thread Leonard Mills
Scott wrote at about Thursday, November 20, 2008 12:45:26 AM: ... >> 19-Nov-2008 15:36:34.955 lame-servers: info: lame server resolving >> '127.52.195.166.in-addr.arpa' (in '52.195.166.in-addr.arpa'?): >> 209.183.48.20#53 > However, I thought the last part, was an IP and a port, telling me, tha

Re: Help understanding lame server error

2008-11-20 Thread Dan
Have you tried looking up the client IP from another line in the logs from the same time? -Original Message- From: Scott Haneda <[EMAIL PROTECTED]> Date: Thu, 20 Nov 2008 00:45:26 To: BIND Users Mailing List Subject: Re: Help understanding lame server error On Nov 19, 2008, a

Re: Help understanding lame server error

2008-11-20 Thread Mark Andrews
In message <[EMAIL PROTECTED]>, Scott Haneda writ es: > On Nov 19, 2008, at 6:19 PM, Kevin Darcy wrote: > > Here is another example, I think not a reverse lookup for sure: > 20-Nov-2008 00:36:38.470 lame-servers: info: lame server resolving > 'szi.szi.sv.gov.yu' (in 'szi.sv.gov.yu'?): 195.178.3

Re: Help understanding lame server error

2008-11-20 Thread Scott Haneda
On Nov 19, 2008, at 6:19 PM, Kevin Darcy wrote: Scott Haneda wrote: I have a good deal if lame server errors in my logs, which I am not entirely understanding. 19-Nov-2008 15:36:34.657 lame-servers: info: lame server resolving '170.73.234.209.in-addr.arpa' (in '73.234.209.in-addr.arpa'?):

Re: Help understanding lame server error

2008-11-19 Thread Kevin Darcy
Scott Haneda wrote: I have a good deal if lame server errors in my logs, which I am not entirely understanding. 19-Nov-2008 15:36:34.657 lame-servers: info: lame server resolving '170.73.234.209.in-addr.arpa' (in '73.234.209.in-addr.arpa'?): 209.234.64.192#53 73.234.209.in-addr.arpa has been

Re: Help understanding lame server error

2008-11-19 Thread Leonard Mills
They are most likely reverse lookups from your MTA. Borked reverse zones are quite common. Len - Original Message From: Scott Haneda <[EMAIL PROTECTED]> To: BIND Users Mailing List Sent: Wednesday, November 19, 2008 3:57:15 PM Subject: Help understanding lame server error I have a

Re: Help understanding lame server error

2008-11-19 Thread Mark Andrews
In message <[EMAIL PROTECTED]>, Scott Haneda write s: > I have a good deal if lame server errors in my logs, which I am not > entirely understanding. > > 19-Nov-2008 15:36:34.657 lame-servers: info: lame server resolving > '170.73.234.209.in-addr.arpa' (in '73.234.209.in-addr.arpa'?): > 209