-
Notifications
You must be signed in to change notification settings - Fork 127
Troubleshooting
The following are a list of common troubleshooting issue and the solution for them. If you have an issue that isn't resolvable by any of the information below, feel free to open an issue to request some assistance.
For support, please open an issue via the tracker.
This is by design - if using NamedManager, you should configure your webserver to use SSL as you're dealing with some data that you really don't want to expose.
If you absolutely understand what you're doing and want to force SSL redirect off (A valid case is when running the application behind an SSL terminator), you can do so, by adding the following to the config.php file:
$_SERVER['HTTPS'] = "TRUE";
If using LDAP, note that only members of the “namedadmins” group are permitted to login to NamedManager – check that you have been assigned to this group.
As per RFC 952 and 1123, underscores are not a valid character for domain names. Some name servers will sometimes allow it, but it's not standard and can break things.
NamedManager will not accept underscores for this reason; use a hypen/dash instead.
In this case you should break the network into /24 chunks with a domain record per chunk. This makes management easier since you have at most 254 records on a domain.
First, check if the new record is appearing on the bind name server. If it isn't, then see the question below for debugging information.
Otherwise it's most likely a caching issue on your computer or on a DNS server between yourself and the ones controlled by NamedManager.
Try querying the record using the host command on the name server itself to verify if this is the case.
Whenever a change is made to the NamedManager configuration, it needs to be pulled down by all the name servers, the zone files written and bind reloaded.
This process can take up to a minute however the status can be checked using the “Name Servers” page, where the synchronisation status is shown.
If configuration is not being delivered to a bind server and is remaining unsynchronised, check that:
- Cron is running on the server.
- The namedmanager_config_writer.php script is being called by cron every minute.
Enable debugging in /etc/namedmanager/config-bind.php and run the script manually, to get a debug log report of the problem. It could be an issue like an incorrect API key or being unable to reach the server, eg firewall problem.
If you aren't getting logs from the bind name servers, open up the name server's details page and get more information regarding synchronisation including the last sync time.
You can access the full synchronisation status by Name Servers -> View Name Servers -> details, for both logs and configuration.
If logs are still not coming through, check that the namedmanager_logpush.php process is running on the bind server, this can be started/restarted with the /etc/init.d/namedmanager_logpush bootscript.
If logging is dying or hanging on a regular basis, it may be that the logrotate.d configuration on the server is rotating the log file and the NamedManager logpush process is still watching the old log file.
If this is the case, there are two ways to resolve this issue:
- Set logrotate to use the copytruncate method of log rotation
- Adjust configuration to restart the NamedManager logging process
Zonefile import is a complicated function that has to deal with variable human-written files in order to import. Sometimes problems occur; this section details some common/known ones.
NamedManager supports a subset of all the domain record types available, there may be some types that cannot be managed by NamedManager yet. If you come across this, check if you can actually accomplish the same job with the SRV or TXT record types.
Patches to add support for missing record types, or to improve the support for the ones we already have, are welcome.
NamedManager will have problems importing round-robin records when in the form of:
www IN A 192.168.1.1
IN A 192.168.2.1
This is due to NamedManager being unable to match the second RR record to the first due to an importer limitation.
The unmatched record will be reported in the import utility, enabling an administrator to add them again after the import.
If attempts to import large zone files fail, you may need to increase PHP limitations on number of POST variables.
These failures can manifest themselves as weird validation errors complaining about missing values due to the way PHP cuts off input mid stream.
The fix is to adjust the following and restart httpd:
max_input_vars = 5000,
If you are using additional security layers, such as Suhosin, you will need to update those, eg:
suhosin.post.max_vars = 5000
suhosin.request.max_vars = 5000