Hi, Not strictly a North American problem but I was wondering if anyone had seen this behaviour. We currently have two blocks of IP address space, 195.224.206/24 and 193.193.186/23. Everything works fine from 195.224.206 but from 193.193.186 there are often problems accessing web servers - either they don't respond for ages then are suddenly OK, send just the headers in response to a GET request then stop or just plain don't respond to HTTP queries at all. This appears to happen mostly with Netscape servers although I only have a few examples so far so I'm not sure. (www.real.com, www.cisco.com, www.etrade.com, www.bt.com) We also have two lines out of the building, although I've tried routing in various ways and the problem seems to follow the IP address rather than the outbound line. (IP addresses are, for the moment, tied to the line until we get BGP on the line currently serving 195.224.206/24 however I can't see how this could be an inbound line problem.) I believe this to be a DNS problem as I can't see anything else that could be causing a problem - it doesn't seem to matter what web browser is used (IE, Netscape, Lynx or even telnet) or if a web cache (Squid) is used or not. There are three reverse DNS servers in totally different locations (One on our site, one on the UK Joint Academic Network and one in Switzerland) so I don't think part of the net being unreacable from somewhere can be the problem. The only *POSSIBLE* explanation I can come up with is that the IPv6 AAAA entries for 193.in-addr.arpa are confusing some nameservers and causing this problem. I'm really grasping at straws though - does anyone have even the slightest idea what cound be going on? (Even off-list wild-guess suggestions would be appreciated.) Thanks. --- Ryan O'Connell - http://complicity.olf.co.uk:8080/ - <nemesis@eh.org> How do you sleep? How do you last the night and keep the dogs at bay? How do you feel when you close your eyes, and try and drift away? Does it feel any better now? Does it mean anymore When the angel of death comes knock, knocking, And banging at your door?
I also had one to ti.com bounce. D. At 04:31 PM 8/17/99 +0100, Ryan O`Connell wrote:
Hi,
Not strictly a North American problem but I was wondering if anyone had seen this behaviour.
We currently have two blocks of IP address space, 195.224.206/24 and 193.193.186/23. Everything works fine from 195.224.206 but from 193.193.186 there are often problems accessing web servers - either they don't respond for ages then are suddenly OK, send just the headers in response to a GET request then stop or just plain don't respond to HTTP queries at all. This appears to happen mostly with Netscape servers although I only have a few examples so far so I'm not sure. (www.real.com, www.cisco.com, www.etrade.com, www.bt.com)
We also have two lines out of the building, although I've tried routing in various ways and the problem seems to follow the IP address rather than the outbound line. (IP addresses are, for the moment, tied to the line until we get BGP on the line currently serving 195.224.206/24 however I can't see how this could be an inbound line problem.)
I believe this to be a DNS problem as I can't see anything else that could be causing a problem - it doesn't seem to matter what web browser is used (IE, Netscape, Lynx or even telnet) or if a web cache (Squid) is used or not. There are three reverse DNS servers in totally different locations (One on our site, one on the UK Joint Academic Network and one in Switzerland) so I don't think part of the net being unreacable from somewhere can be the problem.
The only *POSSIBLE* explanation I can come up with is that the IPv6 AAAA entries for 193.in-addr.arpa are confusing some nameservers and causing this problem. I'm really grasping at straws though - does anyone have even the slightest idea what cound be going on? (Even off-list wild-guess suggestions would be appreciated.)
Thanks.
--- Ryan O'Connell - http://complicity.olf.co.uk:8080/ - <nemesis@eh.org>
How do you sleep? How do you last the night and keep the dogs at bay? How do you feel when you close your eyes, and try and drift away? Does it feel any better now? Does it mean anymore When the angel of death comes knock, knocking, And banging at your door?
One of my clients in the Caribbean is seeing similar behavior. Some websites are reachable, others not. It's not clear if this is DNS or some sort of core routing instability. Your message said you see everything fine from one netblock you have, but not from another. This sounds like someone's messing with advertisements and perhaps made a mess. It also correlates with data I've seen from other clients in other locales. -- ----------------------------------------------------------------- Daniel Senie dts@senie.com Amaranth Networks Inc. http://www.amaranthnetworks.com
Problem appears to be MTU related - if I reduce the ethernet MTU to 1400 on the web cache everything runs fine. (Cheers to Rush at GX Networks for suggesting this) I've yet to find a common router though. Upon further investigation mail appeared to be OK because failed mail is going to our backup MX which reachs us via a different route. --- Ryan O'Connell - <roconnell@olf.co.uk> "It was a gift from Hobbes, we're alike in a lot of ways" Seconds out. Do you wanna know what this fight's about? Commerciality over art can't win out. I'm alike in a lot of ways, I'm alike in a lot of ways.
I have a potential need to get traffic into Mexico for multi-media. It's pretty regular high-band-width stuff. If anyone can help, please send reply directly to me. I'm on NANOG, but only monitor it indirectly.
participants (5)
-
Daniel Senie -
ddiviniaï¼ broadcast.com -
Roeland M.J. Meyer -
Ryan O`Connell -
Ryan O`Connell