I thought it was the MAC address of the particular device, but yours is longer than that. Curious.
(One of the reasons we didn't want to use Wide-Area Bonjour for this). -Neil -- Neil Johnson Network Engineer The University of Iowa Phone: 319 384-0938 Fax: 319 335-2951 Mobile: 319 540-2081 E-Mail: neil-john...@uiowa.edu On 7/6/12 3:36 PM, "Cheryl-Anne Juba" <cj...@umd.edu> wrote: >Good afternoon -- > >I had a question about how you setup Wide Area Bonjour -- in your example >below you listed a dns record for _appletv-v2._tcp: > >35CF2488F02660B1._appletv-v2._tcp SRV 0 0 3689 >utnet-appletv.bonjour.utexas.edu. ; Replace with unicast FQDN of target >host >35CF2488F02660B1._appletv-v2._tcp TXT "txtvers=1" >"hG=00000000-06f6-4f5d-0171-0bcc51d34d14" "MniT=167845888" "fs=2" >"Name=utnet-appletv" "PrVs=65538" "DFID=2" "EiTS=1" "MiTPV=196611" > >What is the number prefixing the ._appletv-v2._tcp? Is that the serial >number of the unit? > >Thanks for your help! > >Cheryl-Anne Juba >Senior Network Engineer >Division of Information Technology >University of Maryland >301-405-3042 > > >-----Original Message----- >From: The EDUCAUSE Wireless Issues Constituent Group Listserv >[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Oscar Ricardo >Silva >Sent: Tuesday, December 20, 2011 7:26 PM >To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU >Subject: Re: [WIRELESS-LAN] You knew it was coming...Airplay/Apple TV >support for instructors. > >As with many of you, I've been tasked with the same thing. I manage the >DNS servers so initially tried it with static entries. That didn't quite >work so I then setup another server that allowed for dynamic updates. >That didn't work either. After basically sniffing traffic between the >Apple TV and other devices I was able to figure out the required records. > And after that I found the magical dns-sd command: > >dns-sd -Z _appletv-v2._tcp > >that would spit out the exact records (in BIND format) that are needed. > It seems that if you do a man on "dns-sd" you don't get all the actual >options. > >Anyway, the important thing here is that I spoke with an Apple engineer >and he said Apple specifically disabled streaming to/from an Apple TV. >This was a concession they made to content providers and that no amount >of DNS records or search domains would allow the Apple TV to be >contacted/used from another network. > >In case anyone is interested, here's the records I gleaned from the Apple >TV: > >$ORIGIN bonjour.utexas.edu. > >_airplay._tcp PTR utnet-appletv._airplay._tcp > >utnet-appletv._airplay._tcp SRV 0 0 7000 >utnet-appletv.bonjour.utexas.edu. ; Replace with unicast FQDN of target >host > >utnet-appletv._airplay._tcp TXT "deviceid=28:E7:CF:DB:6E:E0" >"features=0x39f7" "model=AppleTV2,1" "pw=1" "srcvers=120.2" > > > >_raop._tcp PTR 28E7CFDB6EE0@utnet-appletv._raop._tcp > >28E7CFDB6EE0@utnet-appletv._raop._tcp SRV 0 0 49152 >utnet-appletv.bonjour.utexas.edu. ; Replace with unicast FQDN of target >host > >28E7CFDB6EE0@utnet-appletv._raop._tcp TXT "txtvers=1" >"ch=2" "cn=0,1,2,3" "da=true" "et=0,3" "md=0,1,2" "pw=true" "sv=false" >"sr=44100" "ss=16" "tp=UDP" "vn=65537" "vs=120.2" "am=AppleTV2,1" "sf=0x4" > > > >_appletv-v2._tcp PTR 35CF2488F02660B1._appletv-v2._tcp > >35CF2488F02660B1._appletv-v2._tcp SRV 0 0 3689 >utnet-appletv.bonjour.utexas.edu. ; Replace with unicast FQDN of target >host >35CF2488F02660B1._appletv-v2._tcp TXT "txtvers=1" >"hG=00000000-06f6-4f5d-0171-0bcc51d34d14" "MniT=167845888" "fs=2" >"Name=utnet-appletv" "PrVs=65538" "DFID=2" "EiTS=1" "MiTPV=196611" > > > >_sleep-proxy._udp PTR 70-35-60-63\032utnet-appletv._sleep-proxy._udp > >70-35-60-63\032utnet-appletv._sleep-proxy._udp SRV 0 0 55597 >utnet-appletv.bonjour.utexas.edu. ; Replace with unicast FQDN of target >host > >70-35-60-63\032utnet-appletv._sleep-proxy._udp TXT "" > > > >Oscar Ricardo Silva >The University of Texas at Austin > > > >On 12/20/2011 06:12 PM, Oscar Ricardo Silva wrote: >> >> >> Subject: Re: You knew it was coming...Airplay/Apple TV support for >> instructors. >> From: "Johnson, Neil M" <neil-john...@uiowa.edu> >> Reply-To: The EDUCAUSE Wireless Issues Constituent Group Listserv >> <WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU> >> Date: Mon, 19 Dec 2011 18:34:42 +0000 >> Content-Type: text/plain >> Parts/Attachments: >> >> text/plain (166 lines) >> >> >> Thanks. >> >> Now I just have to convince our DNS admins to least try it out :-). >> >> I'm concerned about how scalable any solution is from a DNS (and >> device >> support) aspect. >> >> -Neil >> > >********** >Participation and subscription information for this EDUCAUSE Constituent >Group discussion list can be found at http://www.educause.edu/groups/. ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
