Fix stubzone retention (#198)
Make the receiver a pointer so that the uptdateStubZones map update will retain the stubzones found, unlike the current case where the update will be applied and then promptly forgotten, because it is working on a copy. Add test/etcd_test.go to test a large part of the code. This didn't catch the chaos middleware hack though. The chaos middleware zones are now *not* automatically added. You have to take care of that by yourself (docs updates). When using debug queries and falling through to the next middleware in etcd, restore the original (with o-o.debug) query before passing it on.
This commit is contained in:
parent
c079de65b5
commit
ad76aef5fc
18 changed files with 210 additions and 104 deletions
|
@ -21,6 +21,7 @@ func (p RRSet) Len() int { return len(p) }
|
|||
func (p RRSet) Swap(i, j int) { p[i], p[j] = p[j], p[i] }
|
||||
func (p RRSet) Less(i, j int) bool { return p[i].String() < p[j].String() }
|
||||
|
||||
// If the TTL of a record is 303 we don't care what the TTL is.
|
||||
type Case struct {
|
||||
Qname string
|
||||
Qtype uint16
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue