Florin Asăvoaie's questions

I have ISC Bind 9.10.4-P1 (named) running on Windows 10, with the following configuration file:

key "rndc-key" {
    algorithm hmac-md5;
    secret "jqTFmyJ3pGkoV4wC/yV9BQ==";
};

options {
    directory "C:\Program Files\ISC BIND 9\etc";
    listen-on {
        127.0.0.1;
    };
    listen-on-v6 {
        ::1;
    };
    allow-query {
        localhost;
    };
    forwarders {
        2001:4860:4860::8888;
        2001:4860:4860::8844;
        8.8.8.8;
        8.8.4.4;
    };
    recursion yes;
    dnssec-validation no;
    auth-nxdomain no;
};

view local {
    match-clients {
        localhost;
    };

    zone "test.local" {
        type master;
        file "zones/test.local.zone";
    };
};

This is what it appears to be listening on (netstat /a /n /o | findstr $PID):

TCP    127.0.0.1:53           0.0.0.0:0              LISTENING       1440
TCP    127.0.0.1:953          0.0.0.0:0              LISTENING       1440
TCP    [::1]:953              [::]:0                 LISTENING       1440
UDP    127.0.0.1:53           *:*                                    1440

I checked the Event Viewer and there are no errors or warning at startup, only the normal messages.

Does anyone have any idea why it does not listen on ::1?

EDIT: If I put any at listen-on-v6, it kind of works. Listens on all IPv6 IPs bound to the machine, except ::1...

I am running Puppet 3.7 and I have the following issue:

Installed the nokogiri gem on the agents with pe_gem. Wrote a custom provider that does require 'nokogiri' at the top.

The Puppet run "sometimes" fails with "Unable to load 'nokogiri'" error from Ruby autoloader.

The thing is - it works the first time it gets the provider from the Puppet master. All subsequent runs fail.

My guess is that somehow there is something loaded before my provider that makes it work, when it does.

Did anyone else experience this or think about what can it be?