resolv.conf being overwritten at startup

[ichiew]

Hello.

I've noticed that when my VE starts up, /etc/resolv.conf gets replaced with one pointing to JPC's default nameservers. This breaks applications which have to do lookups against a locally-running private nameserver. /etc/hostname is also replaced, changing the hostname back to the default of "vps". This also causes problems. (In particular, it breaks MySQL replication.)

Is there a way to disable this behaviour at VE startup?

[thisisit3]

I believe VZPP is doing it, if thats true then open a ticket and ask for tech support to disable that feature. if don't know if such a setting is VPS-specific or affects the entire node.

Also, it shouldn't replace the /etc/hostname with the default "vps.", in theory when you change your hostname you notify tech support and they update their records with your new hostname, maybe a tech didn't follow the correct procedure and your VZPP isn't aware of your new hostname?

[JPC-Masood]

Hello.

I've noticed that when my VE starts up, /etc/resolv.conf gets replaced with one pointing to JPC's default nameservers. This breaks applications which have to do lookups against a locally-running private nameserver. /etc/hostname is also replaced, changing the hostname back to the default of "vps". This also causes problems. (In particular, it breaks MySQL replication.)

Is there a way to disable this behaviour at VE startup?

hostname, resolv.conf need to be setup via node. You should not modify them. Please have them setup via support ticket what you want them to be. And your billing account need to match with your vps hostname.