Lme server requests

[Kevin Darcy]

William Grossman wrote:

> I am running redhat 8 with bind 9 and I keep getting lame server requests
> listed in my message log.  In looking for information about this on the
> internet most discussions say not to worry about this because it is a
> problem on a different DNS server.  I'm still concerned is for a few
> reasons.  First I have received a few calls concerning people not being able
> to send mail to our domain.  All of these emails are being returned with
> Subject: Warning: could not send message for past 4 hours
> ********
> host name lookup failure.
>
>      Secondly, the way that (in '****.COM) the .com is in caps seems
> different than the other posts concerning this.  Any help would be
> appreciated.
> I've included the Lame server messages below.
>
> Jan 27 11:15:37 ******** named[1825]: lame server resolving 'nystrom.com'
> (in 'nystrom.COM'?): 192.35.51.34#53
> Jan 27 11:20:53 ******** named[1825]: lame server resolving 'nystrom.com'
> (in 'nystrom.COM'?): 192.42.93.34#53
> Jan 27 13:55:06 ******** named[1825]: lame server resolving
> 'UnUSED.linkexpress.com.br.dawson.com' (in 'dawson.COM'?): 64.156.138.2#53
> Jan 27 14:39:13 ******** named[1825]: lame server resolving
> 'blackstone-ney.com' (in 'blackstone-ney.COM'?): 204.117.214.10#53
> Jan 27 14:47:57 ******** named[1825]: lame server resolving
> 'defer2.greatoffrs.com.dawson.com' (in 'dawson.COM'?): 64.156.138.2#53
> Jan 27 19:03:05 ******** named[1825]: lame server resolving
> 'johansoninsurance.com' (in 'johansoninsurance.COM'?): 204.117.214.10#53
> Jan 27 19:03:08 ******** named[1825]: lame server resolving
> 'luthern-jamestown.org.dawson.com' (in 'dawson.COM'?): 64.156.138.2#53
> Jan 27 19:03:09 ******** named[1825]: lame server resolving 'bilickilaw.com'
> (in 'bilickilaw.COM'?): 204.117.214.10#53
> Jan 27 19:03:18 ******** named[1825]: lame server resolving 'keybank.com'
> (in 'keybank.COM'?): 198.6.100.21#53
> Jan 27 19:03:26 ******** named[1825]: lame server resolving 'abdellalaw.com'
> (in 'abdellalaw.COM'?): 204.117.214.10#53
> Jan 27 19:38:33 ******** named[1825]: lame server resolving
> '211.251.15.216.in-addr.arpa' (in '251.15.216.in-addr.arpa'?):
> 216.15.129.3#53
> Jan 27 20:38:16 ******** named[1825]: lame server resolving
> '64.119.220.25.rev.iwaynetworks.com.dawson.com' (in 'dawson.COM'?):
> 64.156.138.2#53
> Jan 27 21:22:08 ******** named[1825]: lame server resolving
> 'rj1.smartnoc.net.dawson.com' (in 'dawson.COM'?): 64.156.138.2#53
> Jan 27 22:00:16 ******** named[1825]: lame server resolving 'mail1.opmr.com'
> (in 'opmr.COM'?): 205.205.53.2#53
> Jan 27 23:48:04 ******** named[1825]: lame server resolving
> '200-204-181-78.cebinet.com.br.dawson.com' (in 'dawson.COM'?):
> 64.156.138.2#53
> Jan 27 23:48:09 ******** named[1825]: lame server resolving
> 'ns-nom.pipex.net' (in 'pipex.NET'?): 137.39.1.3#53
> Jan 28 01:20:22 ******** named[1825]: lame server resolving
> 'om40.yourmailsoure.com.dawson.com' (in 'dawson.COM'?): 64.156.138.2#53
> Jan 28 03:34:41 ******** named[1825]: lame server resolving
> '64.119.220.25.rev.iwaynetworks.com.dawson.com' (in 'dawson.COM'?):
> 64.156.138.2#53
> Jan 28 04:34:31 ******** named[1825]: lame server resolving
> '162.117.37.64.in-addr.arpa' (in '117.37.64.in-addr.arpa'?): 216.15.129.3#53
> Jan 28 04:34:31 ******** named[1825]: lame server resolving
> 'yank.postlite.com' (in 'postlite.COM'?): 216.15.129.3#53
> Jan 28 07:27:41 ******** named[1825]: lame server resolving
> 'otbound5.lamailer.com.dawson.com' (in 'dawson.COM'?): 64.156.138.2#53
> Jan 28 08:00:03 ******** named[1825]: lame server resolving
> 'vacationbreak.net.dawson.com' (in 'dawson.COM'?): 64.156.138.2#53
> Jan 28 08:34:49 ******** named[1825]: lame server resolving
> '64.119.220.14.rev.iwaynetworks.com.dawson.com' (in 'dawson.COM'?):
> 64.156.138.2#53
> Jan 28 09:04:36 ******** named[1825]: lame server resolving
> 'defer1.rapid-e.net.dawson.com' (in 'dawson.COM'?): 64.156.138.2#53
> Jan 28 09:15:45 ******** named[1825]: lame server resolving
> 'localhost.localdomain.dawson.com' (in 'dawson.COM'?): 64.156.138.2#53
> Jan 28 09:29:23 ******** named[1825]: lame server resolving
> 'optimal-robotics.com' (in 'optimal-robotics.COM'?): 205.205.53.2#53
> Jan 28 11:41:46 ******** named[1825]: lame server resolving
> 'host70.wmi.xodiax.com.dawson.com' (in 'dawson.COM'?): 64.156.138.2#53
> Jan 28 12:25:09 ******** named[1825]: lame server resolving 'mail1.opmr.com'
> (in 'opmr.COM'?): 205.205.53.2#53

Well, it looks like the maintainers of dawson.com need a lesson regarding
trailing periods, and it looks like at least one of the delegated nameservers
for nystrom.com is persistently lame (at least, it was lame when I queried it),
but since you haven't told us what *your* domain is, how do you expect any help
figuring out why inbound email might be having problems?


- Kevin