Re: Determining case of REFUSED queries

2024-10-04 Thread tale via bind-users
On Thu, Oct 3, 2024 at 6:23 PM Lyle Giese via bind-users wrote: > I get this: > ; <<>> DiG 9.16.50-Debian <<>> ns socialinnovation.ca >... > socialinnovation.ca.3600IN NS dns.rebel.ca. > socialinnovation.ca.3600IN NS sean.ns.cloudflare.com. > socialinnovation.ca

Re: Determining case of REFUSED queries

2024-10-03 Thread Lyle Giese via bind-users
173.245.59.231 is a cloudflare name server. I get this: dig ns socialinnovation.ca ; <<>> DiG 9.16.50-Debian <<>> ns socialinnovation.ca ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29081 ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITI

Re: Determining case of REFUSED queries

2024-10-03 Thread J Doe
On 2024-09-19 19:17, Mark Andrews wrote: I think the reason for the REFUSED is pretty obvious % dig +norec google._domainkey.socialinnovation.ca @173.245.59.231 txt ; <<>> DiG 9.21.0-dev <<>> +norec google._domainkey.socialinnovation.ca @173.245.59.231 txt ;; global options: +cmd ;; Got answer

Re: Determining case of REFUSED queries

2024-09-19 Thread Mark Andrews
I think the reason for the REFUSED is pretty obvious % dig +norec google._domainkey.socialinnovation.ca @173.245.59.231 txt ; <<>> DiG 9.21.0-dev <<>> +norec google._domainkey.socialinnovation.ca @173.245.59.231 txt ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: RE

Determining case of REFUSED queries

2024-09-19 Thread J Doe
Hi list, I have BIND 9.18.29 validating recursive resolver running on OpenBSD 7.5. This resolver performs resolution for a mail server. Sometimes in my logs I will see the following: 17-Sep-2024 16:21:41.562 lame-servers: info: REFUSED unexpected RCODE resolving 'google._domainkey.so