Here's the situation: my company runs a website, but we don't have anybody in-house qualified to be a sysadmin, so when something goes awry, we're very much at the mercy of our hosting provider's helpdesk.* We're having a severe problem with our server, and I need some help sorting it out.
(* -- Yes, this is a terrible position to be in, and at the very least we should have a plan where our host explicitly provides sysadmin support.)
From the perspective of the internet, our site is dead; all attempts to access OurWebsite.com** time out, whether it's via HTTP, SSH, FTP, Ping, email, etc.
(** -- Not our actual name.)
Some digging has revealed that we have two IPv4 addresses: x.x.x.217 and x.x.x.225, both of which apparently have been pointing to the same server. I can access the server via 217 address just fine; however, the 225 address appears to be stone dead.
More digging confirms that the DNS entry for OurWebsite.com is pointing to the 225 address. This explains the behavior I'm seeing, at least.
So here's my primary question: What do I do to fix this? How do I get the 225 address working again?
Also of interest, but less pressing: What could have caused this? Everything was working just fine as recently as last night, but when I tried to access the server this morning, it appeared to be stone dead until I specifically used the 217 address.
Edit: Some details about the server: It's a dedicated server (we have it all to ourselves) running Fedora 8. It's hosted by GoDaddy, so I don't have physical access to the box.