[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-users] RE: A tad bit of a problem
- Subject: [cobalt-users] RE: A tad bit of a problem
- From: "B. Runge" <brunge@xxxxxxxxxxx>
- Date: Thu Nov 7 15:13:01 2002
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
To your responce...yes, no, no, yes...found it in /var/log/secure by a
typo that I had hosts.deny.
However....when it rains it pours! I am in one heck of a spot and this
makes night two. Allow me to get a bit more in depth. Users at the
indytel domain cannot pop for mail (POP before Relay is enabled) and
some time ago I altered q.popper in inetd.conf to allow for more
connects. (I do know that I have a secondary DNS issue,...that is a
whole nother story)
This all started when clients just were not able to "pop" for
mail,..usage was way high as I posted earlier....I installed IPCHAINS,
threw my script in, ran it, no problems. Then things were working for
about 4 hours then we had an issue with people not being able to send
mail.....and now quite sometime later neither are working. Tried
differnt combinations of starting/stopping/reloading services. I would
be quite surprised if this message reaches the list! So I upgraded BIND
to Solarspeeds "RaQ34-Solarspeed.net-Bind-8.3.3" on BOTH of my Raq's
(4i) I have a bad feeling that I have reached the point of no return
with this...this is also my other issue if I do a named -v I get the
BIND version on my primary server.....if I run the named -v on my
secondary server......guess what, no out put...not installed. Needless
to say, I re-loaded the *.pkg,..it installed.....In named.conf (on
secondary server) I have it pointing to primary just how it has always
in the past. When it moves my zones over to the secondary it my zones
look something like this sec.indytel.com.Blzd kind of crazy but is it a
easy fix and if anyone is curious the trailing charicters are not
consistant.....
So, in a nut shell I have a mail server thats acting up....a secondary
dns server that is not working (that by the way is hosting other
domains which they are having the same problems) and a few cans of
worms.
Thanks again....Bill