up vote -4 down vote favorite
share [g+] share [fb]

After configuring a domain name to use the name server of the new server, the new server had become inaccessible (even if using the IP address). Is this normal?

link|improve this question
25% accept rate
You might consider providing some details as to what was literally changed - with the DNS records? – user48838 Aug 14 '11 at 23:11
2  
No this is not "normal". What response do you get from typing NSlookup and the server name at the command prompt? – Fergus Aug 14 '11 at 23:16
Do you have local access to this server? If so can you ping/check websites/other servers? If you cannot ping any other servers its probably a network issue. have you checked the logs to see what errors are there? Is this Windows or Linux? – tkrabec Aug 15 '11 at 1:24
feedback

closed as not a real question by Iain♦, Scott Pack, MikeyB, Shane Madden, womble Aug 15 '11 at 21:20

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. See the FAQ for guidance on how to improve it.

2 Answers

up vote 3 down vote

To directly answer your question, the answer is no.

If you can't access one of your servers, even by IP address, you have a larger issue that goes outside of the scope of DNS.

link|improve this answer
feedback
up vote 0 down vote

did accessing the new server by IP address work before the change? What makes you think it's actually up?

I figure one of two things is happening:

  • Your 'new server' is an Apache virtual host and can only be accessed by name. When accessing it by IP, it doesn't know which host it's supposed to be. To check for this, put the hostname and IP into your hosts file.
  • Your 'new server' is down. Nothing to do with your DNS change.
link|improve this answer
feedback

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