One of the most useful initial steps in troubleshooting is to establish
your ability to reproduce the error.
So, I'd look at getting to the command-line of the originating resolver, if
possible, and using a command-line tool like "dig" to generate queries
towards the intended target and see if
Hi,
Am 01.10.18 um 21:10 schrieb Karol Babioch:
> Do you have any suggestion / recommendation what I can do to narrow the
> problem down? I already tried to increase the tracing and enabled query
> logging, but I couldn't get to the bottom of things. What else can I do
> here?
as an additional
Hi Kevin,
thanks for your reply.
Am 01.10.18 um 20:46 schrieb Kevin Darcy:
> Removing "forward only" just masks the problem by telling the resolver
> algorithm to fail over to iterative resolution when it encounters the
> SERVFAIL.
You are probably right, but at least it chooses the correct
You need to get to the root cause of what's causing the SERVFAIL.
Removing "forward only" just masks the problem by telling the resolver
algorithm to fail over to iterative resolution when it encounters the
SERVFAIL. So, sure, the query resolves, but probably not from the correct
server, and
Hi,
after upgrading my bind installation from 9.10.0 to 9.13.3 I'm
encoutering issues with zones that are forwarded. My setup is somewhat
complicated, but I was able to simplify it, so hopefully explanations.
Basically I have a split horizon DNS, so on my local resolver I'm
forwarding specific
5 matches
Mail list logo
