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 am a developer and have virtually no experience configuring a server. I configured Route 53 and my registrar to point to it. Created 3 A record sets to point to my instance elastic ip.

When I dig my domain (or open it in lynx) it all works normal. However, from the outside world nothing seems to happen.

I should mention that the elastic ip opens in the browser, no problem. The domain is

Any clues would be highly appreciated.. Thnx

share|improve this question

Looks like it's mostly made its way around the world.

DNS changes can take time to show up on different networks because of DNS records' TTL (time-to-live).

share|improve this answer
I'm not sure why, but when I open it from inside, using lynx it shows me apache IT WORKS page. Which is the desired behaviour for now. From outside, I get nothing. – user171478 Apr 27 '13 at 21:30
Define "nothing". Domain not found? Empty page? – ceejayoz Apr 27 '13 at 22:09
chrome's This webpage is not available. – user171478 Apr 27 '13 at 22:12
Chrome's "this webpage is not available" usually has more details at the bottom on the exact error. – ceejayoz Apr 27 '13 at 22:14
The server at can't be found, because the DNS lookup failed. DNS is the network service that translates a website's name to its Internet address. This error is most often caused by having no connection to the Internet or a misconfigured network. It can also be caused by an unresponsive DNS server or a firewall preventing Google Chrome from accessing the network. – user171478 Apr 27 '13 at 22:34

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.