search

elm-lang / elm-package

Command line tool to share Elm libraries
BSD 3-Clause "New" or "Revised" License
213 stars 66 forks source link

package.elm-lang.org DNS lookups failing #282

Closed keithasaurus closed 7 years ago

keithasaurus commented 7 years ago

https://www.whatsmydns.net/#A/elm-lang.org

The link above should show a lack of ability to resolve the IP for elm-lang.org in several places. Was there an IP change?

Practically, I'm unable to install packages, and a curl yields the following:

curl http://package.elm-lang.org
curl: (6) Could not resolve host: package.elm-lang.org

I didn't see a place for submitting issues on the website, so apologies if this is the wrong place.

process-bot commented 7 years ago

Thanks for the issue! Make sure it satisfies this checklist. My human colleagues will appreciate it!

Here is what to expect next, and if anyone wants to comment, keep these things in mind.

hauntedhost commented 7 years ago

My CI server is also reporting a DNS failure:

Error: The following HTTP request failed.
<http://package.elm-lang.org/all-packages?elm-package-version=0.18&since=2017-08-24%2019%3A44%3A12.624292%20UTC>
FailedConnectionException2 "package.elm-lang.org" 80 
False getAddrInfo: does not exist (Temporary failure in name resolution)

Interestingly the URL http://package.elm-lang.org/all-packages?elm-package-version=0.18&since=2017-08-24%2019%3A44%3A12.624292%20UTC returns null 👀

Whereas truncating the timestamp from the URL returns a payload: http://package.elm-lang.org/all-packages?elm-package-version=0.18&since=2017-08-24

keithasaurus commented 7 years ago

@somlor FWIW you can do a temp fix by adding this line to /etc/hosts 107.170.159.76 package.elm-lang.org

oppai commented 7 years ago

package.elm-lang.org is hosted by DreamHost. http://elm-lang.org.w3lookup.net/

DreamHost has any problems about connection. https://twitter.com/DreamHostCare/status/900855897383202816

I have same issue that cant resolve domain from AWS.

evancz commented 7 years ago

The root issue was the DreamHost DNS was having trouble today. Migrating to a different DNS seemed like a bad way to approach the issue, so there was no practical action to take. Like I shared on Slack, you can work around it by using the hosts file idea that @keithasaurus mentioned.