On 8/9/22 16:02, Dino Edwards wrote:
>
>> It's absolutely not forwarding. It's resolving recursively. I'm using
> unbound with pfsense and I'm suspecting there is something wrong with it.
>> When I point to MS DNS server or 9.9.9.9, it's resolving correctly.
>
> The issue has been resolved. Just
>It's absolutely not forwarding. It's resolving recursively. I'm using
unbound with pfsense and I'm suspecting there is something wrong with it.
>When I point to MS DNS server or 9.9.9.9, it's resolving correctly.
The issue has been resolved. Just in case someone finds the solution useful,
pfse
>In any case, the OP may well be using a local resolver, but they didn't say
whether it's resolving recursively or forwarding (e.g. to 8.8.8.8), and I'd
bet it's the latter.
It's absolutely not forwarding. It's resolving recursively. I'm using
unbound with pfsense and I'm suspecting there is som
On Tue, 9 Aug 2022, Bill Cole wrote:
On 2022-08-09 at 12:50:22 UTC-0400 (Tue, 9 Aug 2022 12:50:22 -0400)
Dino Edwards
is rumored to have said:
Let's do some concreate tests.
1) What is the output from:
dig +short 2.0.0.127.zen.spamhaus.org
Output is nothing
Your DNS resolver is brok
Dino Edwards:
>
>
> >Let's do some concreate tests.
>
> >1) What is the output from:
>
> > dig +short 2.0.0.127.zen.spamhaus.org
>
> Output is nothing
There should be a list of responses, as pointed out by Bill Cole
(or an error response if you are using a provider's resolver).
Wiet
On 2022-08-09 at 12:50:22 UTC-0400 (Tue, 9 Aug 2022 12:50:22 -0400)
Dino Edwards
is rumored to have said:
>> Let's do some concreate tests.
>
>> 1) What is the output from:
>
>> dig +short 2.0.0.127.zen.spamhaus.org
>
> Output is nothing
Your DNS resolver is broken. That's a test name which shou
Dino Edwards:
>
> << I suggest that you start with dig/nslookup and establish that you have
> properly working DNS, and that your ISP is not replacing all "not found"
> responses with the IP address of some "helpful" website.
>
> Using local DNS servers and not ISP servers. DNS is working as it s
I suggest that you start with dig/nslookup and establish that you
have properly working DNS, and that your ISP is not replacing all
"not found" responses with the IP address of some "helpful" website.
Wietse
