Bind (dns server): What is the cause of the "connect failed: 127.0.0.1#953: connection refused" error?

Question

Domain Name System

From scratch: downloaded BIND v9.11.2 using the installer, successfully installed, ... installed for evaluation purposes on Windows 10 Pro. According to the instructions for use, I generated the key with the command rndc -confgen -a, then created a file named.confand entered lines into it that speak for themselves:

options {
  directory "c:\windows\system32\etc";
  listen-on { 192.168.0.2; 127.0.0.1; };
  allow-transfer { 192.168.0.1; };

  forwarders {
  192.168.0.1;
  8.8.8.8;
  };

};
logging {
  channel default-log {
    file "c:\windows\system32\etc\named.log";
    severity debug;
    print-severity yes;
    };
  category default {
    default-log;
    };
};

after, I executed the command rndc reloadand, hoping for the best, the console answered me:

rndc: connect failed: 127.0.0.1#953: connection refused

the first suspicion is that the port is "clogged" 953, but it turned out that it is free and no one is listening to it ... in which direction to dig?

Answer 1

I really "stepped" ... the answer turned out to be eerily simple - it was necessary to manually start the ISC BIND service.
Initially, there was a checkmark in the installer (like: run after installation), I relied on it, but in vain, because the installation went through, but here the start of the attached service did not happen. Corrected. Thanks everyone for the replies.