On Dec 12 12:07, Mathieu Arnold wrote:
+--On 12 décembre 2014 05:00:00 -0600 Scot Hetzel
wrote:
| On Fri, Dec 12, 2014 at 4:15 AM, Darren Pilgrim
| wrote
|> On 12/11/2014 11:53 PM, Matt Smith wrote:
|>>
|>> Somebody has let me know that I made an obvious mistake in the above. I
|>> meant that t
+--On 12 décembre 2014 05:00:00 -0600 Scot Hetzel
wrote:
| On Fri, Dec 12, 2014 at 4:15 AM, Darren Pilgrim
| wrote
|> On 12/11/2014 11:53 PM, Matt Smith wrote:
|>>
|>> Somebody has let me know that I made an obvious mistake in the above. I
|>> meant that the default rcorder is to run Unbound fir
On Fri, Dec 12, 2014 at 4:15 AM, Darren Pilgrim
wrote
> On 12/11/2014 11:53 PM, Matt Smith wrote:
>>
>> Somebody has let me know that I made an obvious mistake in the above. I
>> meant that the default rcorder is to run Unbound first followed by NSD.
>> So to clarify I think in the default situati
On 12/11/2014 11:53 PM, Matt Smith wrote:
Somebody has let me know that I made an obvious mistake in the above. I
meant that the default rcorder is to run Unbound first followed by NSD.
So to clarify I think in the default situation Unbound starts first,
contacts NSD and gets no answer because it
On Dec 11 10:51, Matt Smith wrote:
Hi,
I have run Unbound and NSD for a long time and everything was working
fine until the recent 1.5.x update for Unbound. Now if I reboot my
server I get DNSSEC validation errors for my own local domain until I
restart Unbound once again. I believe this is p
Hi,
I have run Unbound and NSD for a long time and everything was working
fine until the recent 1.5.x update for Unbound. Now if I reboot my
server I get DNSSEC validation errors for my own local domain until I
restart Unbound once again. I believe this is possibly related to the rc
startup o
