In the previous article, we used powerdns's own pdns.conf configuration to implement dual backup of the domain name resolution service of master and slave. However, in actual production and use, we find that individual records or domains often fail to achieve strict synchronization between master and slave, resulting in domain name service errors.
Therefore, I updated the two domain name servers ns1.happytang.org and ns2.happytang.org and configured them as mater. But in order to keep the records of the two name servers strictly consistent, we used mysql master-slave synchronization.
For specific principles, see this blog post by Claudio Kuenzler .
mysql master-slave synchronization see this blog post .
This is just to record the problems encountered in the middle.
1. In the process of configuring master-slave synchronization, 3306 of master_port does not need to add single quotes.
2. The server id of the middle slave was changed but mysql was not restarted, causing slave_io to appear no. It will be fine after restarting.
3. Our master server was using oneinstack at the time. When configuring mysql master-slave distribution, my.cnf file was not found. After reviewing, in the 5.7 version of mysql, some compiled versions do not have my.cnf by default. You can create my.cnf by yourself. At least, you should add four parameter settings of datadir, basedir, log-bin and server-id under the [mysqld] field in my.cnf.
4. In powerdns, we found that occasionally the MX records of individual domain names do not take effect, but they can be added again after deletion.
The original text has also been posted on the corresponding page of the personal blog .