• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

win2k+apache+dns2go

TheOmegaCode

Platinum Member
There seem to be a few posts on dns2go, but none really helpfull...
Ok, here's the deal. I'm running Apache 1.3 on Win2k sp 1 with DNS2GO 2.6.0.0 installed as a service.
It was recently brought to my attention, that my url omega-online.myip.org wouldn't work with the www prefix. So I went into DNS2GO and forwarded the www prefix to port 8080. I went into my httpd.conf file and changed the listen to 8080 and BindAddress *. Now my problems have swapped, you can now hit my site with a www. but not without!
Now jimmyhaha and I have been racking our brains to why this is happening. He is running dns2go, Apache, and win2k also. He has dsl, but no router. He did the same things to dns2go and apache that I did, but he can't get the www prefix to work.
Why? Anyone know?

PS I am running PPPoE DSL which is handled by my Linksys router. And I have ports 80 and 8080 forwarded to my private ip.
 
Wouldn't you have to set apache to listen to both port 80 and 8080? However, since you're using a commercial DDNS, they probably onlt allow one port to handle web requests. I use d2g.com (which I think is the same as yours) and the client only has an option for one port for http forwarding.

TWU
 
This is just a guess, but I'm think that they're using "www.yourdomain.com" to point to "yourdomain.com:8080". Take a look at this article that I wrote that uses this trick for zoneedit.com. How to run your webserver on a different port number other than port 80

However, if you webserver software allows you to use host headers or virtual servers, you can get around this very easily. Use "www2.yourdomain.com" to point to your IP address. Then use both "www.yourdomain.com" and "yourdomain.com" to point to "www2.yourdomain.com:8080". Here is the other article I wrote on how to do thi: How to run your webserver on a different port number other than port 80 using host headers

Again, just is just a hunch of mine.
 
Back
Top