By default, my droplet (Ubuntu 13.04 x64) was set up with two DNS servers in resolv.conf: 18.104.22.168 and 22.214.171.124. In debugging why my client requests to Twilio were slow or failing, I found out that host resolution was timing out half the time and eventually discovered that 126.96.36.199 is not responding to queries from my droplet:
dierks@sharkodile:~$ host api.twilio.com 188.8.131.52 ;; connection timed out; no servers could be reached
It works from my desktop in my office:
~ $ host api.twilio.com 184.108.40.206 Using domain server: Name: 220.127.116.11 Address: 18.104.22.168#53 Aliases: api.twilio.com is an alias for public-vip374d1ca4e.prod.twilio.com. public-vip374d1ca4e.prod.twilio.com is an alias for ec2-174-129-254-101.compute-1.amazonaws.com. ec2-174-129-254-101.compute-1.amazonaws.com has address 22.214.171.124
This could be specific to my droplet or to DO. It’s not a big concern for me (I just replaced 126.96.36.199 with 188.8.131.52 in my config; Level3 apparently doesn’t want the public using 184.108.40.206 in the first place), but I thought I’d see if anyone else was seeing this problem and possibly contribute if anyone else is trying to debug similar problems.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
Click below to sign up and get $100 of credit to try our products over 60 days!