[Dnssec-trigger] Bug reports ?

[W.C.A. Wijngaards]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Phil,

On 10/21/2011 07:00 PM, Phil Regnauld wrote:
> W.C.A. Wijngaards (wouter) writes:
>>
>> Alright, thanks for that, remove the tcp-upstreamyes from the conf when
>> you try again (and add the trustanchoragain), otherwise dnssec-trigger
>> fails.
> 
> 	Why wouldn't tcp-upstream: yes and dnssec-trigger not work
> 	together ?  Or is it because dnssec-trigger only probes with UDP ?

dnssec-trigger wants tcp-upstream to be the default (no) in
unbound.conf.  It enables it dynamically when necessary.

>> You can always try 'Hotspot signon' which puts you in insecure mode: the
>> servers from DHCP are used, and unbound is bypassed.  Maybe that is
>> useful during debugging to get DHCP-connectivity again.
> 
> 	Right, will test that as well.

Have fun probing proxies :-)

Best regards,
   Wouter
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJOoo+IAAoJEJ9vHC1+BF+NTTEP/j60X5IPuCsbRCYHiMSkxmWI
MTkM1XoGjguOhUgBg9qmQ0uXIAxklgx27GMxAhcO2KeremOBHx8XKy6CEmFVWi+g
GBLpRuimvMYPx3w1c7EOvm2j5s88AcjOQmVt+AEM9Qwm/WNrFa6bho3zZgVIWJun
DxdWRfRGg2dTT0J7HaNsAdTfhGjY2tM5GjmvSAmNeC+kshQqPoMpvkDJB50HP1/S
xGKS6H5dezwurIdf1yY8dI5L+UN+2AIdOSnI/S00Cz96OmYK+4AFz6Ah1wHj8RIy
NDdUlZ5wdZrIsBwzL+DHJYmJq3hIq6dq+0E/XfgBU2yc8gTaqB9WXRAhGmR1DqQ6
SArM8fPhbQ2mRb4xBMKOYkDRYyT1oiwoOsJ1SsP3rdhWORjl2jYzCF6iBPnMSDlC
j+/xP2a7f0RQCv/NnXDB+/IDeOQVf7ScDCgKdzF28bOGZXGvKj4L/tIPsKInYpIz
/AQV4fYw+FJOu7gYSRm1OmQzh+gx12rGboWkxqNTy+x5ruycsTIGGt1DRgqHDL5H
pl6WUp4B1aXcX+wVjzRtymwRg1EzQY8ZX64bcUYR8SK4/Sv6tt4s6cLnHlEgfQg2
stb6e+i8sEbGCQbG/7DqOrswVcPDZXob9MnpZw4gWmOl+jZoXHfft8WRrjwzF4Ns
VVDplg2/cewSho+yTzfL
=19+N
-----END PGP SIGNATURE-----