Re: Enforce EDNS

2017-02-06 Thread Mark Andrews
In message , Daniel Stirnimann writes: > Hello all, > > Our resolver failed to contact an upstream name server as a result of > network connectivity issues. named retries eventually worked but as it > reverted back to not using EDNS and the answer should have been signed, > the query response fa

RE: Bind Queries log file format

2017-02-06 Thread MURTARI, JOHN
> From: Warren Kumari [mailto:war...@kumari.net] > Customer: "My BIND went Boom! It's been running fine for many years, > and then for no reason at all it went Boom. Here are my log files..." > ISC: "Doh. Sorry. Unfortunately the log file doesn't have sufficient > debug info. Can you please turn o

Re: Bind Queries log file format

2017-02-06 Thread Reindl Harald
Am 06.02.2017 um 14:25 schrieb Warren Kumari: I suspect perhaps some of the thread got missed (or was unclear). The reason for adding it to the main log file *by default* is because of things like: Customer: "My BIND went Boom! It's been running fine for many years, and then for no reason at a

Re: Bind Queries log file format

2017-02-06 Thread Warren Kumari
On Mon, Feb 6, 2017 at 7:44 AM, MURTARI, JOHN wrote: >> We may move it to the end of the log message (bugs ticket #44606 has >> been created for looking at it). Maybe its location was poor.. please >> can everyone who participated in this thread say whether having it at >> the end will be ok? > >

Re: Bind Queries log file format

2017-02-06 Thread MURTARI, JOHN
> We may move it to the end of the log message (bugs ticket #44606 has > been created for looking at it). Maybe its location was poor.. please > can everyone who participated in this thread say whether having it at > the end will be ok? It's really only for code debug. I'd say give the admin a me