8 Comments

Summary:

Last week DynDNS released its beta support for Wide Area Bonjour and DNS Service Discovery. This means that if you own your own domain name, and you have a Custom DNS service with DynDNS, you can configure your Apple AirPort device (AirPort Extreme, AirPort Express and […]

Last week DynDNS released its beta support for Wide Area Bonjour and DNS Service Discovery. This means that if you own your own domain name, and you have a Custom DNS service with DynDNS, you can configure your Apple AirPort device (AirPort Extreme, AirPort Express and Time Capsule) to present itself as part of that domain, automatically updating your domain name and broadcasting configured services.

What is Wide Area Bonjour?

Wide Area Bonjour enables the same zero-config automatic service discovery functionality over the public Internet that we all enjoy on our local network (seeing our shared files, printers, scanners and so forth). If you have a MobileMe account and utilize the Back To My Mac functionality, you’re already using Wide Area Bonjour without even knowing it.

Why would we use this?

Most of us who use DynDNS use it to be able to let the IP Address that our ISP give us resolve with a friendly domain name (such as myname.homedns.org). This basic free DynDNS service works really well as long as you have a third-party router that supports DynDNS (which most of them do). Unfortunately Apple, being Apple, does not support DynDNS in its routers, leaving you to run the OS X DynDNS updater application on your computer. The downside to this is that if your computer is asleep and your home Internet connection drops and reconnects (giving you a new IP address) DynDNS does not get updated until the computer wakes up. When wanting to use Snow Leopard’s Wake On Demand feature this is a problem, so this has meant “tough luck,” requiring you to run the DynDNS Mac client on multiple machines and hope the IP updating occurs often enough. It generally works fine, with the occasional expected downtime when your home IP changes at midday if computers are sleeping.

Does it work?

This DynDNS Community post explains the current problem the DynDNS team are having. The gist is that while the Wide Area Bonjour service discovery works just fine, the domain name IP allocation will only work if your IP does not resolve a reverse name lookup. This is an issue since almost all Internet Providers that give you a dynamic IP address have a full domain name allocated already. For instance, if you do a reserve name lookup on your dynamic IP you may get a name of 123-148-53-102.dyn.ispname.com. This is a problem because of the way Apple’s Global Dynamic Hostname configuration currently works. It will only attempt to configure a name for the IP address if a name doesn’t already exist. DynDNS has queried Apple about the way this works and it appears to be non-intentional behaviour caused by a bug. Apple has indicated on the bonjour mailing list that a fix will come some time in the future, but at this stage there is no ETA. Apple will have to issue firmware updates for the Airport devices to make this work as expected.

What is working fine at the moment is Wide Area Bonjour service discovery. So if you have a static IP that does not resolve with a reverse name lookup and would like to emulate the kind of automatic service discovery functionality that you experience with Back To My Mac, you can achieve this goal with DynDNS now. DynDNS have two guides to assist with the appropriate configurations if you want to give it a try:

  1. Great write up! We’re meeting with some of the Apple folks next week at IETF in Anaheim, California, and hopefully we can help with the efforts to get the AirPort issue resolved. If anyone needs help setting up Wide Area Bonjour, we’re currently providing support for this beta functionality on the community site at http://www.dyndnscommunity.com.

    Share
  2. Frankly, I’d just ditch the Apple router rather than going through all the hoopla. Or, as I do, have my servers hosted, so it’s not a problem…

    Share
    1. I have never found a 3rd party router (with any firmware variations open and closed) that works without any issues for Back To My Mac with multiple client Macs. Apple routers work perfectly for me.

      Share
  3. [...] more at The Apple Blog AKPC_IDS += "512,"; Share this Post: Tagged [...]

    Share
  4. Ditching the Apple Router is a rather extreme solution, especially given all he other things it does so well.

    Share
  5. I’m on the verge of selling mine… a huge draw was the Back to My Mac and Airport Disk functionality, but apparently I can’t reach it from work (government… firewalls… bureaucracy). Would this solution / DynDNS work differently/better than BTMM?

    Share
    1. To be honest, I’ve no idea about Back To My Mac, BUT what worked for me in a particularly restrictive environment, were two things.

      1) LogMeIn.com – if this is still restrictive, what I ended up doing to access my Linux machine via SSH/VNC was to

      2) set up port 80 (yes, that’s right, port 80) on my router, to forward to the SSH port (22) on my server. Realistically, who serves webpages on port 80 from their *home* machine? And if you do, you sure want to be on top of security issues. In short, *don’t*….which leaves 80 free and open for ssh traffic. And unless your work allows no net access at all, or only to “whitelisted” sites (which is rare), they probably won’t be blocking port 80 to random addresses, such as your home ip. Set up PuTTY to for local port forwarding from the VNC port to port 80, and you’re home free….

      Share
  6. It may solve your issues of discovery, but I doubt it will solve your issues of protocol. You will still not be able to mount your AFP/SMB shares and copy files back and forth, no matter the solution, if your work (like mine) does not allow for it. You need to set up some sort of secure tunnel using a VPN to do that…

    Share

Comments have been disabled for this post