| Posted by evanpyrz, 11-13-2013, 12:38 AM | | Hey there,
So I have a small VPS setup with cPanel/WHM, Apache etc. Setup be the VPS host when I purchased it, so already configured. I was trying to install Subversion from the command line yesterday and after installing it (no errors) the entire VPS stopped resolving to it's hostname, and all domains hosted under it. I can still access WHM/Cpanel by using the IP address, however I cannot access it through the hostname. If anyone has any ideas, or needs more information to help me out, I would greatly appreciate it! I did try restoring a backup from 2 days prior (to be safe), however that still didn't do it. I'm assuming it's something with the Apache configuration, however looking at it I can't find anything that is sticking out to me.
Server's IP is 66.147.232.74
It's hostname should be phoenix.jetmedia.us
Thanks in advance!
--eric
|
| Posted by FLDataTeK, 11-13-2013, 12:59 AM | | Looks like niether of your NS servers are responding..
NS2.jetmedia.us. ['216.120.248.78'] [TTL=7200]
NS1.jetmedia.us. ['216.120.236.144'] [TTL=7200]
http://www.intodns.com/jetmedia.us
Did you move and not change the NS server IP's to your new server maybe? If so you need to change the IP's for ns1 and ns2 at your registrar.
|
| Posted by net, 11-13-2013, 01:00 AM | | Seems like your main domain is not even properly resolved: http://intodns.com/jetmedia.us
Edit: Jeremy beat me! :-)
|
| Posted by Kailash12, 11-13-2013, 01:01 AM | | It seems that problem with DNS server for jetmedia.us domain. Make sure that there is no problem with the DNS server where jetmedia.us domain's DNS zone is created.
Edit: 2 replies in 2 min
|
| Posted by Joker911, 11-13-2013, 02:28 AM | | Try # /etc/init.d/named restart
|
| Posted by LankapartnerHost, 11-13-2013, 03:17 AM | | It seems you not updated the IPs in domain yet..,
|
| Posted by evanpyrz, 11-13-2013, 12:12 PM | | Jeremy,
Checked with eNom and my nameservers are registered correctly still. Those IPs you listed for me are correct. Where can I check to see if the server is still configured for those IPs? I know the "Nameserver IP" page in WHM is now just a display report and not an actual configuration page. Do I need to manually edit something?
|
| Posted by FLDataTeK, 11-13-2013, 03:52 PM | | I was not able to ping the two ips for the name servers when I was checking. And they still are not.
Pinging 216.120.236.144 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 216.120.236.144:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Pinging 216.120.248.78 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 216.120.248.78:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Here are tracerts from my two looking glass sites to help you..
From Chicago
traceroute to 216.120.248.78 (216.120.248.78), 30 hops max, 40 byte packets
1 chiovzhn01.myservercontrol.com (149.255.32.98) 0.035 ms 0.037 ms 0.013 ms
2 xe-0-1-0.cr1.ord1.us.nlayer.net (69.31.105.37) 0.229 ms 0.211 ms 0.198 ms
3 eqix.chcg.twtelecom.NET (206.223.119.36) 1.551 ms 0.990 ms 1.528 ms
4 aby1-ar1-xe-0-0-0-0.us.twtelecom.net (66.192.242.50) 20.694 ms 20.948 ms 20.365 ms
5 66-162-65-30.static.twtelecom.net (66.162.65.30) 23.458 ms 23.692 ms 23.684 ms
6 * * *
7 * * *
-- Traceroute timed out --
From Jacksonville
traceroute to 216.120.248.78 (216.120.248.78), 30 hops max, 40 byte packets
1 ovz-jax-02.myservercontrol.com (199.102.65.121) 0.092 ms 0.065 ms 0.014 ms
2 68-67-68-93.static.as19844.net (68.67.68.93) 0.543 ms 1.002 ms 1.229 ms
3 198.205.127.45 (198.205.127.45) 0.700 ms 0.957 ms 1.178 ms
4 198.205.127.57 (198.205.127.57) 0.367 ms 0.460 ms 0.491 ms
5 ve101.e2-17.core-a.jcvnflcq.as19844.net (198.205.127.5) 0.386 ms 0.384 ms 0.433 ms
6 ae4-374.edge4.Atlanta2.Level3.net (4.28.182.33) 9.992 ms 9.982 ms 9.967 ms
7 vlan51.ebr1.Atlanta2.Level3.net (4.69.150.62) 25.062 ms vlan52.ebr2.Atlanta2.Level3.net (4.69.150.126) 25.368 ms 25.028 ms
8 ae-73-73.ebr3.Atlanta2.Level3.net (4.69.148.253) 24.905 ms ae-63-63.ebr3.Atlanta2.Level3.net (4.69.148.241) 25.292 ms 25.258 ms
9 ae-2-2.ebr1.Washington1.Level3.net (4.69.132.86) 25.797 ms 24.922 ms 24.724 ms
10 ae-91-91.csw4.Washington1.Level3.net (4.69.134.142) 25.313 ms ae-81-81.csw3.Washington1.Level3.net (4.69.134.138) 25.065 ms ae-61-61.csw1.Washington1.Level3.net (4.69.134.130) 24.625 ms
11 ae-92-92.ebr2.Washington1.Level3.net (4.69.134.157) 25.331 ms ae-82-82.ebr2.Washington1.Level3.net (4.69.134.153) 25.251 ms ae-72-72.ebr2.Washington1.Level3.net (4.69.134.149) 25.005 ms
12 ae-4-4.ebr2.Newark1.Level3.net (4.69.132.102) 25.366 ms 25.006 ms 25.046 ms
13 ae-22-52.car2.Newark1.Level3.net (4.69.156.38) 25.421 ms 25.257 ms 25.107 ms
14 HOSTROCKET.car2.Newark1.Level3.net (4.79.190.46) 38.404 ms 38.905 ms 38.497 ms
15 * * *
16 * * *
-- Traceroute timed out --
|
| Posted by Johnny Cache, 11-14-2013, 12:00 AM | | If you still need support with this, and assuming you still have access to the VM, I'd check /var/log/messages and see which zones are reporting errors (domain.com.db not loaded due to errors) could be that a misconfig is preventing BIND from starting - all the zones are in /var/named however if you do find something to change in the individual zone, you'll want to use the DNS editor in WHM to make/apply the changes.
Doesn't sound like it's Apache related, what with particular IPs not pinging, but you can check /etc/httpd/logs/error_log. Good log to review regularly anyhow.
Also look at the 'ifconfig', 'route' and 'route -n' outputs. You can paste the output here if you need. Wouldn't hurt to look at it.
|
|
 Add to Favourites
 Print this Article
|
