LARTC - Apr 2002 - RE: long delays with NNTP after switching T1 to other ser vcie provider

Or maybe some kind of DNS issue is going on.  

- Greg


-----Original Message-----
From: David Koski [mailto:david@KosmosIsland.com]
Sent: Saturday, April 13, 2002 10:31 AM
To: LARTC
Subject: [LARTC] long delays with NNTP after switching T1 to other
servcie provider


After moving a Linux server serving as a wireless gateway/router to another
ISP,
I noticed a problem with NNTP.  When attempting to communicate NNTP through
the
Linux server, there are long delays that often result in timeouts.  For
example,
when using the newsreader pan, I get the following errors in the log file,
in
reverse chronological order:

Connect Failure
NNTP handshake failed: Error reading from socket.
Handshake failed: Error reading from socket.
NNTP handshake failed: Error reading from socket.
Timed out waiting to read from the server.


The Linux server is fed with a T1 from a different source.  Before changing
over, there was no problem with NNTP.  The only other difference that would
seem
to matter is the reconfiguration of the server.  I only took some services
off
line (qmail for example) and reconfigured the routing.  All other traffic
through the server works well, with the exception of dhcp which I
haven''t
resolved yet.

I suspect a QoS control issue from upstream.  Is it possible that NNTP
requests
are sitting in a queue somewhere waiting for a the "right" time to
dequeue?
If
so, would there be something I could do with the TOS that might help?  Or Am
I
on the wrong track?

TIA,
David Koski
david@KosmosIsland.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

Reverse DNS does not work.  Could that be it?

David

On Sat, 13 Apr 2002 12:51:35 -0500
Greg Scott <GregScott@InfraSupportEtc.com> wrote:
> Or maybe some kind of DNS issue is going on.  
> 
> - Greg
> 
> 
> -----Original Message-----
> From: David Koski [mailto:david@KosmosIsland.com]
> Sent: Saturday, April 13, 2002 10:31 AM
> To: LARTC
> Subject: [LARTC] long delays with NNTP after switching T1 to other
> servcie provider
> 
> 
> After moving a Linux server serving as a wireless gateway/router to another
> ISP,
> I noticed a problem with NNTP.  When attempting to communicate NNTP through
> the
> Linux server, there are long delays that often result in timeouts.  For
> example,
> when using the newsreader pan, I get the following errors in the log file,
> in
> reverse chronological order:
> 
> Connect Failure
> NNTP handshake failed: Error reading from socket.
> Handshake failed: Error reading from socket.
> NNTP handshake failed: Error reading from socket.
> Timed out waiting to read from the server.
> 
> 
> The Linux server is fed with a T1 from a different source.  Before changing
> over, there was no problem with NNTP.  The only other difference that would
> seem
> to matter is the reconfiguration of the server.  I only took some services
> off
> line (qmail for example) and reconfigured the routing.  All other traffic
> through the server works well, with the exception of dhcp which I
haven''t
> resolved yet.
> 
> I suspect a QoS control issue from upstream.  Is it possible that NNTP
> requests
> are sitting in a queue somewhere waiting for a the "right" time
to dequeue?
> If
> so, would there be something I could do with the TOS that might help?  Or
Am
> I
> on the wrong track?
> 
> TIA,
> David Koski
> david@KosmosIsland.com
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

I''ll bet that''s the right direction.  I''ve seen other
services,
especially ftp, where the ftp server tries a reverse DNS and 
gets mad or times out if it can''t resolve it.  One of the dumbest 
engineering decisions I''ve ever seen!  I''ll bet that nntp
service
you''re trying to get at does the same thing.  But the deal is,
the nntp server might be having reverse DNS problems resolving
your IP address to a name, not you resolving its address to a name.
So **you**  having reverse DNS problems might not be the key.  

Remember, I am just speculating here.

- Greg



-----Original Message-----
From: David Koski [mailto:david@KosmosIsland.com]
Sent: Sunday, April 14, 2002 12:37 AM
To: Greg Scott; LARTC
Subject: Re: [LARTC] long delays with NNTP after switching T1 to other
ser vcie provider


Reverse DNS does not work.  Could that be it?

David

