akornetov-chasemail-org
Level 1
(5 points)
Q: iOS 9 and airprint with dns-sd
With the recent release of iOS 9, airprint has stopped working completely in our campus. Prior to iOS 9 we were using DNS-SD via static DNS records, with different subdomains for each network so we could control who prints to what printer. IE:
192.168.200.x wireless subnet
query PTR lb._dns-sd._udp.0.200.168.192.in-addr.arpa ---> example.local
192.168.300.x wireless students subnet
query PTR lb._dns-sd._udp.0.300.168.192.in-addr.arpa ---> studentnet.example.local
This way we are able to control which printers get published to which people. Under iOS 8.4 and older, the iPad would then query the DNS server for the IPP records and discover the printer. After that it was happy printing!
_universal._sub._ipp._tcp.example.local: type PTR, class IN --> officeprinter1._ipp._tcp.example.local
OR
_universal._sub._ipp._tcp.studentnet.example.local: type PTR, class IN --> officeprinter1._ipp._tcp.example.local
As of iOS 9, the behavior is now the below, instead
Standard query 0x84bb SOA local ---> response "no such name"
What is the purpose of changing the DNS lookup behavior? It worked fine in IOS 8.4, and while the new airprint features are excellent, there doesn't seem to be a rhyme or reason as to changing the DNS lookup behavior.
iPad, iOS 9.0.1, airprint in a campus
rccharles
Level 6
(8,476 points)
Education Customers
Support: 1-800-800-2775
Sales: 1-800-780-5009
