[CentOS] Bind fails to start after update from 7.1 to 7.2
Emmett Culley
lst_manage at webengineer.comTue Jan 5 21:03:29 UTC 2016
- Previous message: [CentOS] A query on graphic console
- Next message: [CentOS] Bind fails to start after update from 7.1 to 7.2
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I am seeing these lines for each domain in the systemd journal: zone relationship123.com/IN: loading from master file relationship123.com.db failed: file not found zone relationship123.com/IN: not loaded due to errors. _default/relationship123.com./IN: file not found If I change the zone defs to include the full path: >From zone "relationships123.com." IN { type master; file "relationships123.com.db"; }; To zone "relationships123.com." IN { type master; file "/var/named/chroot/var/named/relationships123.com.db"; }; in the config file, named starts, but then fails to provide DNS replies with the following error for each request: general: error: zone relationships123.com/IN: loading from master file /var/named/chroot/var/named/relationships123.com.db failed: file not found general: error: zone relationships123.com/IN: not loaded due to errors. Nothing was changed in the named configuration prior to updating to 7.2 As usual I am using systemctl start named-chroot to start the server. Any ideas? Emmett
- Previous message: [CentOS] A query on graphic console
- Next message: [CentOS] Bind fails to start after update from 7.1 to 7.2
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the CentOS mailing list