On Sat, 13 Apr 2002 12:51:35 -0500
Greg Scott <GregScott@InfraSupportEtc.com> wrote:
> Or maybe some kind of DNS issue is going on.  
> 
> - Greg
> 
> 
> -----Original Message-----
> From: David Koski [mailto:david@KosmosIsland.com]
> Sent: Saturday, April 13, 2002 10:31 AM
> To: LARTC
> Subject: [LARTC] long delays with NNTP after switching T1 to other
> servcie provider
> 
> 
> After moving a Linux server serving as a wireless gateway/router to
another
> ISP,
> I noticed a problem with NNTP.  When attempting to communicate NNTP
through
> the
> Linux server, there are long delays that often result in timeouts.  For
> example,
> when using the newsreader pan, I get the following errors in the log file,
> in
> reverse chronological order:
> 
> Connect Failure
> NNTP handshake failed: Error reading from socket.
> Handshake failed: Error reading from socket.
> NNTP handshake failed: Error reading from socket.
> Timed out waiting to read from the server.
> 
> 
> The Linux server is fed with a T1 from a different source.  Before
changing
> over, there was no problem with NNTP.  The only other difference that
would
> seem
> to matter is the reconfiguration of the server.  I only took some services
> off
> line (qmail for example) and reconfigured the routing.  All other traffic
> through the server works well, with the exception of dhcp which I
haven''t
> resolved yet.
> 
> I suspect a QoS control issue from upstream.  Is it possible that NNTP
> requests
> are sitting in a queue somewhere waiting for a the "right" time
to
dequeue?
> If
> so, would there be something I could do with the TOS that might help?  Or
Am
> I
> on the wrong track?
> 
> TIA,
> David Koski
> david@KosmosIsland.com
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

To clarify, doing a reverse DNS on me outside of the local network does not
work.  Are we on the same page?  I think that is causing a problem receiving
some mail also.

Thanks,
David

On Sun, 14 Apr 2002 01:29:44 -0500
Greg Scott <GregScott@InfraSupportEtc.com> wrote:
> I''ll bet that''s the right direction.  I''ve seen
other services,
> especially ftp, where the ftp server tries a reverse DNS and 
> gets mad or times out if it can''t resolve it.  One of the dumbest 
> engineering decisions I''ve ever seen!  I''ll bet that nntp
service
> you''re trying to get at does the same thing.  But the deal is,
> the nntp server might be having reverse DNS problems resolving
> your IP address to a name, not you resolving its address to a name.
> So **you**  having reverse DNS problems might not be the key.  
> 
> Remember, I am just speculating here.
> 
> - Greg
> 
> 
> 
> -----Original Message-----
> From: David Koski [mailto:david@KosmosIsland.com]
> Sent: Sunday, April 14, 2002 12:37 AM
> To: Greg Scott; LARTC
> Subject: Re: [LARTC] long delays with NNTP after switching T1 to other
> ser vcie provider
> 
> 
> Reverse DNS does not work.  Could that be it?
> 
> David
> 
> On Sat, 13 Apr 2002 12:51:35 -0500
> Greg Scott <GregScott@InfraSupportEtc.com> wrote:
> 
> > Or maybe some kind of DNS issue is going on.  
> > 
> > - Greg
> > 
> > 
> > -----Original Message-----
> > From: David Koski [mailto:david@KosmosIsland.com]
> > Sent: Saturday, April 13, 2002 10:31 AM
> > To: LARTC
> > Subject: [LARTC] long delays with NNTP after switching T1 to other
> > servcie provider
> > 
> > 
> > After moving a Linux server serving as a wireless gateway/router to
> another
> > ISP,
> > I noticed a problem with NNTP.  When attempting to communicate NNTP
> through
> > the
> > Linux server, there are long delays that often result in timeouts. 
For
> > example,
> > when using the newsreader pan, I get the following errors in the log
file,
> > in
> > reverse chronological order:
> > 
> > Connect Failure
> > NNTP handshake failed: Error reading from socket.
> > Handshake failed: Error reading from socket.
> > NNTP handshake failed: Error reading from socket.
> > Timed out waiting to read from the server.
> > 
> > 
> > The Linux server is fed with a T1 from a different source.  Before
> changing
> > over, there was no problem with NNTP.  The only other difference that
> would
> > seem
> > to matter is the reconfiguration of the server.  I only took some
services
> > off
> > line (qmail for example) and reconfigured the routing.  All other
traffic
> > through the server works well, with the exception of dhcp which I
haven''t
> > resolved yet.
> > 
> > I suspect a QoS control issue from upstream.  Is it possible that NNTP
> > requests
> > are sitting in a queue somewhere waiting for a the "right"
time to
> dequeue?
> > If
> > so, would there be something I could do with the TOS that might help? 
Or
> Am
> > I
> > on the wrong track?
> > 
> > TIA,
> > David Koski
> > david@KosmosIsland.com
> > _______________________________________________
> > LARTC mailing list / LARTC@mailman.ds9a.nl
> > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

On Sun, Apr 14, 2002 at 12:37:14AM -0700, David Koski
wrote:
> To clarify, doing a reverse DNS on me outside of the local network does not
> work.  Are we on the same page?  I think that is causing a problem
receiving
> some mail also.
Might very well be. I sould advise contacting the administrator of your NNTP
server to see if s/he has reverse lookups configured. Also contact your T1
supplier to get reverse DNS working.

If you don''t have a nameserver <SHAMELESS PLUG> go to
http://www.powerdns.com </SHAMELESS PLUG>.

Regards,

bert hubert

-- 
http://www.PowerDNS.com          Versatile DNS Software & Services
http://www.tk                              the dot in .tk
http://lartc.org           Linux Advanced Routing & Traffic Control HOWTO