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 <z...@mac.com> 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 <j...@mooseyard.com> 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