Re: [cobalt-users] Questions abot log

[flash22@xxxxxxx]

On Thu, 30 Aug 2001, Brett Bunch wrote:

> Can someone tell me what all of these bad referrals, lame servers, and
> findns errors are! I am new to the linux world.
> Also, for some reason, everything will be happy on my e-mail & web
> server, then the e-mail will just drop off of the world for a while, web
> server is still on, eventually e-mail comes back. What's up with that?

ok, line by line....

> Aug 30 20:24:52 dns1 named[356]: master zone "guntersvilleboe.com" (IN)
> loaded (serial 2001072510)

etc etc, normal, good, doing what it is supposed to...

> "guntersvilletechnologyinvitational.com" (IN) loaded (serial 2001072510)

[egads! people type that in ?]

> Aug 30 20:24:53 dns1 named[357]: Ready to answer queries.

done starting up...

> Aug 30 20:24:53 dns1 named[357]: sysquery: findns error (NXDOMAIN) on
> dns1.guntersvilleboe.com?

bad bad bad, you have a domain name referring to a nameserver that should
be YOU , but there isn't any such domain record, you are missing a NS
record for the domain....finfns means 'find nameserver record for domain'

You are being warned your domain isn't consistant....it's broken, tho it
may happen to seem to work...

nslookup gripes:
server dns2.guntersvilleboe.com
*** Can't find address for server dns2.guntersvilleboe.com: Non-existent
host/domain



> Aug 30 20:25:05 dns1 last message repeated 6 times
> Aug 30 20:25:19 dns1 named[357]: bad referral (. !< mi.com) from
> [64.226.246.54].53

random junk, other peoples lame servers, just like yours;)

> Aug 30 20:25:57 dns1 named[357]: Lame server on 'BLACKHOLE.EP.NET' (in
> 'EP.net'?): [198.32.2.10].53 'DOT.EP.NET'

You may have something pointed at 127.0.0.x for reverse here..hard to tell
'blackhole' dns addresses are sometimes used for safeguarding errors


> Aug 30 20:27:27 dns1 named[357]: Lame server on
> '178.115.53.64.in-addr.arpa' (in '115.53.64.in-addr.arpa'?):
> [206.74.254.2].53 'DNS4.INFOAVE.NET'

More junk, other peoples errors that youi can do nothing about...

> query(178.115.53.64.in-addr.arpa) All possible A RR's lame

This is just a variation on lame server, it means the you tried every
possible domain/nameserver to look up an address, and they were all
lame...

> Aug 30 20:28:29 dns1 proftpd[849]: dns1.guntersvilleboe.com
> (24-216-49-88.hsacorp.net[24.216.49.88]) - FTP session closed. 

Just you ..;)

As for email dropping off the face of the earth, if you are sending via
the ISP i think you are , i'm not surprised, we have had similar
problems with them...and serious connectivity issues....sigh

Your having broken NS records won't help inbound email btw, you have a
50/50 chance of resolver errors when the remote machine looks up your
domain name, not all clients are smart enough to retry, some just have a
fit and give up...

gsh