> On 17 Dec 2020, at 06:44, Timothe Litt wrote:
>
>
> On 16-Dec-20 13:52, Tim Daneliuk wrote:
>> On 12/16/20 12:25 PM, Timothe Litt wrote:
>>
>>> On 16-Dec-20 11:37, Tim Daneliuk wrote:
>>>
I ran into a situation yesterday which got me pondering something about
bind.
In
Hi Tale,
Thanks for explaining
We can close this query now.
Thanks team for helping me understand the issue.
--
Thanks
Prasanna
On 17/12/20, 1:13 AM, "tale" wrote:
On Wed, Dec 16, 2020 at 3:48 AM Prasanna Mathivanan (pmathiva) via
bind-users wrote:
> Whenever we have broken de
Am 16.12.20 um 19:18 schrieb Tim Daneliuk:
On 12/16/20 11:36 AM, Reindl Harald wrote:
where did i give the advice "don't fail"?
please read my repsonse again!
* the zone fails on the master
* the zone is still available on the slaves
* so the error isn't fatal
* but you recognize your mistak
On 16-Dec-20 13:52, Tim Daneliuk wrote:
> On 12/16/20 12:25 PM, Timothe Litt wrote:
>> On 16-Dec-20 11:37, Tim Daneliuk wrote:
>>> I ran into a situation yesterday which got me pondering something about
>>> bind.
>>>
>>> In this case, a single line in a zone file was bad. The devops automation
>
On Wed, Dec 16, 2020 at 3:48 AM Prasanna Mathivanan (pmathiva) via
bind-users wrote:
> Whenever we have broken delegation as domain owners didn't follow proper RFC,
> the default behaviour of the query hits " _." which
> doesn’t exist.? And we get NXDOMAIN or SERVFAIL response.
Going back to
On 12/16/20 12:25 PM, Timothe Litt wrote:
> On 16-Dec-20 11:37, Tim Daneliuk wrote:
>> I ran into a situation yesterday which got me pondering something about bind.
>>
>> In this case, a single line in a zone file was bad. The devops automation
>> had inserted a space in the hostname field of a PT
On 16-Dec-20 11:37, Tim Daneliuk wrote:
> I ran into a situation yesterday which got me pondering something about bind.
>
> In this case, a single line in a zone file was bad. The devops automation
> had inserted a space in the hostname field of a PTR record.
>
> What was interesting was that - at
On 12/16/20 11:36 AM, Reindl Harald wrote:
>
>
> Am 16.12.20 um 18:26 schrieb Gregory Sloop:
>> This isn't, IMO, very useful as a response to the OP.
>
> let that decide the OP
>
>> To sum up the response; "It's better to never fail!"
>>
>> Yes, that seems pretty obvious. It *would* be better t
Am 16.12.20 um 18:26 schrieb Gregory Sloop:
This isn't, IMO, very useful as a response to the OP.
let that decide the OP
To sum up the response; "It's better to never fail!"
Yes, that seems pretty obvious. It *would* be better to never fail. Way,
way better.
But the big problem in life
This isn't, IMO, very useful as a response to the OP.
To sum up the response; "It's better to never fail!"
Yes, that seems pretty obvious. It *would* be better to never fail. Way, way
better.
But the big problem in life is; We're always failing! Dammit!
So, learning how to gracefully fail, and
Am 16.12.20 um 17:37 schrieb Tim Daneliuk:
I ran into a situation yesterday which got me pondering something about bind.
In this case, a single line in a zone file was bad. The devops automation
had inserted a space in the hostname field of a PTR record.
What was interesting was that - at s
I ran into a situation yesterday which got me pondering something about bind.
In this case, a single line in a zone file was bad. The devops automation
had inserted a space in the hostname field of a PTR record.
What was interesting was that - at startup - bind absolutely refused
to load the zon
Nameservers generate their own requests. Nameservers have to translate names
to addresses as part of the notify process.
--
Mark Andrews
> On 16 Dec 2020, at 19:18, Xinyu Wang wrote:
>
>
>
>
> Hi guys, I noticed query-source takes effect even recursive is set false.
> My question is, i
Thanks Mark for responding.
Whenever we have broken delegation as domain owners didn't follow proper RFC,
the default behaviour of the query hits " _." which doesn’t
exist.? And we get NXDOMAIN or SERVFAIL response.
Is my understanding correct ?
--
Thanks
Prasanna
On 14/12/20, 6:51 AM,
Hi guys, I noticed query-source takes effect even recursive is set false.
My question is, if recursion is disabled, no outgoing queries should be
generated. So why query-source still takes effect?
Also, resovler is created per view when starting up named even
recursive==false. Why? Do resolvers ne
15 matches
Mail list logo