Community support for Plesk, CPanel, WebMin and others with insight from two of the founders of Plesk. Ask for help here! No question is too simple or complicated.
We have a container on a hardware node that is attempting to update as it is supposed to. We can ping ka.swsoft.com but it almost always goes to one of our other servers before the gateway and then to swsoft. I don't know what the problem is or how to fix it. I do know that the license is graced.
[root@hw003 etc]# traceroute ka.swsoft.com
traceroute to ka.swsoft.com (64.131.90.38), 30 hops max, 46 byte packets
1 65.44.220.11 (65.44.220.11) 0.133 ms 0.101 ms 0.101 ms
2 65.44.220.1 (65.44.220.1) 0.381 ms 0.212 ms 0.376 ms
3 ip65-46-16-65.z16-46-65.customer.algx.net (65.46.16.65) 0.719 ms 0.385 ms 0.380 ms
4 ge11-1-4d0.mcr1.la-ca.us.xo.net (216.156.11.45) 2.159 ms 2.398 ms 2.271 ms
5 vb1400.rar3.la-ca.us.xo.net (216.156.0.113) 4.491 ms 4.503 ms 3.729 ms
6 207.88.14.218.ptr.us.xo.net (207.88.14.218) 2.342 ms 2.355 ms 2.347 ms
7 ge-11-2-1.mpr1.lax12.us.above.net (64.125.13.17) 2.352 ms 2.354 ms 2.349 ms
8 xe-2-3-0.cr1.lax112.us.above.net (64.125.31.190) 2.553 ms 2.551 ms 2.542 ms
MPLS Label=791026 CoS=0 TTL=85 S=0
9 xe-2-0-0.cr1.iah1.us.above.net (64.125.25.46) 46.927 ms 37.889 ms 37.891 ms
MPLS Label=575101 CoS=0 TTL=85 S=0
10 xe-2-1-0.cr1.dca2.us.above.net (64.125.25.113) 65.966 ms 85.232 ms 65.762 ms
MPLS Label=713014 CoS=0 TTL=85 S=0
11 xe-1-1-0.mpr3.iad1.us.above.net (64.125.31.113) 66.362 ms 66.369 ms 66.162 ms
MPLS Label=380431 CoS=0 TTL=85 S=0
12 xe-0-0-0.mpr4.iad1.us.above.net (64.125.31.106) 66.172 ms 66.153 ms 66.095 ms
MPLS Label=367480 CoS=0 TTL=85 S=0
13 xe-1-1-0.mpr4.iad2.us.above.net (64.125.31.133) 67.130 ms 67.902 ms 67.168 ms
14 64.125.195.222.t00883-02.above.net (64.125.195.222) 66.842 ms 66.991 ms 67.109 ms
15 dl1-si-dc.swsoft.net (64.131.87.10) 68.728 ms 68.937 ms 68.180 ms
16 ix7-si-dc.swsoft.net (64.131.90.221) 67.750 ms 67.930 ms 67.192 ms
There is no reason that I am aware of why we are going to hw001 first. I've checked resolv.conf - okay. I've checked network - okay. I've also checked route and the arp table show .11 listed. Not sure why.
Hmm. Maybe I didn't explain it right. I have one server out of more than 25 that all have the same nameservers. 4.2.2.1 and 4.2.2.2. Only one machine is having issues. It is trying to get to Parallels by going to our 10th virtuozzo server at .11 and then it hits the gateway of .1. All other servers hit the gateway at .1 and straight to ka.swsoft.com.
Thank you for the recourses but I am not getting that message. Actually, the server did update last night.
The question remains why it is trying to hit another server of ours before going outside no matter where.
Changing DNS to OpenDNS in resolve.conf still runs the same route. As to your question I tried that. This is a dedicated server with three Plesk servers on one hardware node. Powerful server.
What is 169.254.0.0 used for? It's on all of my hardware nodes and I assumed associated with Plesk or Virtuozzo. Only this server is having the issue of convoluted DNS routing.
