Re: Wrong NSEC3 for wildcard cname

2014-11-21 Thread Casey Deccio
On Wed, Nov 19, 2014 at 7:03 PM, Graham Clinch wrote: > Thanks - that's certainly looking less red. DNSViz is an exceptionally > useful tool! > > Thanks! > ... > > delv +vtrace continues to report "NSEC3 at super-domain" only for > foo.cnametest2.palatine.ac.uk records, and not for > foo.cname

Re: Re: Wrong NSEC3 for wildcard cname

2014-11-20 Thread Timothe Litt
On 19-Nov-14 19:03, Graham Clinch wrote: > Hi Casey & List folks, >> My apologies - this was actually a bug in DNSViz. The NSEC3 computation >> was being performed on the wrong name (the wrong origin was being >> applied). It should be fixed now, as shown in: >> >> http://dnsviz.net/d/foo.cnamete

Re: Wrong NSEC3 for wildcard cname

2014-11-19 Thread Graham Clinch
Hi Casey & List folks, > My apologies - this was actually a bug in DNSViz. The NSEC3 computation > was being performed on the wrong name (the wrong origin was being > applied). It should be fixed now, as shown in: > > http://dnsviz.net/d/foo.cnametest.lancs.ac.uk/VGzlkA/dnssec/ > http://dnsviz.n

Re: Wrong NSEC3 for wildcard cname

2014-11-19 Thread Casey Deccio
Hi Graham, On Wed, Nov 19, 2014 at 11:59 AM, Graham Clinch wrote: > Using bind 9.9.5 with inline-signing, I have a test wildcard cname > record in two zones: > > *.cnametest.lancs.ac.uk CNAME www.lancs.ac.uk > *.cnametest.palatine.ac.uk CNAME www.palatine.ac.uk > > dnsviz is showing the error >