gangooparsand:
I suggest to fix the problem where it is, and afterwards to establish the most logical order where you want to update your dyndns.
If a router (even a 'first class'..) has erratic behaviour (sometimes..) it's time to change (or repair) it. But for the symtoms you have, the problems may persist even with a new first class box for the following reasons:
1) To update your dyndns, your 'thing' (router or any pc) must be able to connect to dyndns - there could be a problem with the service of your isp or dns-server, and even if connection is ok, there may be a lag until dnsservers are updated.
2) wireless won't connect.. ¿how may wifi networks are in your area and what channels do they use? I have seen may connection and quality problems where you have different networks, and most of them use the same factory default channels. Use a utility like netstumbler on a laptop to see how many networks use the same channel and change it to a free channel or one where you see only weak signals.
Recomended order for updating dyndns.
1) Router: The most practical solution, as updating is done even if you shut down computers on your network.
2) Dedicated update program like DynDNSupdater. Especially recomended for two reasons: a) gives you visual control if you are connected without the need trying to access webpages or routerconfig. b) works as long as your pc is running, even if you shutdown or reinitializise your server, or if you use different servers (hfs,voicechatserver,streaming...). If you use dyndns, DynDNSupdater seems to be the best choice.
3) Integrated dnsupdaters like in hfs. Avoid configuring updating from different servers, it only rises the nomber of problems like the one you mention in your first post. Happily, dynDNS does not update with an updaterequest from a different IP, so even if you see a false IP on your hfs, your gango.persand.org url will not be updated with a strange ip.
