BIND 10 #675: xfrin can't have a default master for all zones
BIND 10 Development
do-not-reply at isc.org
Mon Mar 7 19:55:53 UTC 2011
#675: xfrin can't have a default master for all zones
------------------------------------+---------------------------
Reporter: jreed | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: xfrin | Resolution:
Keywords: | Sensitive: 0
Estimated Number of Hours: 0.0 | Add Hours to Ticket: 0
Billable?: 1 | Total Hours: 0
Internal?: 0 |
------------------------------------+---------------------------
Description changed by jreed:
Old description:
> src/bin/xfrin/xfrin.py.in has:
>
> DEFAULT_MASTER = '127.0.0.1'
>
> My zone kept attempting to do a SOA check from the default master. Note
> this is hardcoded as the spec has an empty "" configuration for this.
>
> In my case this causes continuous SERVFAILs.
>
> The spec configuration should be removed. The default hardcoded
> configuration should be removed.
>
> (This is related to #670 -- it should even attempt to do a refresh if is
> not configured as a secondary zone.)
New description:
src/bin/xfrin/xfrin.py.in has:
DEFAULT_MASTER = '127.0.0.1'
My zone kept attempting to do a SOA check from the default master. Note
this is hardcoded as the spec has an empty "" configuration for this.
In my case this causes continuous SERVFAILs.
The spec configuration should be removed. The default hardcoded
configuration should be removed.
(This is related to #670 -- it should not attempt to do a refresh if is
not configured as a secondary zone.)
--
--
Ticket URL: <http://bind10.isc.org/ticket/675#comment:1>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list