[Closed] Apple Time Capsule failing to register its dynamic global hostname in my Custom DNS Zone

Hello world and people at DynDNS,

Following the advice of a tutorial published by DynDNS (which can be found here: http://www.dyndns.com/support/kb/apple_airport_with_custom_dns.html) I decided to buy the custom DNS service in order to be able to access my time machine remotely using a hostname and have it update my dynamic IP address much like my previous router was able to do with the free dynamic DNS service (I don't know why Apple can't include this functionality in the Time Capsule, practically all routers worth their salt these days support some form of free dynamic DNS service, but then I suppose there's no money in that, is there Apple?).

However, I have since discovered that this service is not reliable. The problem is that after rebooting the Time Capsule (I'm assuming that it's the Time Capsule but it could be a problem on the side of DynDNS too) it appears to fail to register its dynamic global hostname with my custom domain (if I login to my account with DynDNS and check my the "custom DNS zone" area the entry for http://timecapsule.my-custom-dns-zone.com has disappeared). It is then necessary to wait a while and then reboot the Time Capsule once again in order for it to correctly register the dynamic global hostname (although not always, sometimes it is necessary to reboot it up to two times for this to be corrected).

This flaw bascially renders this service useless as I can't rely on it to work when accessing the Time Capsule remotely. If I make any configuration changes to the Time Capsule remotely via the Airport Utility it will reboot when I apply them (yes, this is another problem with this device, why do have to reboot the thing if I do something as simple as forward a new port Apple?) which then usually leads to the global hostname not being registered with DynDNS as described above, which in turn means that I have essentially lost "contact" with the Time Capsule permamently until I reboot it and it correctly registers its hostname (which I obviously can't do remotely if I have lost contact with the Time Capsule, the only way to reboot now would be doing it physically at the location of the Time Capsule).

Is anybody else experiencing this issue? Or am I in the minority?

My three questions on this matter would be:

1) Apple, why are you so rubbish?

2) DynDNS why are you willingly adivising people to buy a service to do a thing which you are already aware doesn't actually work? This bug is obviously something which you are aware of as is evidenced by this link: http://www.dyndnscommunity.com/questions/1087/apple-airport-does-not-create-global-dynamic-hostname-in-custom-dns-zone, which, unfortunately, I only discovered after I had already bought the ~$45 custom DNS service.

3) How would I go about getting a refund on the ~$45 I paid for the custom DNS service which isn't able to do what it was advertised as being able to do in the tutorial? I really feel like I have been taken for a ride here as I am not going to be using the custom DNS for anything else.

I look forward to hearing from someone at DynDNS.

Thanks, Martin.