::1 localhost mysite.local myothersite.local anothersite.local yetanothersite. What could I be missing Thanks in advance for. Also, looking into my IIS I noticed that only one application is running: I'm very new to this, I haven't configured anything besides the IIS. 127.0.0.1 0.0.0.1 (This was already in the file) Still not working. # localhost is used to configure the loopback interface server DNS address could not be found - iis. Eventually, your hosts file will look like something this: # local will do) UPDATE 2011.12.18: If you tab-delimit the vhosts (a rather unknown trick) for the ::1 entry, MAMP won’t delete it when reloading MAMP/adding a new vhost. If you don’t want all the hassle after a restart, you might consider renaming your vhosts to. Note that after restarting MAMP, the IPv6 entries will be gone … yeah, so that bug needs to fixed soon (either by Apple, or by MAMP). Hope to see this fixed in a future version. I’ve created an issue on the MAMP bug tracker for this, requesting the author to automatically add IPv6 entries to the hosts file when creating/editing a vhost. To fix this problem (without having to rename each vhost) you need to add IPv6 entries for each of your vhosts in your /etc/hosts file: ::1 mysite.localĪfter that. This may result in unexpected failures to connect to. By default Mac OS X does not use the DNS server to resolve these names. local domain is not defined as a valid top-level domain on the Internet, some private networks have DNS servers that assign hostnames in the. local is treated as a Bonjour host rather than by querying the DNS server entries in Network preferences. The Multicast DNS feature of Bonjour technology allows devices on a local network to connect to each other by name without a separate DNS server. Turns out, after a few Google Search Coupons, that the culprit is Bonjour (emphasis mine): This makes sense because the DNS lookup process will realize the domain is live, but the server isn’t. If you’d rename the site to v, it’d be - … beware, buzzword coming up … - snappy again. The most tricky part in this issue is that it only happens if you have a domain ending in. An issue I’ve encountered with MAMP Pro since having upgraded to OS X Lion was that requests to vhosts served via MAMP took their time to load: after about 3 to 5 seconds of loading, the site would finally load.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |