RE: [Nolug] DNS Server Problem with TCP

Hi Dustin.

What did you have in mind? :) I've looked at ps results and they are pretty
much the same, but they don't match exactly. Nothing caught my eye.

Netstat shows that named is connected to port 53 for both TCP and UDP. It will
be interesting to see what it say after it fails next time.

John

   John Souvestre - Southern Star & Integrated Data Systems - (504) 355-0609

> -----Original Message-----
> From: owner-nolug@stoney.redfishnetworks.com [mailto:owner-
> nolug@stoney.redfishnetworks.com] On Behalf Of Dustin Puryear
> Sent: Saturday, October 25, 2008 2:04 PM
> To: nolug@nolug.org
> Subject: Re: [Nolug] DNS Server Problem with TCP
>
> I meant "are there any network daemons running on the two boxes or maybe
> just one of them"?
>
> Not the contents of /etc/services.
>
> I like how you think though! ;)
>
> --
> Dustin Puryear
> President and Sr. Consultant
> Puryear Information Technology, LLC
> 225-706-8414 x112
> http://www.puryear-it.com
>
> Author, "Best Practices for Managing Linux and UNIX Servers"
> http://www.puryear-it.com/pubs/linux-unix-best-practices/
>
>
> John Souvestre wrote:
> > Hi Dustin.
> >
> > Ns1 is set up as master and ns2 is a slave. The bind config is the same,
> > otherwise.
> >
> > The /etc/services file is the same on both systems. It includes
> >
> > domain 53/tcp # name-domain server
> > domain 53/udp
> >
> > Thanks,
> >
> > John
> >
> > John Souvestre - Southern Star & Integrated Data Systems - (504) 355-
> 0609
> >
> > > -----Original Message-----
> > > From: owner-nolug@stoney.redfishnetworks.com [mailto:owner-
> > > nolug@stoney.redfishnetworks.com] On Behalf Of Dustin Puryear
> > > Sent: Saturday, October 25, 2008 10:40 AM
> > > To: nolug@nolug.org
> > > Subject: Re: [Nolug] DNS Server Problem with TCP
> > >
> > > Also, you say "setup almost identically". What running network services
> > > are on the two DNS servers?
> > >
> > > --
> > > Dustin Puryear
> > > President and Sr. Consultant
> > > Puryear Information Technology, LLC
> > > 225-706-8414 x112
> > > http://www.puryear-it.com
> > >
> > > Author, "Best Practices for Managing Linux and UNIX Servers"
> > > http://www.puryear-it.com/pubs/linux-unix-best-practices/
> > >
> > >
> > > Dustin Puryear wrote:
> > > > The exact same version of RH? And what is the kernel version on both?
> > > > And the version of bind on both?
> > > >
> > > > --
> > > > Dustin Puryear
> > > > President and Sr. Consultant
> > > > Puryear Information Technology, LLC
> > > > 225-706-8414 x112
> > > > http://www.puryear-it.com
> > > >
> > > > Author, "Best Practices for Managing Linux and UNIX Servers"
> > > > http://www.puryear-it.com/pubs/linux-unix-best-practices/
> > > >
> > > >
> > > > John Souvestre wrote:
> > > >> Hi all.
> > > >>
> > > >> I'm having a strange problem with one of our DNS servers
> (ns1.idsno.net).
> > > Our
> > > >> ns2.idsno.net server is set up almost identically and it has no
> problem.
> > > >>
> > > >> The problem is with the ability to do DNS TCP transfers. What makes
> this
> > > really
> > > >> strange is that TCP works just fine when the box is rebooted. But a
> few
> > > days
> > > >> later, it stops responding to TCP. I've seen this happen a half
> dozen
> > > times.
> > > >>
> > > >> We're running RH. As far as I can tell, IPTables is not being used
> on the
> > > box.
> > > >>
> > > >> I don't see anything interesting in /var/log/messages.
> > > >>
> > > >> The box is behind a PIX but so is the other one. Port 53 UDP and TCP
> are
> > > both
> > > >> enabled.
> > > >>
> > > >> Does anyone have any ideas?
> > > >>
> > > >> Thanks!
> > > >>
> > > >> John
> > > >>
> > > >> John Souvestre - Southern Star & Integrated Data Systems - (504)
> 355-
> > > 0609
> > > >>
> > > >>
> > > >> ___________________
> > > >> Nolug mailing list
> > > >> nolug@nolug.org
> > > >>
> > > >> --
> > > >> This message was scanned by ESVA and is believed to be clean.
> > > >> Click here to report this message as spam.
> > > >> http://esva.puryear-it.com/cgi-bin/learn-msg.cgi?id=
> > > >>
> > > >>
> > > > ___________________
> > > > Nolug mailing list
> > > > nolug@nolug.org
> > > >
> > > > --
> > > > This message was scanned by ESVA and is believed to be clean.
> > > > Click here to report this message as spam.
> > > > http://esva.puryear-it.com/cgi-bin/learn-msg.cgi?id=
> > > >
> > > >
> > > ___________________
> > > Nolug mailing list
> > > nolug@nolug.org
> >
> > ___________________
> > Nolug mailing list
> > nolug@nolug.org
> >
> > --
> > This message was scanned by ESVA and is believed to be clean.
> > Click here to report this message as spam.
> > http://esva.puryear-it.com/cgi-bin/learn-msg.cgi?id=
> >
> >
> ___________________
> Nolug mailing list
> nolug@nolug.org

___________________
Nolug mailing list
nolug@nolug.org
Received on 10/25/08