Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm not really sure what's going on, so bear with me, please
I installed Apache 2.0.53 today and set up a web site. When I view it on my LAN, everything runs perfectly fine.
If I try to access the site over the Internet, the site takes *forever* to load (20 seconds for an 8KB image).
I ran Ethereal and I think the slowdown is coming from failed DNS queries. Every time I get a connection on my web server port (80) the server sends a DNS query out and gets the response "DNS Standard query response, No such name."
I think the problem may lie in the address that my server is requesting the query on:
Queries->etho: type A, class inet.
I'm pretty sure that the server should be querying the connecting IP address and not "etho" (yes, that's an "oh" and not a "zero").
Any idea what the heck is causing my server to send out the query for "etho?" Is that even the probme? I have a dynamic IP address from my ISP, so I'm using dyndns.org. The server has a static IP address set up on the LAN. I have my ISP's DNS servers in my /etc/resolve.conf file. Apache isn't trying to do any hostname lookups (according to httpd.conf). I have no other network/Internet related problems.
Hm, not my special expertise, but I do know somewhat, and even sometimes somewhy (now if I can acquire somewho & somewhere I'll be getting places ), so I suggest you post two (for clarity) more messages here; one has all your server's network setup data, and the other has your Apache setup re networking. Subject to securtiy concerns, of course!
Might also need to tell us a little about your network & how the server cnonects to the World Outside...; Does the server have two nics, is it directly on your lan, and if no followed by yes, how does it get through to the W.O...
May need more, but this sounds like a good start.
Oh!, and which version of what OS does it run? It's hard to gave too many details here, as long as they relate to the basic O/S and the networking.
OK, I am very far from an expert in these matters but I am trying to up my karma by trying to help, so...
Is it possible that the problem is with your ISP? Possibly they are throttling traffic to port 80 just to frustrate dynamic IP home users like yourself. You might try running Apache on a high-numbered non-standard port nnnn and accessing yoursite.org:nnnn, see if that makes a difference.
I tried running my web server on a bunch of different ports, but all have the same problem. I've even tried going directly to my (WAN) IP address instead of going to my DYNDNS hostname.
The server is running on a slackware 10 box with kernel 2.4.26. The box has 1 NIC which is connected to the built in switch on my Netgear MR814 router.
Here are the relevant (ie, used) portions of my httpd.conf
Ok, like I said I am not an Apache expert, but such as I know, I didn't *notice* anything wrong.
I also do not (yet) know DYNDNS (probably should explore--), but I also have a router between the DSL-modem and the computerS, But haven't yet tried to run a server from inside here.
I do have some small suspicion, though, that the router might, and I said *might*, be where the extra dns-time is going. Once the dns has resolved, are there still delays in the established communication, or is this problem *only* while resolving via DYNDNS ?
(I *suspect* that DYNDNS will add some time by defiition.)
It still loads way to slow if I check it via the 'Net from home, but I can pull it up at work no problem and I've had friends pull it up with no problem. I'll just write this off as one of those development oddities.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.