|
This question was originally included on another post, and was moved here as a standalone question for clarity. Hi Cory, I've tried to get this working with my Airport Extreme running version 7.5 (75000.17) and using version 5.5 (550.29) of the Airport Utility but can't get it to work. I've checked over the instructions several times and can't see where I'm going wrong. I can get my laptop to work though so I guess that I have the DNS set up correctly and I really can't see the difference in what I'm doing between the laptop and the airport. Any suggestions? Is there something missing in the instructions for the Airport? Thanks, Alan The settings for the base station and here is the host name section: I did wonder whether I needed to share anything on the airport to get t to work so I published my printer, that turned up as various entries but none with my global hostname. Regards Alan |
The question has been closed Dec 05 at 06:52 AM ago by Cry Havok for the following reason "Abandoned question".
|
I've just checked and it is now working? I haven't changed anything although I did take my laptop into the office so it would have updated its record. I also power-cycled the modem when I returned home which would have caused the Airport to reconnect and update its record also. |
|
Hi Cory, I believe IETF 77 is now over. Did you eventually get to head along and if so is there anything to report from your contacts at Apple on this particular issue? Thanks Hi Chris, Yes, it's an issue they've encountered before, and I think our observation that the behavior is different if the PTR record exists for the device IP has given them some useful direction to check out. I just sent out a follow up email to our contacts there, and hopefully will hear back soon on when this will be fixed. I'll keep the http://DynDNS.com Community posted on our progress! -Cory
Apr 14 at 04:10 PM
cvonwallenstein ♦♦
|
|
Hi Steven, It has been working for me since March, the issues I had above cleared when I removed the MobileMe details from the Airport. Apart from remote access which works without any configuration of the Airport I have also been able to print remotely as well. It is available to use now, all you need to do is purchase their Custom DNS service add the records and configure your Mac and Airport. Regards Alan |
|
Hi Steven, Sorry for the long delay, I was unaware that this thread had been updated. I can vouch that the screen sharing and printing works, I don't have a drive connected to my Airport Extreme so can't comment although I'm assuming that it will work just like the other services. One smart feature is the ability to choose which machine I want to screen share with, if I connect to my network remotely then I can connect to any of the machines that are offering the service, not just one as before. Everything works through the router, it is on all of the time and the printer is connected to it, I can even check on the ink levels remotely. If the Macs are off then they don't appear, I would assume that the attached drive would be available at all times as well. I guess the community wiki copies the message onto the wiki for all to see? Regards Alan |
|
Alan, After looking at the log files on our end and seeing your updates come through, I've identified the issue. The logic in the Apple products for advertising a global dynamic hostname in http://DynDNS.com has a precondition of determining whether or not a hostname already exists. That's not to say the specified hostname exists; rather, it checks for any hostname in existence. This is determined by the device doing a reverse DNS lookup of its IP address. From the perspective of the Apple AirPort device, the IP address is the WAN IP. The Apple AirPort did the equivalent of (where NN.NN.NN.NN is your WAN IP address):
And found a valid hostname for its WAN IP in reverse DNS. Since the device determined that it already had a valid hostname, there was no need for it register another one at http://airport-extreme.justtoast.com. If you look in your Custom DNS zone, you will indeed see your printer advertised, and the SRV records are pointing to this hostname that the Apple AirPort found by doing a reverse DNS lookup. The device only talked to the servers at http://DynDNS.com when it needed to register the service; it had no need to create another global dynamic hostname, since it had already found one. Compare and contrast this to your computer accessing the Internet from behind the Apple AirPort. This computer would have an internal NAT IP. When your computer did a reverse DNS lookup, no result would have been returned, since the address is private to your network and you likely did not configure reverse DNS for your network. Therefore, to be uniquely identified, your computer registered a dynamic global hostname at http://DynDNS.com. Had your computer been directly connected to your cable/DSL model or other means of connectivity (and not behind the Apple AirPort home gateway), it would have done the same thing that the AirPort did: used the hostname returned by the reverse DNS lookup. It's important to note that all of this is transparent to your users for the purpose of sharing services. They never have to enter "airport-extreme.justtoast.com", they only have to browse "justtoast.com" for advertised services, and their computers will be able to access those services using friendly instance names. Regardless of whether the actual hosts use the already provided hostnames as determined by reverse DNS or register new hostnames within your zone, the PTR, SRV, and TXT records required for Wide Area Bonjour are still setup correctly, and users can successfully discover the services. |
1 2 next page »