Am 02.10.2016 um 22:04 schrieb Maile Halatuituia:
how about nslookup with set debug option i think would do

besides the fact that when you think "nslookup" is the solution for anything you don't know your problem you did not understand my simple question:

"dig" or "nslookup" or whatever is just a client talking to a dns server on port 53 - that's it - it won't debug your server and if it would be able to do so your server would leak informations classified as security hole which needs to be closed

From: bind-users <bind-users-boun...@lists.isc.org> on behalf of Reindl Harald 
<h.rei...@thelounge.net>
Sent: Monday, October 3, 2016 8:34 AM
To: bind-users@lists.isc.org
Subject: Re: debug SERVFAIL

Am 02.10.2016 um 21:25 schrieb Per olof Ljungmark:
Thank you for all good advices, but I cannot refrain from commenting on
the fact that nobody answered my real question, namely,

A tip on how to generate debug output from "dig", in particular when
investigating SERVFAIL. In my stupidity I though asking on this list
would generate better answers than Google but it did not.

dig can not tell you why the server responds with SERVFAIL
how would you imagine this to be possible?
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

Reply via email to