BIND 10 #1986: b10-auth shouldn't try to forward update requests without ddns running
BIND 10 Development
do-not-reply at isc.org
Tue May 29 03:02:06 UTC 2012
#1986: b10-auth shouldn't try to forward update requests without ddns running
-------------------------------------+-------------------------------------
Reporter: | Owner:
jinmei | Status: new
Type: | Milestone: Next-Sprint-
defect | Proposed
Priority: | Resolution:
medium | Sensitive: 0
Component: | Sub-Project: DNS
b10-auth | Estimated Difficulty: 0
Keywords: | Total Hours: 0
Defect Severity: N/A |
Feature Depending on Ticket: DDNS |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by jinmei):
Now the details and plans of #1985 are not so clear, we'll need to
consider this task independently.
I can think of two options:
1. easy but ad-hoc: introduce a new config option for b10-auth, say,
"use-ddns" to manually control that
2. probably more correct for longer term but will require more work:
have ddns tell auth (or in general anyone who's interested) when
it's ready for accepting requests, and extend auth to dynamically
create the forwarder. With this approach we could also solve #1985
by having b10-ddns include the UNIX socket file path in the
notification.
We'll first need to decide whether, how, when we solve this, and then
need to give it a fresh estimation. I suspect any prior estimations
on this ticket are now useless.
As for "when", my revised suggestion is the hardening sprint.
--
Ticket URL: <http://bind10.isc.org/ticket/1986#comment:2>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list