search for: bind9rndc

...y: > > > I had to go do something else and have returned. I discovered that I > hadn't gone back far enough. This complaint first appears here: > > ==========Enable bind gssapi and bind9_DLZ > =============================== > [....] Stopping domain name service...: bind9rndc: connect failed: > 127.0.0.1#953: connection refused > . ok > [ ok ] Starting domain name service...: bind9. > > Notice the "refused" appearance. As there is no firewall on this > machine, yet, port 953 is not blocked. > > This DC appears to operating correctl...

You can try to bind the interfaces including localhost. That worked for me. Am 25. Februar 2015 21:20:05 MEZ, schrieb Marc Muehlfeld <mmuehlfeld at samba.org>: >Hello Bob, > >Am 25.02.2015 um 19:09 schrieb Bob of Donelson Trophy: >> I ran your "1-setup-sernet-samba4-ADDC-wheezy.sh" script and noticed >> this (during install:) >> >> ==========SE

...ote: > > > I had to go do something else and have returned. I discovered that I > hadn't gone back far enough. This complaint first appears here: > > ==========Enable bind gssapi and bind9_DLZ > =============================== > [....] Stopping domain name service...: bind9rndc: connect failed: > 127.0.0.1#953: connection refused > . ok > [ ok ] Starting domain name service...: bind9. > > Notice the "refused" appearance. As there is no firewall on this > machine, yet, port 953 is not blocked. > > This DC appears to operating correctly des...

...b Bob of Donelson Trophy: >> >>> I had to go do something else and have returned. I discovered that I hadn't gone back far enough. This complaint first appears here: ==========Enable bind gssapi and bind9_DLZ =============================== [....] Stopping domain name service...: bind9rndc: connect failed: 127.0.0.1#953: connection refused . ok [ ok ] Starting domain name service...: bind9. Notice the "refused" appearance. As there is no firewall on this machine, yet, port 953 is not blocked. This DC appears to operating correctly despite this. This may be a 'bind9'...

I had to go do something else and have returned. I discovered that I hadn't gone back far enough. This complaint first appears here: ==========Enable bind gssapi and bind9_DLZ =============================== [....] Stopping domain name service...: bind9rndc: connect failed: 127.0.0.1#953: connection refused . ok [ ok ] Starting domain name service...: bind9. Notice the "refused" appearance. As there is no firewall on this machine, yet, port 953 is not blocked. This DC appears to operating correctly despite this. This may be a 'bind9...

Hai Bob. SETDNSDOMAIN='hostname -d' needs to be: SETDNSDOMAIN=`hostname -d` .. so change them all . SETDNSDOMAIN=`hostname -d` SETHOSTNAME=`hostname -s` SERVER_IP_ADDRESS=`hostname -i` and you can ignore : >[....] Stopping domain name service...: bind9rndc: connect failed: >127.0.0.1#953: connection refused > >. ok > >[ ok ] Starting domain name service...: bind9. in the next script version you wont see these messages. as long as you see.. >[ ok ] Starting domain name service...: bind9. its ok. Greetz, Louis >-----...

...ote: >> >>> I had to go do something else and have returned. I >discovered that I hadn't gone back far enough. This complaint >first appears here: ==========Enable bind gssapi and bind9_DLZ >=============================== [....] Stopping domain name >service...: bind9rndc: connect failed: 127.0.0.1#953: >connection refused . ok [ ok ] Starting domain name >service...: bind9. Notice the "refused" appearance. As there >is no firewall on this machine, yet, port 953 is not blocked. >This DC appears to operating correctly despite this. This may...

I upped 1.0.4 of the script.. I added checks if no DC's are found, error message and exits script, so no python errors anymore, if i did it right. ;-) on both DC's do the following. and whats the output of : cat /etc/hosts cat /etc/resolv.conf and kinit Administrator SETDNSDOMAIN=`hostname -d` SETHOSTNAME=`hostname -s` SERVER_IP_ADRESS=`hostname -i` echo "Test domainname: