Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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 have a domain for example and use freedns service to add an A record and the destination ip to my webserver. If i try to access or put the ip server into the url all works fine. But after a couple of hours, i can't reach the server through my domain name or through my ip.

I try to access and is now working, i access via the ip of my server and still is not working. I go to the cmd and try ping and is working, i ping ip and is working, please tell me what is wrong.

Problem solved, solution: somebody from my network was searching for ip and mac. And after he found the ip and mac he associated on his computer and he had access to the internet and not i. Now i need i way to hide my mac or my ip so that the user cannot see my mac in the program he use. Thanks for all the anserws.

share|improve this question
Most likely, the freeDNS service requires you to 'refresh' your listing every few hours. – David Schwartz Oct 23 '11 at 19:42
I'll keep hammering on this ancillary point until, well, until people really take it to heart: There is no value at all in obfuscating the domain name in question (""). DNS is publicly published information. Unless you are using the domain strictly on internal, private networks, hiding the domain only forces those whom you would like to help you to guess at what the problem might be. We can't perform even the most basic of DNS diagnostics. It merely wastes your time and ours. – anastrophe Oct 23 '11 at 20:34
@anastrophe: I can imagine his boss not being happy about going extenal with internal problems... – Bart De Vos Oct 25 '11 at 8:35
@BartDeVos, Perhaps, but that really isn't our problem. People come here with their problems, and experts provide answers, free of charge. Obfuscating critical details essentially abuses our goodwill. – anastrophe Oct 25 '11 at 18:23

You say you have a static IP address so you would be better off using a "free static DNS provider" - try putting that term into your favourite search engine.

share|improve this answer

But after a couple of hours, i can't reach the server through my domain name or through my ip.

This, together with the fact that you are able to ping the server, tells me that most likely your web server service (not the server itself) is crashing. Restart the service and check the logs to try and find out why it keeps failing.

share|improve this answer
Like this: sudo /etc/init.d/apache2 restart? Where can i find the service logs? Do you mean /var/log/apache2/error.log? – Oct 25 '11 at 8:32
Yes, like that (assuming you are indeed running Apache). Definitely check the Apache error log(s) and also check the messages log. – John Gardeniers Oct 25 '11 at 8:36
I found this in /var/log/apache2/error.log: [Mon Oct 24 19:01:21 2011] [error] [client] File does not exist: /var/www/ – Oct 25 '11 at 8:45
@mjonutz, that's just a file not found while someone was trying to hack your site. Pretty normal stuff. – John Gardeniers Oct 25 '11 at 11:03

You need to set up a daemon to keep the listing updated, when you use a dynamic DNS service. Check out this guide for example:

share|improve this answer
From your question - are you saying that you can't access the webserver by IP-address either, after a couple of hours? How do you usually fix this? – Kvisle Oct 24 '11 at 17:53

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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