Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am on a VPS that is pretty much unmanaged so it means im on my own. I did my best to configure it so i can host my own site for other people to see it online but seems like i have network problems because in the last days many of my users report they cant enter my site from my domain and seems like Google and Facebook cant either (this never happened before).

Its weird because i can enter my site without problems and so many other people as well. But then i tried to make a php include and i get this error:

Warning: include(): php_network_getaddresses: getaddrinfo failed: Name or service not known in

I was told that seems like my server cant resolve domains. The includes work if i use IPs instead of domains. So it means i have a DNS problem or something? What can i do to fix it? Im on a Linux 2.6.32-431.11.2.el6.x86_64 on x86_64 CentOS Linux 6.5

Thank you.


i have this on my resolv.conf

# Generated by NetworkManager

# No nameservers found; try putting DNS servers into your
# ifcfg files in /etc/sysconfig/network-scripts like so:

share|improve this question

closed as off-topic by Iain, Andrew B, TomTom, Magellan, Sven May 31 '14 at 11:24

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions must demonstrate a minimal understanding of the problem being solved. Try including attempted solutions, why they didn't work, and the expected results. See How can I ask better questions on Server Fault? for further guidance." – Iain, Andrew B, TomTom, Magellan, Sven
If this question can be reworded to fit the rules in the help center, please edit the question.

What's in your /etc/resolv.conf? – Mike Scott May 31 '14 at 6:06
I edited my question with that info. Please check it back. – Nuker May 31 '14 at 6:11
Can you try that again, copying and pasting from a command line session and not from some GUI or web interface. It's impossible to tell what's in the file and what isn't. And use the markup for code to ensure it's formatted properly here. – Mike Scott May 31 '14 at 6:15
I did my best but i cant get it without the bold. Sorry. However i think the important part is below that since everything else is commented out. – Nuker May 31 '14 at 6:21
What did you put in the include() that gave you that error message? – Ladadadada May 31 '14 at 6:32

To me it sounds like all symptoms are pointing at a problem with the authoritative DNS servers for the domain rather than a problem with the server itself.

Looking up the domain name, I find that on the .com servers it is delegated to and There are glue records (but only for IPv4), and the IP addresses of those two DNS servers are not in the same /8. Both DNS servers reply with the same A record, and both are able to report no AAAA record for the domain.

The domain would be unreachable to IPv6-only users, but that is probably not the problem you are facing. At this point I am wondering if you might have two different problems, and the symptoms you see from your own server is caused by something other than the reachability problems, seen from outside.

I looked up the IP address of the server, and found it to be announced by AS16276. That network has a large number of peers, so having no route at all to that network, does not sound like the most likely explanation. It does however mean there are more different paths packets could get routed to your server, and more possibilities for problems affecting a small number of users. (That is sort of a good thing, because you don't want outages to affect all your users). With this knowledge, the next I would look for is traceroute from some of the affected users towards your server as well as traceroute output from your server towards the IP address of those clients.

There is a warning about bogons being announced by AS16276. But it is not related to the IP address of your server, so I don't think that is a problem. I tested traceroute towards your IP from three different networks in two different countries, and I saw no reachability problems. I saw a few routers on the way, which would rarely send time exceeded messages, but that in itself is no problem.

share|improve this answer
So its something i cant fix my self nor my host? – Nuker May 31 '14 at 11:46
@Nuker If you want an answer, you need to give us the information we need. We can't guess what your domain name is, and you haven't told us, what problem your DNS provider has. – kasperd May 31 '14 at 12:28
Thats kinda sensitive information. Can I tell you by PM or something? – Nuker May 31 '14 at 12:46
@Nuker The point of serverfault is that others with the same problem can lookup the answer, which in this case would include the steps involved in debugging. So the answer would include the domain name. Be aware that when somebody try to reach your site, the domain name is sent in clear over the Internet. If the domain name itself is sensitive, then you should really focus on fixing the systems which assumed a domain name could be kept secret. – kasperd May 31 '14 at 12:52
Okay, here you go: i would appreciate your help. I tried all and im getting out of ideas. – Nuker May 31 '14 at 13:03

Not the answer you're looking for? Browse other questions tagged or ask your own question.