Hello guys, on my droplet with Ubuntu Server 16.04 i have problems with connectivity. I receive the connection timeout error randomly. For example, if I run the command $ host -v www.google.com I get this:
# host -v www.google.com
Trying "www.google.com"
;; connection timed out; no servers could be reached
If I do it again, I receive this:
# host -v www.google.com
Trying "www.google.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57226
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;www.google.com. IN A
;; ANSWER SECTION:
www.google.com. 129 IN A 74.125.206.105
www.google.com. 129 IN A 74.125.206.99
www.google.com. 129 IN A 74.125.206.106
www.google.com. 129 IN A 74.125.206.103
www.google.com. 129 IN A 74.125.206.104
www.google.com. 129 IN A 74.125.206.147
Received 128 bytes from 67.207.67.3#53 in 0 ms
Trying "www.google.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47207
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;www.google.com. IN AAAA
;; ANSWER SECTION:
www.google.com. 53 IN AAAA 2a00:1450:4001:81c::2004
Received 60 bytes from 67.207.67.2#53 in 0 ms
Trying "www.google.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2163
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;www.google.com. IN MX
;; AUTHORITY SECTION:
google.com. 59 IN SOA ns1.google.com. dns-admin.google.com. 191054502 900 900 1800 60
Received 82 bytes from 67.207.67.3#53 in 0 ms
I can not understand what causes this behavior. Also to log in with ssh to the droplet I have to do 3 or more attempts before succeeding, i hope you can help me. Thank you and sorry for the bad english.
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!
This comment has been deleted
Hello there,
This sounds like a possible local issue. However, you can always check our status page for any planned maintenance or service outages.
https://status.digitalocean.com/
You can first verify if the issue occurs only when trying to reach your droplet and then reach other resources from it or if you’re experiencing the issue with other providers.
This will be the starting point for your investigation since this might be a temporary problem from your ISP or some DNS issue.
Regards
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.