Error's in our /var/log/messages file

We recently started receiving named errors in our logs. Can soneone tell us what the problem might be and how to fix it or if there is nothing to worry about that these are normal. We just have not seen them before. There are a lot of them.

The errors are:

named[77] recvfrom: No route to host
named[77] accept: Connection reset by peer

Thanks in advance.
Bob Ross

bross073097Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

rbrCommented:
named is the Internet domain name server. In general you don't need it. What did you change before the error occured. Pls post your /etc/named.boot
0
bross073097Author Commented:
Yes we need it. We haven't added anything for a few weeks. We just started noticing the errors, so we are not sure when they atarted. All the domains work.

Thanks
Bob Ross

;
; named boot file
;
; The first part of this file is maintained by configdns.  If you
want
; to make additions, add them after the `DO NOT DELETE' line below
and
; they will be retained across configdns changes.
;
;type           domain                  source file or host
;----------------------------------------------------------------------------
directory       /etc/namedb
;
cache           .                               root.cache
;
primary         kingman.com                     kingman.db
primary         166.63.209.in-addr.arpa         reverse.db
primary         116.210.209.in-addr.arpa        reverse2.db
primary         0.0.127.in-addr.arpa            localhost.rev
primary         mohavecounty.net                mohave.db
primary         negz.com                        negz.db
primary         tacos.com                       tacos.db
primary         kingman.net                     kingnet.db
primary         venturawest.com                 venturawest.db
primary         nasaracing.com                  nasacom.db
primary         sywss.com                       sywss.db
primary         10acres.com                     10acres.db
primary         route66web.com                  route66web.db
primary         dunton1.com                     dunton1.db
primary         desertvarmits.com               desertvarmits.db
primary         ourhdtrike.com                  ourhdtrike.db
;primary                surftheusa.net
surftheusa.db
primary         surftheusa.com                  surftheusa-com.db
primary         aero-cam.com                    aero-cam.db
primary         wizardesign.com                 wizardesign.db
primary         fortrock.com                    fortrock.db
primary         c-aclub.com                     c-aclub.db
primary         funtruck.com                    funtruck.db
;
; DO NOT DELETE THIS LINE -- place local changes below here
;

0
jetxCommented:
please post your /etc/namedb file setup

thanks
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

gunny051499Commented:
i guess, this is very unlikely a configuration problem deriving from your local config. most probably your handling data/getting requests, where there is a problem with the secondary nameserver or the like.

you could upgrade to a newer version of bind (the latest is 8.2.2 to be found at http://www.isc.org/products/BIND).

these newer versions allow you to set up more complex debugging situations. this surely will help in cases like this one.
0
bross073097Author Commented:
I tried to upgrade but it had a few fits so we pulled it back out. we will be upgrading soon to a newer server once all the settings are finished. We were just a bit concerned about the errors because we had not seen them before and didn't want to bring down the service.

Would you say it should be fine so we can sleep better?.

Thanks
Bob
0
gunny051499Commented:
have a look at www.cert.org. older versions of bind (like your 4.9.x) are quite vulnerable to attacks.

since i'm not realy paranoic, that's not the only thing why i suggest you an upgrade. i would suggest you to do so because it's faster than the older one and offers a whole bunch of possibilities to customize your logging. and that should be what you are realy looking for at the moment.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ihardingCommented:
I agree with gunny.  Just looking at the security issue, that should be enough to upgrade.  Regarding the errors, check your forwarders.  If they seem to be OK, yes, sleep at night.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux

From novice to tech pro — start learning today.