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 can't access my website, the DNS fails at a certain point.

I don't understand much of this stuff, so I hope someone can give a simple answer for this question: Can I fix it even if it is a temporary solution? How?

I believe these questions are the exact thing that is happening to me

C:\> tracert

16 ( )
17 ( )
18 * * * Request timed out.
19 * * * Request timed out.
30 * * * Request timed out.

If I am missing any info let me know...



DNS request timed out.
    timeout was 2 seconds.
Server:  UnKnown
Address:  fe80::29d3:9dff:56ed:1b1d

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to UnKnown timed-out



Pinging [] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Accessing the page

The connection has timed out
The server at is taking too long to respond.

Of note: It was working just fine until Sunday morning, when it sundently started to behave like this.

share|improve this question
up vote 3 down vote accepted

dns lookup is resolving to:

what you're doing is not dns. you are tracing the server hops to get to wherever your site is hosted.

not all servers will respond to a ping, and not all ipaddresses will resolve to a domain name

to test dns resolution use on a windows box: nslookup

if this is not working in all locations, be patient, dns can take a fair while to replicate around the world.

if after 48 hours it is still failing, get in contact with your domain name host or registar.

after your update:

check this url for lookup information:

it looks like your dns on your machine is a bit funky.

that you're able to do a tracert suggests that the dns is resolving to an IP address ok.

what do you get if you just do: ping

also, what do you get when you open the page in a web browser.

i get an apache config page from here, so i would suggest the issue is somewhere on your LAN.

share|improve this answer
See Update2... With a ping I get 100% packet loss, accessing the page I get that the page is taking too long to respond, the same happens to that ip address... Is it the DNS from my machine? What could I do about it? – BrunoLM Jun 28 '10 at 9:48
I solved by changing the DNS from my router to Google's DNS and then rebooted the router. I will accept your answer because it helped me to understand a bit more and helped me to find the problem! Thanks! – BrunoLM Jun 28 '10 at 21:56

Based on your update it looks like there is indeed a DNS issue but your first problem is to determine at what point that error is, because it might just as easily be on your own machine. Start systematically eliminating links in the chain. Start at the DNS server, checking firstly that you do in fact have the correct entries, and work back to your machine until the lookup fails.

share|improve this answer

Your web site and the DNS servers are all on the same subnet ( - 244). This is a single point of failure.

That network had some connectivity issues (I can't reproduce them now) so not only did your site stop responding, but for some the domain would have stopped resolving too. This would also cause inbound e-mail to bounce instead of queue.

Invest in some diverse DNS hosting, so that your DNS continues to work even if the main web hosting goes down. A google search for "secondary DNS provider" should reveal plenty.

share|improve this answer

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.