Is solving this problem at the DNS level really necessary?
Apple already has tech in place to both associate a native app with a domain name (so you can share login keychain items between a native app and its corresponding site in Safari), and to associate a specific HTML page with a native app + optional deep-link URL (see: the 'open in <X app>' banner in Safari).
The fact that Apple hasn't connected the dots to provide a better experience is bizarre, but seems to be one constrained by product decisions rather than pure technical limitations. Mucking around with DNS adds in a lot of complexity for few apparent gains.
(To say nothing of the major problem this doesn't seem to be trying to solve, which is iOS not having a system like Android's Intents to manage routing a single desired action to multiple apps that could all potentially handle it)
Apple already has tech in place to both associate a native app with a domain name (so you can share login keychain items between a native app and its corresponding site in Safari), and to associate a specific HTML page with a native app + optional deep-link URL (see: the 'open in <X app>' banner in Safari).
The fact that Apple hasn't connected the dots to provide a better experience is bizarre, but seems to be one constrained by product decisions rather than pure technical limitations. Mucking around with DNS adds in a lot of complexity for few apparent gains.
(To say nothing of the major problem this doesn't seem to be trying to solve, which is iOS not having a system like Android's Intents to manage routing a single desired action to multiple apps that could all potentially handle it)