meadowsr
join:2009-11-05
Monument, CO
|  Qwest DSL modem recommendation, *with a twist*
I live in southern CO, and have Qwest DSL. I have the ActionTec GT701-WG modem, and am more-or-less happy with it. Up until recently, however.
Up until recently, I was hosting a number of servers on my home machine, including DNS, postfix, and apache, and all was working well. Well, "well" in that my workarounds for a couple issues worked well. The main issue was that I was not able to talk to my servers using my (static) public IP address, only the local LAN address. To combat having to use raw IP addresses, say for things like my mail account, I implemented BIND "views" so that requests from the LAN addresses got one answer (the local IP address) and all other requests got another (the static public IP). Worked flawlessly that way for years.
Well, I've recently had necessity to move some of my hosting to Dreamhost, which required me passing DNS functionality to them. However, there is no equivalent to BIND "views" that I can take advantage of now. But, I still host some services (like apache) on my home machine, including some virtual domains and subdomains.
Some of these virtual domains are now inaccessible to me on my LAN, because I cannot access them using the public IP address. I'm told by those more in the know than I that this is because "I suspect your router doesn't do that forwarding from inside your NAT", where "that forwarding" is the port forwarding I've set up on the ActionTec so that, for example, port 80 is routed to my WWW server machine.
I can get to my main web site by virtue of the fact that I've created an alias to "www.mydomain.com" that resolves to the local address. However, this is not feasible for all my virtual domains and subdomains.
So, all this long-winded description to ask: "Is there an alternate DSL modem/router that I can use for my Qwest DSL service that *does* do the correct port forwarding for requests from machines inside the NAT?" |
