Re: Resolve alternative TLD
Thanks Jens, will try all that over the coming days Op Jul 4, 2014, om 11:13 PM heeft Jens Alfke het volgende geschreven: > > On Jul 4, 2014, at 1:24 PM, Diederik Meijer | Ten Horses > wrote: > >> I have no experience with this sort of thing, hopefully I can make that work >> with NSURLConnection or -Session.. > > If you register an NSURLProtocol, it will be used by anything (in your > process) that uses NSURLConnection or NSURLSession. That includes UIWebViews. > > Basically, when you register a protocol class, it’ll be called for every > request and gets a chance to claim it or not. You’d just claim any request > where the NSURL’s host matched your custom domain. Then you have to handle > the request by returning an NSURLResponse and a sequence of NSData objects. > In your case you’d start up an NSURLConnection of your own (with the hostname > changed to a hardcoded IP address) and delegate to that. > > —Jens ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Resolve alternative TLD
On Jul 4, 2014, at 1:24 PM, Diederik Meijer | Ten Horses wrote: > I have no experience with this sort of thing, hopefully I can make that work > with NSURLConnection or -Session.. If you register an NSURLProtocol, it will be used by anything (in your process) that uses NSURLConnection or NSURLSession. That includes UIWebViews. Basically, when you register a protocol class, it’ll be called for every request and gets a chance to claim it or not. You’d just claim any request where the NSURL’s host matched your custom domain. Then you have to handle the request by returning an NSURLResponse and a sequence of NSData objects. In your case you’d start up an NSURLConnection of your own (with the hostname changed to a hardcoded IP address) and delegate to that. —Jens ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Resolve alternative TLD
That's very promising, thank you! I have no experience with this sort of thing, hopefully I can make that work with NSURLConnection or -Session.. I'll look into the documentation on NSURLProtocol Thanks again to you both! Op Jul 4, 2014, om 10:01 PM heeft Jens Alfke het volgende geschreven: > > On Jul 4, 2014, at 4:27 AM, Uli Kusterer wrote: > >> 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 > > Yes, NSURLProtocol is available on iOS (all versions), and it could be used > this way. > > —Jens ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Resolve alternative TLD
Let me clarify: The 'start.rentals' domain is *not* a valid domain. The root servers for .rentals have no info on it: > set q=ns > rentals Server: 192.168.123.1 Address: 192.168.123.1#53 Non-authoritative answer: rentals nameserver = demand.beta.aridns.net.au. rentals nameserver = demand.alpha.aridns.net.au. rentals nameserver = demand.gamma.aridns.net.au. rentals name server = demand.delta.aridns.net.au. > set q=a > start.rentals Server: 192.168.123.1 Address: 192.168.123.1#53 ** server can't find start.rentals: NXDOMAIN > server demand.beta.aridns.net.au Default server: demand.beta.aridns.net.au Address: 37.209.194.7#53 > start.rentals. Server: demand.beta.aridns.net.au Address: 37.209.194.7#53 ** server can't find start.rentals.: NXDOMAIN For valid 'vanity' TLDs, you must prefix it with 'http:' in order for Safari to resolve it; otherwise it simply performs a search on that term. Whoever registered 'start.rentals' needs to follow up with their registrar. Sal On Fri, Jul 4, 2014 at 3:56 PM, Sal Conigliaro wrote: > If you prefix it with 'http:', then the browser can resolve the name. > > Sal > > -- > Sal Conigliaro, > e design > http://www.erinedesign.com > @sconig > > On Fri, Jul 4, 2014 at 3:00 PM, wrote: > >> >> Date: Thu, 03 Jul 2014 22:33:21 +0200 >> From: Diederik Meijer | Ten Horses >> To: Alex Zavatone >> Cc: "cocoa-dev@lists.apple.com Developers" >> Subject: Re: Resolve alternative TLD >> Message-ID: >> Content-Type: text/plain; charset=windows-1252 >> >> This is what it looks like in the Sundial browser: >> http://www.tenhorses.com/sundial.png >> >> So I guess I somehow need to handle DNS Lookup / IP resolving myself, is >> there anybody here who has any idea how to proceed? >> >> Thanks! >> >> >> >> >> >> Op Jul 3, 2014, om 7:31 PM heeft Alex Zavatone het >> volgende geschreven: >> >> > Firefox doesn't resolve start.rental either. >> > Neither does Chrome. >> > >> > On Jul 3, 2014, at 12:58 PM, Diederik Meijer | Ten Horses wrote: >> > >> >> Take start.rental as an example, has a live server on the dot rental >> TLD, but no standard browser will resolve it, try it in Safari, you'll see.. >> >> >> >> Verstuurd vanaf mijn iPhone >> >> >> >>> Op 3 jul. 2014 om 18:22 heeft Jens Alfke het >> volgende geschreven: >> >>> >> >>> >> >>>> On Jul 3, 2014, at 6:52 AM, Diederik Meijer | Ten Horses < >> diede...@tenhorses.com> wrote: >> >>>> >> >>>> The issue being that the TLD (think for example: domain.law, with >> law being the TLD) is accessible through a DNS server, but since the TLD is >> not officially registered with ICANN, standard browsers do not resolve the >> domain into an IP address. Using a standard UIWebView does not work. But, I >> repeat, the server is up and running and the domain is accessible through >> the network. >> >>> >> >>> Really? I’m not aware of anything built into browsers that restricts >> them to a fixed set of “official” TLDs. As far as I know, the client simply >> hands off _any_ hostname for DNS lookup, which will query the configured >> DNS server(s). >> >>> >> >>> Are you 100% sure that the DNS is configured correctly? For example, >> the name server (or some parent of it) needs to have a custom entry for >> “.law”, otherwise it will end up querying upstream for it, and the upstream >> (ISP) name servers won’t know about that TLD. >> >>> >> >>> Also, are you 100% sure that the iOS device is configured to access >> the DNS server that knows about your custom domain? It’s probably getting >> the name server IP addresses via DHCP. >> >>> >> >>> —Jens >> >>> >> >>> PS: This question really belongs on the macnetworkprog mailing list. >> There are Apple networking gurus hanging out there who don’t monitor >> cocoa-dev. >> >> ___ >> >> >> >> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) >> >> >> >> 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: >> >> https://lists.apple.com/mailman/options/cocoa-dev/zav%40mac.com >> >> >> >> This email sent to z...@mac.com >> > >> > >> >> > > -- Sal Conigliaro, e design http://www.erinedesign.com @sconig ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Resolve alternative TLD
On Jul 4, 2014, at 4:27 AM, Uli Kusterer wrote: > 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 Yes, NSURLProtocol is available on iOS (all versions), and it could be used this way. —Jens ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Resolve alternative TLD
If you prefix it with 'http:', then the browser can resolve the name. Sal -- Sal Conigliaro, e design http://www.erinedesign.com @sconig On Fri, Jul 4, 2014 at 3:00 PM, wrote: > > Date: Thu, 03 Jul 2014 22:33:21 +0200 > From: Diederik Meijer | Ten Horses > To: Alex Zavatone > Cc: "cocoa-dev@lists.apple.com Developers" > Subject: Re: Resolve alternative TLD > Message-ID: > Content-Type: text/plain; charset=windows-1252 > > This is what it looks like in the Sundial browser: > http://www.tenhorses.com/sundial.png > > So I guess I somehow need to handle DNS Lookup / IP resolving myself, is > there anybody here who has any idea how to proceed? > > Thanks! > > > > > > Op Jul 3, 2014, om 7:31 PM heeft Alex Zavatone het volgende > geschreven: > > > Firefox doesn't resolve start.rental either. > > Neither does Chrome. > > > > On Jul 3, 2014, at 12:58 PM, Diederik Meijer | Ten Horses wrote: > > > >> Take start.rental as an example, has a live server on the dot rental > TLD, but no standard browser will resolve it, try it in Safari, you'll see.. > >> > >> Verstuurd vanaf mijn iPhone > >> > >>> Op 3 jul. 2014 om 18:22 heeft Jens Alfke het > volgende geschreven: > >>> > >>> > >>>> On Jul 3, 2014, at 6:52 AM, Diederik Meijer | Ten Horses < > diede...@tenhorses.com> wrote: > >>>> > >>>> The issue being that the TLD (think for example: domain.law, with law > being the TLD) is accessible through a DNS server, but since the TLD is not > officially registered with ICANN, standard browsers do not resolve the > domain into an IP address. Using a standard UIWebView does not work. But, I > repeat, the server is up and running and the domain is accessible through > the network. > >>> > >>> Really? I’m not aware of anything built into browsers that restricts > them to a fixed set of “official” TLDs. As far as I know, the client simply > hands off _any_ hostname for DNS lookup, which will query the configured > DNS server(s). > >>> > >>> Are you 100% sure that the DNS is configured correctly? For example, > the name server (or some parent of it) needs to have a custom entry for > “.law”, otherwise it will end up querying upstream for it, and the upstream > (ISP) name servers won’t know about that TLD. > >>> > >>> Also, are you 100% sure that the iOS device is configured to access > the DNS server that knows about your custom domain? It’s probably getting > the name server IP addresses via DHCP. > >>> > >>> —Jens > >>> > >>> PS: This question really belongs on the macnetworkprog mailing list. > There are Apple networking gurus hanging out there who don’t monitor > cocoa-dev. > >> ___ > >> > >> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > >> > >> 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: > >> https://lists.apple.com/mailman/options/cocoa-dev/zav%40mac.com > >> > >> This email sent to z...@mac.com > > > > > > ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Resolve alternative TLD
On 03 Jul 2014, at 22:54, Jens Alfke wrote: > On Jul 3, 2014, at 1:33 PM, Diederik Meijer | Ten Horses > 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 (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Resolve alternative TLD
OK thanks everybody! Op Jul 3, 2014, om 10:54 PM heeft Jens Alfke het volgende geschreven: > > On Jul 3, 2014, at 1:33 PM, Diederik Meijer | Ten Horses > 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. > > —Jens ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Resolve alternative TLD
On Jul 3, 2014, at 1:33 PM, Diederik Meijer | Ten Horses 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. —Jens ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Resolve alternative TLD
On Jul 3, 2014, at 10:31 AM, Alex Zavatone wrote: > Firefox doesn't resolve start.rental either. > Neither does Chrome. Yup. It is not a valid TLD in that .rental is not known to any of the root servers. Domain lookups for uncached entries start at one of the root servers. If those servers don't know how to get to the .rental domain then for all practical purposes it doesn't exist. On the other hand ".rentals" (note the trailing "s") is a valid TLD. See http://www.iana.org/domains/root/db/rentals.html However, the .rentals server knows nothing about the start.rentals domain. $ whois -h whois.donuts.co start.rentals Domain not found. ... Marc ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Resolve alternative TLD
This is what it looks like in the Sundial browser: http://www.tenhorses.com/sundial.png So I guess I somehow need to handle DNS Lookup / IP resolving myself, is there anybody here who has any idea how to proceed? Thanks! Op Jul 3, 2014, om 7:31 PM heeft Alex Zavatone het volgende geschreven: > Firefox doesn't resolve start.rental either. > Neither does Chrome. > > On Jul 3, 2014, at 12:58 PM, Diederik Meijer | Ten Horses wrote: > >> Take start.rental as an example, has a live server on the dot rental TLD, >> but no standard browser will resolve it, try it in Safari, you'll see.. >> >> Verstuurd vanaf mijn iPhone >> >>> Op 3 jul. 2014 om 18:22 heeft Jens Alfke het volgende >>> geschreven: >>> >>> On Jul 3, 2014, at 6:52 AM, Diederik Meijer | Ten Horses wrote: The issue being that the TLD (think for example: domain.law, with law being the TLD) is accessible through a DNS server, but since the TLD is not officially registered with ICANN, standard browsers do not resolve the domain into an IP address. Using a standard UIWebView does not work. But, I repeat, the server is up and running and the domain is accessible through the network. >>> >>> Really? I’m not aware of anything built into browsers that restricts them >>> to a fixed set of “official” TLDs. As far as I know, the client simply >>> hands off _any_ hostname for DNS lookup, which will query the configured >>> DNS server(s). >>> >>> Are you 100% sure that the DNS is configured correctly? For example, the >>> name server (or some parent of it) needs to have a custom entry for “.law”, >>> otherwise it will end up querying upstream for it, and the upstream (ISP) >>> name servers won’t know about that TLD. >>> >>> Also, are you 100% sure that the iOS device is configured to access the DNS >>> server that knows about your custom domain? It’s probably getting the name >>> server IP addresses via DHCP. >>> >>> —Jens >>> >>> PS: This question really belongs on the macnetworkprog mailing list. There >>> are Apple networking gurus hanging out there who don’t monitor cocoa-dev. >> ___ >> >> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) >> >> 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: >> https://lists.apple.com/mailman/options/cocoa-dev/zav%40mac.com >> >> This email sent to z...@mac.com > > ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Resolve alternative TLD
On Jul 3, 2014, at 10:31 AM, Alex Zavatone wrote: > Firefox doesn't resolve start.rental either. > Neither does Chrome. Neither does curl, nor whois. (And I tried the same commands on a Linux system and they failed there too, so this isn’t specific to Apple OSs.) $ curl start.rental curl: (6) Could not resolve host: start.rental $ whois start.rental whois: rental.whois-servers.net: nodename nor servname provided, or not known My guess is that the global root name servers (run by ICANN) haven’t been updated to support custom TLDs yet. (I’m not really following that topic, mostly because I think custom TLDs are silly, so I don’t know whether they’re supposed to be enabled yet or not.) —Jens ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Resolve alternative TLD
Firefox doesn't resolve start.rental either. Neither does Chrome. On Jul 3, 2014, at 12:58 PM, Diederik Meijer | Ten Horses wrote: > Take start.rental as an example, has a live server on the dot rental TLD, but > no standard browser will resolve it, try it in Safari, you'll see.. > > Verstuurd vanaf mijn iPhone > >> Op 3 jul. 2014 om 18:22 heeft Jens Alfke het volgende >> geschreven: >> >> >>> On Jul 3, 2014, at 6:52 AM, Diederik Meijer | Ten Horses >>> wrote: >>> >>> The issue being that the TLD (think for example: domain.law, with law being >>> the TLD) is accessible through a DNS server, but since the TLD is not >>> officially registered with ICANN, standard browsers do not resolve the >>> domain into an IP address. Using a standard UIWebView does not work. But, I >>> repeat, the server is up and running and the domain is accessible through >>> the network. >> >> Really? I’m not aware of anything built into browsers that restricts them to >> a fixed set of “official” TLDs. As far as I know, the client simply hands >> off _any_ hostname for DNS lookup, which will query the configured DNS >> server(s). >> >> Are you 100% sure that the DNS is configured correctly? For example, the >> name server (or some parent of it) needs to have a custom entry for “.law”, >> otherwise it will end up querying upstream for it, and the upstream (ISP) >> name servers won’t know about that TLD. >> >> Also, are you 100% sure that the iOS device is configured to access the DNS >> server that knows about your custom domain? It’s probably getting the name >> server IP addresses via DHCP. >> >> —Jens >> >> PS: This question really belongs on the macnetworkprog mailing list. There >> are Apple networking gurus hanging out there who don’t monitor cocoa-dev. > ___ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > 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: > https://lists.apple.com/mailman/options/cocoa-dev/zav%40mac.com > > This email sent to z...@mac.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Resolve alternative TLD
Wait, so it's not a real DNS server, or what? I suppose in that case you'd have to take the URL and look up the domain yourself, then feed the raw IP address to WebKit instead. > > Cheers, > -- Uli Kusterer > "The Witnesses of TeachText are everywhere..." > http://www.zathras.d Exactly, any experience on looking up the domain and handling the ip address? I have no idea how to do that... ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Resolve alternative TLD
Had such an issue today on an iPad with DNS pointing to a local Mac OSx server. Did not resolve server.local until we put "local" into search domains on the iPad. Regards Danny Sent from my iPhone > On 03 Jul 2014, at 19:13, Uli Kusterer wrote: > >> On 03 Jul 2014, at 19:07, Diederik Meijer | Ten Horses >> wrote: >> Thanks, prefixing my one just reports 'server cannot be found'... > > Wait, so it's not a real DNS server, or what? I suppose in that case you'd > have to take the URL and look up the domain yourself, then feed the raw IP > address to WebKit instead. > > Cheers, > -- Uli Kusterer > "The Witnesses of TeachText are everywhere..." > http://www.zathras.de > > > ___ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > 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: > https://lists.apple.com/mailman/options/cocoa-dev/dthuering%40gmail.com > > This email sent to dthuer...@gmail.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Resolve alternative TLD
On 03 Jul 2014, at 19:07, Diederik Meijer | Ten Horses wrote: > Thanks, prefixing my one just reports 'server cannot be found'... Wait, so it's not a real DNS server, or what? I suppose in that case you'd have to take the URL and look up the domain yourself, then feed the raw IP address to WebKit instead. Cheers, -- Uli Kusterer "The Witnesses of TeachText are everywhere..." http://www.zathras.de ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Resolve alternative TLD
On 03 Jul 2014, at 18:54, Paul Scott wrote: > This is a known problem on Safari for Mac, and presumably for iOS. I reported > it, and my bug report was closed as a duplicate of radar:10252476. We have a > corporate TLD that does not resolve in safari, unless you prefix it with > http:// so that Safari doesn’t treat it as a search term. That is a feature of Safari's URL entry text field. NSURLRequest etc. will take your word for it that whatever you give it is a valid domain name and try to resolve it, not matter what the TLD is. They do not perform google searches. So if this is a web view in your own app, it should just work. Have you tried it? Cheers, -- Uli Kusterer "The Witnesses of TeachText are everywhere..." http://www.zathras.de ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Resolve alternative TLD
Thanks, prefixing my one just reports 'server cannot be found'... Verstuurd vanaf mijn iPhone > Op 3 jul. 2014 om 18:54 heeft Paul Scott het volgende > geschreven: > > This is a known problem on Safari for Mac, and presumably for iOS. I reported > it, and my bug report was closed as a duplicate of radar:10252476. We have a > corporate TLD that does not resolve in safari, unless you prefix it with > http:// so that Safari doesn’t treat it as a search term. > > Paul > >> On Jul 3, 2014, at 9:22 AM, Jens Alfke wrote: >> >> >> On Jul 3, 2014, at 6:52 AM, Diederik Meijer | Ten Horses >> wrote: >> >>> The issue being that the TLD (think for example: domain.law, with law being >>> the TLD) is accessible through a DNS server, but since the TLD is not >>> officially registered with ICANN, standard browsers do not resolve the >>> domain into an IP address. Using a standard UIWebView does not work. But, I >>> repeat, the server is up and running and the domain is accessible through >>> the network. >> >> Really? I’m not aware of anything built into browsers that restricts them to >> a fixed set of “official” TLDs. As far as I know, the client simply hands >> off _any_ hostname for DNS lookup, which will query the configured DNS >> server(s). >> >> Are you 100% sure that the DNS is configured correctly? For example, the >> name server (or some parent of it) needs to have a custom entry for “.law”, >> otherwise it will end up querying upstream for it, and the upstream (ISP) >> name servers won’t know about that TLD. >> >> Also, are you 100% sure that the iOS device is configured to access the DNS >> server that knows about your custom domain? It’s probably getting the name >> server IP addresses via DHCP. >> >> —Jens >> >> PS: This question really belongs on the macnetworkprog mailing list. There >> are Apple networking gurus hanging out there who don’t monitor cocoa-dev. > > -- > Paul Scott > psc...@skycoast.us > ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Resolve alternative TLD
In addition, if you run it through the Sundial browser (www.sundialbrowser.com), it will resolve .rental domains... ICANN effectively has a monopoly on which TLD's are accessible. Forclarity: this is not a new TLD generally issued, it is a TLD issued bu unifiedroot.com Verstuurd vanaf mijn iPhone > Op 3 jul. 2014 om 18:22 heeft Jens Alfke het volgende > geschreven: > > >> On Jul 3, 2014, at 6:52 AM, Diederik Meijer | Ten Horses >> wrote: >> >> The issue being that the TLD (think for example: domain.law, with law being >> the TLD) is accessible through a DNS server, but since the TLD is not >> officially registered with ICANN, standard browsers do not resolve the >> domain into an IP address. Using a standard UIWebView does not work. But, I >> repeat, the server is up and running and the domain is accessible through >> the network. > > Really? I’m not aware of anything built into browsers that restricts them to > a fixed set of “official” TLDs. As far as I know, the client simply hands off > _any_ hostname for DNS lookup, which will query the configured DNS server(s). > > Are you 100% sure that the DNS is configured correctly? For example, the name > server (or some parent of it) needs to have a custom entry for “.law”, > otherwise it will end up querying upstream for it, and the upstream (ISP) > name servers won’t know about that TLD. > > Also, are you 100% sure that the iOS device is configured to access the DNS > server that knows about your custom domain? It’s probably getting the name > server IP addresses via DHCP. > > —Jens > > PS: This question really belongs on the macnetworkprog mailing list. There > are Apple networking gurus hanging out there who don’t monitor cocoa-dev. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Resolve alternative TLD
Take start.rental as an example, has a live server on the dot rental TLD, but no standard browser will resolve it, try it in Safari, you'll see.. Verstuurd vanaf mijn iPhone > Op 3 jul. 2014 om 18:22 heeft Jens Alfke het volgende > geschreven: > > >> On Jul 3, 2014, at 6:52 AM, Diederik Meijer | Ten Horses >> wrote: >> >> The issue being that the TLD (think for example: domain.law, with law being >> the TLD) is accessible through a DNS server, but since the TLD is not >> officially registered with ICANN, standard browsers do not resolve the >> domain into an IP address. Using a standard UIWebView does not work. But, I >> repeat, the server is up and running and the domain is accessible through >> the network. > > Really? I’m not aware of anything built into browsers that restricts them to > a fixed set of “official” TLDs. As far as I know, the client simply hands off > _any_ hostname for DNS lookup, which will query the configured DNS server(s). > > Are you 100% sure that the DNS is configured correctly? For example, the name > server (or some parent of it) needs to have a custom entry for “.law”, > otherwise it will end up querying upstream for it, and the upstream (ISP) > name servers won’t know about that TLD. > > Also, are you 100% sure that the iOS device is configured to access the DNS > server that knows about your custom domain? It’s probably getting the name > server IP addresses via DHCP. > > —Jens > > PS: This question really belongs on the macnetworkprog mailing list. There > are Apple networking gurus hanging out there who don’t monitor cocoa-dev. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Resolve alternative TLD
This is a known problem on Safari for Mac, and presumably for iOS. I reported it, and my bug report was closed as a duplicate of radar:10252476. We have a corporate TLD that does not resolve in safari, unless you prefix it with http:// so that Safari doesn’t treat it as a search term. Paul > On Jul 3, 2014, at 9:22 AM, Jens Alfke wrote: > > > On Jul 3, 2014, at 6:52 AM, Diederik Meijer | Ten Horses > wrote: > >> The issue being that the TLD (think for example: domain.law, with law being >> the TLD) is accessible through a DNS server, but since the TLD is not >> officially registered with ICANN, standard browsers do not resolve the >> domain into an IP address. Using a standard UIWebView does not work. But, I >> repeat, the server is up and running and the domain is accessible through >> the network. > > Really? I’m not aware of anything built into browsers that restricts them to > a fixed set of “official” TLDs. As far as I know, the client simply hands off > _any_ hostname for DNS lookup, which will query the configured DNS server(s). > > Are you 100% sure that the DNS is configured correctly? For example, the name > server (or some parent of it) needs to have a custom entry for “.law”, > otherwise it will end up querying upstream for it, and the upstream (ISP) > name servers won’t know about that TLD. > > Also, are you 100% sure that the iOS device is configured to access the DNS > server that knows about your custom domain? It’s probably getting the name > server IP addresses via DHCP. > > —Jens > > PS: This question really belongs on the macnetworkprog mailing list. There > are Apple networking gurus hanging out there who don’t monitor cocoa-dev. > -- Paul Scott psc...@skycoast.us smime.p7s Description: S/MIME cryptographic signature ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Resolve alternative TLD
On Jul 3, 2014, at 6:52 AM, Diederik Meijer | Ten Horses wrote: > The issue being that the TLD (think for example: domain.law, with law being > the TLD) is accessible through a DNS server, but since the TLD is not > officially registered with ICANN, standard browsers do not resolve the domain > into an IP address. Using a standard UIWebView does not work. But, I repeat, > the server is up and running and the domain is accessible through the network. Really? I’m not aware of anything built into browsers that restricts them to a fixed set of “official” TLDs. As far as I know, the client simply hands off _any_ hostname for DNS lookup, which will query the configured DNS server(s). Are you 100% sure that the DNS is configured correctly? For example, the name server (or some parent of it) needs to have a custom entry for “.law”, otherwise it will end up querying upstream for it, and the upstream (ISP) name servers won’t know about that TLD. Also, are you 100% sure that the iOS device is configured to access the DNS server that knows about your custom domain? It’s probably getting the name server IP addresses via DHCP. —Jens PS: This question really belongs on the macnetworkprog mailing list. There are Apple networking gurus hanging out there who don’t monitor cocoa-dev. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Resolve alternative TLD
Dear list, Is it possible to have an iOS app connect to a web server through a domain name that uses an alternative TLD (top level domain name)? The issue being that the TLD (think for example: domain.law, with law being the TLD) is accessible through a DNS server, but since the TLD is not officially registered with ICANN, standard browsers do not resolve the domain into an IP address. Using a standard UIWebView does not work. But, I repeat, the server is up and running and the domain is accessible through the network. Is there any way to configure my app's networking classes to handle this, like resolving the domain itself, or pointing the networking requests to the appropriate DNS? Is there anybody out there with experience on this that can point me in the right direction? I think I saw something related fly by on this list a couple of weeks back, but now I cannot seem to find it. Many thanks, Diederik ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
