...
TODO: develop procedure for renaming the volume group and document here (when / is on LVM as ours normally are, this may require rebuilding the initial RAM disk, re-configuring the boot manager, editing fstab ...). Maybe useful links: https://we.riseup.net/debian/renaming-a-lvm-root-volume-group, https://bugzilla.redhat.com/show_bug.cgi?id=230190#c17 (RedHat),
Name resolution
If all these conditions are met ...
- The name change includes a domain name change.
- /etc/resolv.conf is either a local file or includes a local head or tail file.
- The local file(s) include a domain line.
... then the domain line(s) may need adjusting.
Postfix
Change the postfix configuration
...
- Find which file system it is backed up to and adjust directory name(s) accordingly.
- Adjust directory and symlinks under /var/backup.
DHCP servers
LTSP
...
Not tested (may all be done by the commands above): if running or using any of avahi, CUPS, ejabberd, Exim, /etc/motd, OpenSSH server, ssmtp or sysklogd then read the Debian WIKI page on changing hostname.
LDAP servers
Change the LDAP client's uri
- edit /etc/ldap.conf
- replace the uri=service.av to the appropriate hostname. Note: if the uri=ldapi:/// or anything else of the kind, leave it
- service slapd restart
Change the LDAP Address Book clients
Name resolution
DNS servers
On DNS servers which have record(s) for the old name, change both the forward and reverse data files.
When the hostname of a system on the Blue Light LANs (192.168.10.0 and 192.168.28.0) is changed, the DNS service on backupserver will need re-configuring as documented in DNS server (bind) administration.
/etc/hosts files
On computers with an /etc/hosts file which has record(s) for the old name, change the line
...
LDAP servers
Change the LDAP client's uri
...
.
...
Change the LDAP Address Book clients