Otdfbt

Output the ŋarâþ crîþ alphabet song without using (m)any letters

How to tell that you are a giant?

Check which numbers satisfy the condition [A*B*C = A! + B! + C!]

How to deal with a team lead who never gives me credit?

What is Arya's weapon design?

Overriding an object in memory with placement new

Is it ethical to give a final exam after the professor has quit before teaching the remaining chapters of the course?

What causes the vertical darker bands in my photo?

Why is "Consequences inflicted." not a sentence?

What's the meaning of 間時肆拾貳 at a car parking sign

What does an IRS interview request entail when called in to verify expenses for a sole proprietor small business?

How to run gsettings for another user Ubuntu 18.04.2 LTS

How to find out what spells would be useless to a blind NPC spellcaster?

How to find all the available tools in mac terminal?

Why is my conclusion inconsistent with the van't Hoff equation?

Withdrew £2800, but only £2000 shows as withdrawn on online banking; what are my obligations?

Can an alien society believe that their star system is the universe?

Do I really need recursive chmod to restrict access to a folder?

What to do with chalk when deepwater soloing?

Is there a problem creating Diff Backups every hour instead of Logs and DIffs?

Why did the IBM 650 use bi-quinary?

Bete Noir -- no dairy

How do I keep my slimes from escaping their pens?

Why was the term "discrete" used in discrete logarithm?

Webserver turned off for a long time, on boot up the sites(s) dont resolve to domain [on hold]

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;

-1

We have a centOS server that was switched off for at least three months. We have three domains pointed to it and on starting the server a week ago only one of the domains has become available.

The server is a centOS box running Apache, we have three vhosts files all fairly identical (except directory names obviously) serving content from /var/www/html/. The server sits on AWS as an EC2 instance and the domain that isn't working was bought via Route 53.

Firstly the domain that was working was bought on Godaddy and simply updating the A Record's IP Address enough to bring it back to life.

The main problem is the domain bought via Route 53 doesn't seem to work, I have updated the A Record and I can see the Name Servers via a whois etc but any attempt to view the website via www.domain.com doesn't open a page. The browser simply states:

server IP address could not be found.

I have tried pinging www.domain.com and it supports the above message, simply stating it could not find the host.

Apache is definately being served and there are no errors in the logs. The EC2 address resolves to the apache test page as expected ( the vhosts would resolve the websites).

Anyone point me in a direction to help, I am already considering recreating the website(s) from scratch but one of them will take a bit of time and cost a little money, I just hoped to use this as a landing page for a short term.

Edit: Screenshot:

domain-name-system web-server apache2

share|improve this question

edited Apr 11 at 15:46

n34_panda

asked Apr 11 at 11:10

n34_pandan34_panda

1294

put on hold as off-topic by Jenny D, womble♦ 2 days ago

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

• "Questions seeking installation, configuration or diagnostic help must include the desired end state, the specific problem or error, sufficient information about the configuration and environment to reproduce it, and attempted solutions. Questions without a clear problem statement are not useful to other readers and are unlikely to get good answers." – Jenny D, womble

If this question can be reworded to fit the rules in the help center, please edit the question.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I've never seen a browser which gives that error. Did you translate it yourself from another language? What browser is it? What are the domain names?
  
  – Michael Hampton♦
  Apr 11 at 15:18
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I have added a screenshot usually it relates to local PC problems, recommended things like flushing DNS, resetting network adapter etc. Unfortunately I've checked via a VPN and mobile device and I am 99.9999% certain it's a fault on the web server (or route to it).
  
  – n34_panda
  Apr 11 at 15:47
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  NXDOMAIN means the name wasn't found in the DNS. Check your DNS records. And again, what is the domain name?
  
  – Michael Hampton♦
  Apr 11 at 17:57
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Hi, I managed to solve the problem. The AWS Route 53 record set must have been "confused". Not very technical term but if your familiar with AWS I essentially deleted all DNS records, deleted the Hosted Zone and then recreated it. It used new name servers and within 5 minutes was loading the site up.
  
  – n34_panda
  Apr 12 at 19:32
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @MichaelHampton I managed to get it working, the registered domain's name servers didn't match the name servers of the hosted zone in AWS Route 53. Once I had contacted the domain company to set the correct ones it is now working as expected.
  
  – n34_panda
  yesterday
  

  
  
  
  

add a comment | 

-1

We have a centOS server that was switched off for at least three months. We have three domains pointed to it and on starting the server a week ago only one of the domains has become available.

