Am 02.10.2016 um 23:24 schrieb Per olof Ljungmark:
On 2016-10-02 22:09, Reindl Harald wrote:
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 kno
On 2016-10-02 22:09, Reindl Harald wrote:
>
>
> 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 m
indl Harald
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 o
how about nslookup with set debug option i think would do
From: bind-users on behalf of Reindl Harald
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
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 thou
Hi,
On 2016-10-02 20:41, Reindl Harald wrote:
>
>
> Am 02.10.2016 um 20:32 schrieb Per olof Ljungmark:
>> On 2016-10-02 19:22, Nico CARTRON wrote:
>>> Hi Per,
>>>
On 2 Oct 2016, at 19:07, Per olof Ljungmark wrote:
[...]
> Just use the "hint" type configuration. This is j
Am 02.10.2016 um 20:32 schrieb Per olof Ljungmark:
On 2016-10-02 19:22, Nico CARTRON wrote:
Hi Per,
On 2 Oct 2016, at 19:07, Per olof Ljungmark wrote:
[...]
Just use the "hint" type configuration. This is just fine for most users.
The interesting thing is why FreeBSD includes the recom
Hi,
On 2016-10-02 19:22, Nico CARTRON wrote:
> Hi Per,
>
>> On 2 Oct 2016, at 19:07, Per olof Ljungmark wrote:
>>
>> [...]
>>
>>> Just use the "hint" type configuration. This is just fine for most users.
>>
>> The interesting thing is why FreeBSD includes the recommendation in the
>> default nam
Hi Per,
> On 2 Oct 2016, at 19:07, Per olof Ljungmark wrote:
>
> [...]
>
>> Just use the "hint" type configuration. This is just fine for most users.
>
> The interesting thing is why FreeBSD includes the recommendation in the
> default named.conf if that is not good, and I thought it would be
Hi,
On 2016-10-02 17:51, Anand Buddhdev wrote:
> On 02/10/16 17:22, Per olof Ljungmark wrote:
>
> Hello Per,
>
> Please see my answers below. You appear to have a bad configuration.
Well, HAD a bad configuration as I just posted.
>> Hmmm, looks like I've found something here. The default named
On 02/10/16 17:22, Per olof Ljungmark wrote:
Hello Per,
Please see my answers below. You appear to have a bad configuration.
> Hmmm, looks like I've found something here. The default named.conf on
> FreeBSD has the following section on the root servers. If I comment out
> the "traditional" root
On 2016-10-02 17:02, Reindl Harald wrote:
>
>
> Am 02.10.2016 um 17:00 schrieb Per olof Ljungmark:
>> On 2016-10-02 16:50, Reindl Harald wrote:
>>>
>>>
>>> Am 02.10.2016 um 16:46 schrieb Per olof Ljungmark:
What is the best way to debug a SERVFAIL problem? I have tried to ramp
up the tr
Am 02.10.2016 um 17:00 schrieb Per olof Ljungmark:
On 2016-10-02 16:50, Reindl Harald wrote:
Am 02.10.2016 um 16:46 schrieb Per olof Ljungmark:
What is the best way to debug a SERVFAIL problem? I have tried to ramp
up the trace level a lot but that did not return anything useful.
It is onl
On 2016-10-02 16:50, Reindl Harald wrote:
>
>
> Am 02.10.2016 um 16:46 schrieb Per olof Ljungmark:
>> What is the best way to debug a SERVFAIL problem? I have tried to ramp
>> up the trace level a lot but that did not return anything useful.
>>
>> It is only one zone in question, namely the PTR f
Am 02.10.2016 um 16:46 schrieb Per olof Ljungmark:
What is the best way to debug a SERVFAIL problem? I have tried to ramp
up the trace level a lot but that did not return anything useful.
It is only one zone in question, namely the PTR for our external subnet.
What puzzles me the most is that
Hi,
What is the best way to debug a SERVFAIL problem? I have tried to ramp
up the trace level a lot but that did not return anything useful.
It is only one zone in question, namely the PTR for our external subnet.
What puzzles me the most is that a secondary on the same subnet answers
just fine f
16 matches
Mail list logo
