resolvers changed by themselves?

[Secret Agent]

I noticed on two different servers that the /etc/resolv.conf had two different resolvers from the original, both in the same data center and both using the same two new resolvers, both originally using the correct default resolvers.

Somewhere cpanel must have adjusted this. The servers are both in the same colocation facility, same 147.xxxxx resolvers originally and now changed to 69.xxx and both same configs/cpanel etc.

Anyone else notice this? It competely affects mail in/out and cannot even ping to yahoo.com

[Secret Agent]

They were in this order:

69.72.164.156
69.72.164.150
69.72.164.150

That is for pegasus web technology which I have nothing to do with whatsoever. The two servers were also already in stock and been with the same two customers for well over 2 months now.

[chirpy]

I've never seen the resolv.conf file modified by cPanel and I don't see anything that does in /scripts/ - you'd need to ask cPanel if there's anything that they do that would change it.

[Tom Pyles]

Noticed something similar here on different servers in different datacenters

[edesignway]

I had the same thing happen on four of my servers last Friday. It changed to an IP that was not working, so routing from the server out to the world stopped until I found that problem.

[Secret Agent]

Can some cpanel tech confirm this was an actual bug? I don't find it to be anything but an overnight mishap considreing 3 of us reported this so far, same time of occurence as well.

[chirpy]

Can some cpanel tech confirm this was an actual bug?

You've been told before, you have to log it in bugzilla or log a support ticket if you want an answer from cPanel, posting here won't elicit an answer.If you've done neither then they may know nothing about the problem.