The server is a centOS box running Apache, we have three vhosts files all fairly identical (except directory names obviously) serving content from /var/www/html/. The server sits on AWS as an EC2 instance and the domain that isn't working was bought via Route 53.

Firstly the domain that was working was bought on Godaddy and simply updating the A Record's IP Address enough to bring it back to life.

The main problem is the domain bought via Route 53 doesn't seem to work, I have updated the A Record and I can see the Name Servers via a whois etc but any attempt to view the website via www.domain.com doesn't open a page. The browser simply states:

server IP address could not be found.

I have tried pinging www.domain.com and it supports the above message, simply stating it could not find the host.

Apache is definately being served and there are no errors in the logs. The EC2 address resolves to the apache test page as expected ( the vhosts would resolve the websites).

Anyone point me in a direction to help, I am already considering recreating the website(s) from scratch but one of them will take a bit of time and cost a little money, I just hoped to use this as a landing page for a short term.

Edit: Screenshot:

domain-name-system web-server apache2

share|improve this question

edited Apr 11 at 15:46

n34_panda

asked Apr 11 at 11:10

n34_pandan34_panda

1294

put on hold as off-topic by Jenny D, womble♦ 2 days ago

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

• "Questions seeking installation, configuration or diagnostic help must include the desired end state, the specific problem or error, sufficient information about the configuration and environment to reproduce it, and attempted solutions. Questions without a clear problem statement are not useful to other readers and are unlikely to get good answers." – Jenny D, womble

If this question can be reworded to fit the rules in the help center, please edit the question.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I've never seen a browser which gives that error. Did you translate it yourself from another language? What browser is it? What are the domain names?
  
  – Michael Hampton♦
  Apr 11 at 15:18
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I have added a screenshot usually it relates to local PC problems, recommended things like flushing DNS, resetting network adapter etc. Unfortunately I've checked via a VPN and mobile device and I am 99.9999% certain it's a fault on the web server (or route to it).
  
  – n34_panda
  Apr 11 at 15:47
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  NXDOMAIN means the name wasn't found in the DNS. Check your DNS records. And again, what is the domain name?
  
  – Michael Hampton♦
  Apr 11 at 17:57
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Hi, I managed to solve the problem. The AWS Route 53 record set must have been "confused". Not very technical term but if your familiar with AWS I essentially deleted all DNS records, deleted the Hosted Zone and then recreated it. It used new name servers and within 5 minutes was loading the site up.
  
  – n34_panda
  Apr 12 at 19:32
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @MichaelHampton I managed to get it working, the registered domain's name servers didn't match the name servers of the hosted zone in AWS Route 53. Once I had contacted the domain company to set the correct ones it is now working as expected.
  
  – n34_panda
  yesterday
  

  
  
  
  

add a comment | 

We have a centOS server that was switched off for at least three months. We have three domains pointed to it and on starting the server a week ago only one of the domains has become available.

The server is a centOS box running Apache, we have three vhosts files all fairly identical (except directory names obviously) serving content from /var/www/html/. The server sits on AWS as an EC2 instance and the domain that isn't working was bought via Route 53.

Firstly the domain that was working was bought on Godaddy and simply updating the A Record's IP Address enough to bring it back to life.

The main problem is the domain bought via Route 53 doesn't seem to work, I have updated the A Record and I can see the Name Servers via a whois etc but any attempt to view the website via www.domain.com doesn't open a page. The browser simply states:

server IP address could not be found.

I have tried pinging www.domain.com and it supports the above message, simply stating it could not find the host.

Apache is definately being served and there are no errors in the logs. The EC2 address resolves to the apache test page as expected ( the vhosts would resolve the websites).

Anyone point me in a direction to help, I am already considering recreating the website(s) from scratch but one of them will take a bit of time and cost a little money, I just hoped to use this as a landing page for a short term.

Edit: Screenshot:

domain-name-system web-server apache2

share|improve this question

edited Apr 11 at 15:46

n34_panda

asked Apr 11 at 11:10

n34_pandan34_panda

1294

server IP address could not be found.

share|improve this question

edited Apr 11 at 15:46

n34_panda

asked Apr 11 at 11:10

n34_pandan34_panda

1294

share|improve this question

edited Apr 11 at 15:46

n34_panda

asked Apr 11 at 11:10

n34_pandan34_panda

1294

asked Apr 11 at 11:10

n34_pandan34_panda

1294

asked Apr 11 at 11:10

n34_pandan34_panda

1294