Submitted by Shirehosting on Sun, 03/22/2015 - 02:59 Pro Licensee
Hi Guys,
We renamed one of our servers from X to Y but for some reason while the servers new name of Y is what it is responding to BIND seems to have not changed over, is there anything we may have missed in the hostname change process?
Cheers
Peter
Status:
Closed (fixed)
Comments
Submitted by andreychek on Sun, 03/22/2015 - 08:55 Comment #1
Howdy -- if you changed the hostname, you'd want to verify that your new hostname is listed in /etc/hosts, as well as on the mydestination line in /etc/postfix/main.cf.
Submitted by Shirehosting on Thu, 03/26/2015 - 06:41 Pro Licensee Comment #2
Hi
Took a look at the above and whilst I did find the wrong host name in the postfix main.cf, I made the change restarted both bind and postfix but the old hostname is still being produced in the new zones.
So just to recap. I have VM pro called x.name.com.au was called a.name.com.au and 2 slave DNS servers both gpl called y.name.com.au and w.name.com.au
Issue is we changed the host name on the pro version and now every time we add a new virtual server the old host name is entered as a NS server (a.name.com.au) along with y and w (which is ok)
I have looked everywhere and cant for the life of me see where the old hostname is hiding
Any suggestions gladly accepted.
Thanks Michael
Submitted by andreychek on Thu, 03/26/2015 - 10:16 Comment #3
Hmm, you may want to double-check that you don't see the old name in System Settings -> Server Templates -> Default -> BIND DNS Domain.
There's a few fields on that screen which could potentially cause what you're describing.
Submitted by Shirehosting on Thu, 03/26/2015 - 19:09 Pro Licensee Comment #4
Thanks you, this was exactly the problem.
Thanks Michael
Submitted by Shirehosting on Thu, 03/26/2015 - 19:10 Pro Licensee Comment #5