Re: Resolve alternative TLD
Re: Resolve alternative TLD
- Subject: Re: Resolve alternative TLD
- From: Uli Kusterer <email@hidden>
- Date: Fri, 04 Jul 2014 13:27:23 +0200
On 03 Jul 2014, at 22:54, Jens Alfke <email@hidden> wrote:
> On Jul 3, 2014, at 1:33 PM, Diederik Meijer | Ten Horses <email@hidden> wrote:
>
>> So I guess I somehow need to handle DNS Lookup / IP resolving myself, is there anybody here who has any idea how to proceed?
>
> If this were Mac OS you could edit /etc/hosts and add an entry for that domain, but that won’t fly on iOS.
>
> You can set up a local nameserver (bind or something like that) and configure it with a hardwired entry for that domain, then point the local WiFi router to use that nameserver as the DNS address it advertises via DHCP.
One thought: On OS X you could probably also register a URL scheme of your own (or override an existing URL scheme) by hooking into the URL loading system. Not sure whether that API is available on iOS, but might be worth looking into as a hook-in point for a manual DNS resolution: Check if the URL is IPv4 or IPv6 raw IP, if not, resolve, then redirect to the raw URL. Also, I haven't looked into what has actually changed, but there have been lots of WebKit changes for iOS 8, so if you can require that, you might have additional API to solve this problem with.
Cheers,
-- Uli Kusterer
"The Witnesses of TeachText are everywhere..."
http://www.zathras.de
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden