Forum OpenACS Q&A: Setting up dynamic DNS on a home server

Collapse
1: Setting up dynamic DNS on a home server
Posted by Jade Rubick on 11/16/02 05:44 AM
I'm in the process of setting up dynamic DNS on a home server, which I plan to eventually host an OpenACS server on.

If I traceroute to the location my server is at right now... 


[jade@hades ~]$ traceroute hdslppp148.ptld.uswest.net
traceroute to hdslppp148.ptld.uswest.net (209.180.171.148), 30 hops max, 38 byte packets
 1  foundry0 (128.100.4.210)  4.106 ms  2.074 ms  2.065 ms
 2  sf-cs1.gw.utoronto.ca (128.100.1.253)  0.536 ms  0.423 ms  0.444 ms
 3  mcl-gpb.gw.utoronto.ca (128.100.96.10)  0.680 ms  0.543 ms  0.515 ms
 4  gate-gateway.gw.utoronto.ca (128.100.96.100)  2.053 ms  2.092 ms  2.752 ms
 5  border-utorgw-if.onet.on.ca (206.248.221.5)  2.274 ms  2.092 ms  3.076 ms
 6  POS10-1.PEERA-TOROON.IP.GROUPTELECOM.NET (206.221.246.125)  2.547 ms  1.854 ms  2.523 ms
 7  GE3-0.WANA-TOROON.IP.GROUPTELECOM.NET (66.59.191.5)  2.509 ms  2.760 ms  2.848 ms
 8  GE1-0.PEERA-CHCGIL.IP.GROUPTELECOM.NET (66.59.191.82)  13.703 ms  15.432 ms  14.173 ms
 9  iar1-so-2-3-0.Chicago.cw.net (208.172.10.153)  13.740 ms  14.084 ms  14.098 ms
10  agr1-loopback.Chicago.cw.net (208.172.2.101)  15.082 ms  13.764 ms  13.976 ms
11  dcr1-so-6-0-0.Chicago.cw.net (208.175.10.49)  13.820 ms  13.607 ms  14.813 ms
12  agr4-so-0-0-0.Chicago.cw.net (208.175.10.30)  14.658 ms  14.401 ms  24.223 ms
13  acr1-loopback.Seattle.cw.net (208.172.82.61)  65.021 ms  55.019 ms  54.654 ms
14  bpr1-as0-0.SeattleSwitchDesign.cw.net (208.172.83.185)  55.127 ms  54.578 ms  54.872 ms
15  touch-america.SeattleSwitchDesign.cw.net (208.173.49.2)  62.753 ms  61.829 ms  61.974 ms
16  por-core-02.tamerica.net (205.171.8.74)  65.727 ms  65.550 ms  65.415 ms
17  ptld-agw2.inet.qwest.net (205.171.130.38)  66.058 ms  66.679 ms  65.168 ms
18  ptld-dsl-gw2.ptld.uswest.net (216.161.52.2)  67.561 ms  65.588 ms  66.639 ms
19  * * *
20  * * *
21  * * *
22  * * *
Does this mean that Uswest (Qwest)'s gateway is blocking access to my server. Pinging works fine, but it looks like traceroutes (and attempts to telnet to ports 993, 22, 25, and so on) don't work.

Any suggestions? Do I have to go with static IPs?

Collapse
2: Re: Setting up dynamic DNS on a home server (response to 1)
Posted by Jonathan Ellis on 11/16/02 07:25 AM
not enough detail... how many hops away from your server was the trace when it stopped? I know qwest likes to set you up with a NAT-ing router, at least before they got in bed with MSN; has that been set up?

(FWIW, carnage blender is hosted on a qwest residential dsl line, and they seem much more server-friendly than most. it's been a long time since I had a dynamic IP, though; it's just so much easier to find a real ISP that will take qwest's line and give you a static IP for it.)

Collapse
3: Re: Setting up dynamic DNS on a home server (response to 2)
Posted by Jade Rubick on 11/16/02 05:46 PM
Thanks for your help, Jonathan. It's been a rough ride. :)

I believe that is just a hop or two away from my server. When I traceroute from my server to that gateway, it looks like it doesn't return anything: 

jade@mail jade]$ /usr/sbin/traceroute ptld-dsl-gw2.ptld.uswest.net
traceroute to ptld-dsl-gw2.ptld.uswest.net (216.161.52.2), 30 hops max, 38 bytepackets
 1  * * *
 2  * * *
So I guess that isn't very helpful. But it does worry me that if I telnet to ports 22, 25, or 993 at the address I'm currently at, I don't get any activity.

I guess this could be because my port forwarding from the router isn't working, but I don't really have any way of checking it that I can think of, besides what I'm doing.

Is there anybody out there using dynamic DNS on Qwest? Any other advice?

Collapse
4: Re: Setting up dynamic DNS on a home server (response to 1)
Posted by Jonathan Ellis on 11/16/02 09:52 PM
it does look like a problem at their end -- however, one way you can verify it's not the port forwarding is, most routers are remotely configurable through telnet and/or port 80. try enabling one of those.