Our current workaround is to add the following to NAMED configuration: check-names master ignore;
Is there a more preferred solution? …or perhaps a different way of looking at this issue? — Raymond Walker Software Systems Engineer StSp. ITS - Northern Arizona University From: Ray Walker <ray.wal...@nau.edu<mailto:ray.wal...@nau.edu>> Date: Monday, June 9, 2014 at 11:47 AM To: "bind-users@lists.isc.org<mailto:bind-users@lists.isc.org>" <bind-users@lists.isc.org<mailto:bind-users@lists.isc.org>> Subject: Bad owner name on hidden primary Running BIND 9.9.5: On moving to a hidden primary setup, dynamic updates to zones we are master for with “unallowed characters” (underscores in our case) have started to fail with the error "bad owner name (check-names)” In the past (pre hidden primary) they did not fail. In the past we have not used the ‘check-names’ option, so behavior should be default… odd since the default behavior is to fail for master zones. Could this have something to do with the SOA of the zone no longer being the actual primary? — Raymond Walker Software Systems Engineer StSp. ITS - Northern Arizona University
_______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
