![](https://pdfstore-manualsonline.prod.a.ki/pdfasset/3/fb/3fb688d4-bc6a-4479-a5b4-ca066e971a2c/3fb688d4-bc6a-4479-a5b4-ca066e971a2c-bg89.png)
Chapter 7 Ongoing System Management 137
MySQL
In general, MySQL is not aected by changing an IP address or DNS name. However,
none of the data in the databases is altered when the DNS name or IP address are
changed. You are responsible for replacing references to the DNS name and address
(if used) in your databases.
If you set a database root password, there might be entries in the database GRANT
table (database=mysql, table=user) that refer to the previous server DNS name. In this
case, use Server Admin to reset the root password, which will then reect the current
server identity.
Server administrators should make sure that MySQL clients that have saved references
to the DNS name of the MySQL Service are updated to reect any change in the server
identity.
QTSS
The typical default conguration will not need further conguration after changing
the DNS name or IP address of QTSS. If you congured specic IP bindings, change
those to the new address and restart the service. Relays you dened might have
invalid IP addresses after an IP address change.
Wiki
Wiki service remains unaected by a change in the IP address, assuming Apache is still
functioning and DNS names change.
However, wikis can be congured to specic DNS names. If you manually edited
conguration les to restrict wiki access to DNS names, make the relevant changes in
those les.
Certicates for Web and Wiki Services
Web and wiki servers that use SSL will need new certicates. You might need to
regenerate or repurchase the certicates. You must use Server Admin to import the
new certicates, then congure each service’s, or site’s, new certicate.
Understanding IP Address or Network Identity Changes on File
Services
File services provide le storage and retrieval for network clients. File services include:
AFP Â
SMB Â
NFS Â
FTP Â