search for: rndckey

Displaying 13 results from an estimated 13 matches for "rndckey".

2005 Nov 26
2
rdnc error
...rror with my rndc key. I could 'play' around with it and may fix it but most likey just hose things up. I think I see the problem but not 100% sure. I think the key file has 3 different names. Here's the error: **Unmatched Entries** /etc/named.conf:23: couldn't find key 'rndckey' for use with command channel 127.0.0.1#953: 1 Time(s) Here's parts of the relevant files: named.conf: controls { inet 127.0.0.1 allow { localhost; } keys { rndckey; }; include "/etc/rndc.key"; <-- does not match above -----------------------------------------------------...
2008 Jun 20
1
rndc: connect failed: 127.0.0.1#953: connection refused
hi wile i am running the command rndc reload i am getting the error rndc: connect failed: 127.0.0.1#953: connection refuse any one can suggest where i am doing wrong this is my rndc.conf key "rndckey" { algorithm hmac-md5; secret "fKZfrqGy9VOPOLA3pgDACA=="; }; options { default-key "rndckey"; default-server 127.0.0.1; default-port 953; }; this my named.conf key "rndckey" { algorithm hmac-md5; secret &q...
2008 Jun 20
2
rndc: connect failed: 127.0.0.1#953: connection refuse
hi wile i am running the command rndc reload i am getting the error rndc: connect failed: 127.0.0.1#953: connection refuse any one can suggest where i am doing wrong this is my rndc.conf key "rndckey" { algorithm hmac-md5; secret "fKZfrqGy9VOPOLA3pgDACA=="; }; options { default-key "rndckey"; default-server 127.0.0.1; default-port 953; }; this my named.conf key "rndckey" { algorithm hmac-md5; secret &q...
2009 Nov 25
7
rndc start fails with "rndc: connect failed: connection refused"
CentOS 4.8, BIND 9.2.4 Hi All: I have a rather annoying problem with rndc which I have not been able to resolve despite much searching and many attempts to correct. When making changes to our DNS entries I have tried to use the following procedures: 1. Flush the cache buffers: rndc flush 2. Stop named: rndc stop 3. Delete the journal files: rm *.jnl 4. Edit the forward and/or
2017 Jun 23
3
Samba AD - Issue with winbindd: Could not write result
...; // allow-update { none; }; // }; //zone "0.in-addr.arpa" IN { // type master; // file "named.zero"; // allow-update { none; }; //}; #zone "niccolai" IN { # type master; # file "niccolai"; # allow-update { key "rndckey" ; }; ## allow-transfer { 10.0.0.19; }; ## notify yes; #}; #zone "10.in-addr.arpa" IN { # type master; # file "10.in-addr.arpa"; # allow-update { key "rndckey" ; }; ## allow-transfer { 10.0.0.19; }; ## notify yes; #...
2017 Jun 23
0
Samba AD - Issue with winbindd: Could not write result
...ne "0.in-addr.arpa" IN { > // type master; > // file "named.zero"; > // allow-update { none; }; > //}; > > #zone "niccolai" IN { > # type master; > # file "niccolai"; > # allow-update { key "rndckey" ; }; > ## allow-transfer { 10.0.0.19; }; > ## notify yes; > #}; > #zone "10.in-addr.arpa" IN { > # type master; > # file "10.in-addr.arpa"; > # allow-update { key "rndckey" ; }; > ## allow-transfer...
2017 Jun 22
2
Samba AD - Issue with winbindd: Could not write result
Hello, I have the same problems outlined in this old thread... Only difference the original poster was on RHEL6.X, I am on RHEL7, he compiled samba on its own, I used Sernet Samba (latest)... Unfortunately there is no solution on this thread. Suggestions? Thank you
2006 Dec 12
1
BIND with ACLs
...ile "/var/named/data/query-log" versions 5 size 50m; }; category queries { query-log; }; }; acl internals { 192.168.1/24; 127/8; }; // // a caching only nameserver config // controls { inet 127.0.0.1 port 953 allow { localhost; } keys { rndckey; }; }; view "external" { match-clients { any; }; recursion no; zone "conntrust.com" IN { type master; file "conntrust.com.hosts"; allow-update {none;}; allow-query {any;}; allow-transfer {any;}; }; zone "w...
2005 Apr 09
1
Samba Dynamic DNS DHCP , client won't register
...ed * port by default. */ // query-source address * port 53; listen-on-v6 { any; }; notify no; forward only; forwarders { 62.108.117.6; }; auth-nxdomain yes; listen-on { capriolo; univerzal; alstar; }; }; // // a caching only nameserver config // controls { inet 127.0.0.1 allow { localhost; } keys { rndckey; }; }; zone "." IN { type hint; file "named.ca"; }; zone "localhost" IN { type master; file "localhost.zone"; allow-update { none; }; }; zone "0.0.127.in-addr.arpa" IN { type master; file "named.local"; allow-update { none; }; }; #--------...
2007 Feb 08
0
Client browsing problem
...revious versions of BIND always asked * questions using port 53, but BIND 8.1 uses an unprivileged * port by default. */ // query-source address * port 53; }; // // a caching only nameserver config // controls { inet 127.0.0.1 allow { localhost; } keys { rndckey; }; }; acl msdpl { 192.168.129.0/24; 192.168.128.0/24; 192.168.130.0/24; }; zone "msdpl.com" IN { type master; file "msdpl.com.zone"; notify yes; allow-query { msdpl; }; allow-transfe...
2006 Dec 25
0
Machines getting disjoint from Domain
...revious versions of BIND always asked * questions using port 53, but BIND 8.1 uses an unprivileged * port by default. */ // query-source address * port 53; }; // // a caching only nameserver config // controls { inet 127.0.0.1 allow { localhost; } keys { rndckey; }; }; acl msdpl { 192.168.129.0/24; 192.168.128.0/24; 192.168.130.0/24; }; zone "msdpl.com" IN { type master; file "msdpl.com.zone"; notify yes; allow-query { msdpl; }; allow-transfe...
2002 Dec 31
1
Trouble pinging servers DNS name.
...BIND always asked * questions using port 53, but BIND 8.1 uses an unprivileged * port by default. */ query-source address * port 53; }; // // an authoritative-only nameserver config // usr share doc bind-9.1.3 arm Bv9ARM.ch03.html // controls { inet 127.0.0.1 allow { localhost; } keys { rndckey; }; }; zone "." IN { type hint; file "named.ca"; }; zone "cofrny.gov" IN { type master; forwarders { }; file "cofrny.gov.db"; }; zone "0.0.127.in-addr.arpa" IN { type master; file "named.local"; }; include "/etc/rndc....
2005 Jun 22
2
Problem Connecting from Windows to Samba-OpenLDAP PDC
...w. Previous versions of BIND always asked * questions using port 53, but BIND 8.1 uses an unprivileged * port by default. */ // query-source address * port 53; }; // // a caching only nameserver config // controls { inet 127.0.0.1 allow { localhost; } keys { rndckey; }; }; zone "0.0.127.in-addr.arpa" { type master; file "pz/127.0.0"; }; zone "mtgmilw.biz" { type master; notify no; file "pz/mtgmilw.biz"; allow-query { any; }; }; zone "0.0.10.in-addr.arpa" { ty...