Zone files are written to the local file system to reflect the host name resolution data administered on the Local Host Name Resolution page. The Security Module uses this data when performing DNS resolution.
A Zone File I/O alarm indicates that an error occurred while trying to access the file system to read or write data for zone files. Possible causes include:
Missing directories.
Permission errors.
No space on the disk.
Other errors that cause failure in the attempt to read or write to the zone files.
Troubleshooting Zone File I/O Alarms
About this task
To troubleshoot the error, you must log on using the root user.
Procedure
Verify that the master directory exists:
Enter ls -ltr /var/named/ | grep master.
If the directory does not exist, enter mkdir /var/named/master.
Check the /var/named/master directory for problems such as missing, permission errors:
Enter ls -ltr /var/named/ | grep master.
The output should be similar to drwxr-x--x 2 root root 4096 Apr 16 11:52 master.
If the permissions are not drwxr-x--x, enter chmod 751 /var/named/master.
If the file ownership is not root, enter chown root /var/named/master.
If the group is not root, enter chgrp root /var/named/master.
Ensure there is enough space on the disk:
Enter df.
If the Use% value is greater than 95%, remove any unnecessary large and old log files on the system.
First check the log files in /var/log/Avaya/sm and ensure their size is not too large more than 100 MB.
Ensure that the file /etc/named.nre.zones exists:
Enter ls -l /etc/named.nre.zones
The output should be similar to -rw-r--r-- 1 root root 219 Apr 16 11:52 /etc/named.nre.zones
If the file does not exist, create the file with the command > /etc/named.nre.zones
If the permissions are not -rw-r--r--, enter chmod 644 /etc/named.nre.zones
If the file ownership is not root, enter chown root /etc/named.nre.zones
If the group is not root, enter chgrp root /etc/named.nre.zones
If the above steps do not solve the problem, contact Avaya Technical Support.
