All of our public IPs are reverse mapped. The initial connection to the site is fast. The delay happens when data starts comming back. A way to visualize this problem is using a browser. You hit "Go" and the target site immediately returns text, but like a low-bandwidth or overloaded site, graphics trickle back. This problem is not limited to a single site ... it's all of them. And isn't limited to a single router, I have two different production evironments setup with different loadbalancer/firewall combos. What they both have in common is the RedHat router doing simple forwarding. One in each environments.
-Ken >> Any suggestions on where to go with this? >If I have a tcp delay, I always check the dns config. In many cases, there is >no reverse dns lookup of the ip-address so the other hosts waits for the >dns-timeout before allowing the connection. So, has your ip-address a >reverse dns entry? >Stef _______________________________________________ LARTC mailing list / [EMAIL PROTECTED] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
