Re: insecurity proof failed for a domain

2021-12-14 Thread Matus UHLAR - fantomas
On 13.12.21 08:18, John Thurston wrote: If you update your resolver to 9.16, I think you can do exactly what you want with the "validate-execpt" option. {rolls eyes} been there. done that. for exactly the same reason :/ On 14.12.21 16:58, Matus UHLAR - fantomas wrote: thanks, this helped. I

Re: insecurity proof failed for a domain

2021-12-14 Thread Matus UHLAR - fantomas
On 13.12.21 08:18, John Thurston wrote: If you update your resolver to 9.16, I think you can do exactly what you want with the "validate-execpt" option. {rolls eyes} been there. done that. for exactly the same reason :/ thanks, this helped. I assume I need to put "local" into validate-except

re: insecurity proof failed for a domain

2021-12-13 Thread John Thurston
If you update your resolver to 9.16, I think you can do exactly what you want with the "validate-execpt" option. {rolls eyes} been there. done that. for exactly the same reason :/ -- -- Do things because you should, not just because you can. John Thurston907-465-8591 john.thurs...@alask

insecurity proof failed for a domain

2021-12-13 Thread Matus UHLAR - fantomas
Hello, I need to internaly forward domain to different nameserver: zone "x.local" { type forward; forward only; forwarders { 100.1.2.3; }; }; when I do this with bind 9.11 (debian 10), I get these messages: Dec 13 14:26:55 mail named[13112]: valid