similar to: Centos 5 where is rndc.conf and named.conf?

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

I've done something a while back that has messed with my named.conf and prevents me from restarting named service normally... My problem... # service named restart Stopping named: [FAILED] Starting named: named: already running [FAILED] nothing gets logged in /var/log/messages obviously, I can do this to restart it... [root at

I thought I've installed the clustering tools, but when I attempt to run clustat, it says it doesn't exist. When I installed the suite, I ran: yum install -y GFS GFS-kernel-smp magma-plugins fence dlm dlm-kernel-smp gulm cman cman-kernel-smp CCSD is running and when I "cat /proc/cluster/nodes", I see my three nodes. Does anyone see the package that I missed for

I recently upgraded my name server to CentOs 4.4 from CentOs 4.3 and bind was one of the many packages upgraded. I get the following message when performing an rndc reload " rndc reload rndc: connection to remote host closed This may indicate that the remote server is using an older version of the command protocol, this host is not authorized to connect, or the key is invalid." which

Hi list Does anyone know if there is a simple way to import standard linux users into the directory server? I have found some but they don't seem to be so flexible since I have to import from several servers into different ou's Regards Per Qvindesland

What happened????? Where is slocate? what package did I not install? Or is there something newer and better?

hello folks! i've got four HP NetServers, two LC2000r and two LH6000r. the CentOS 4.2 ServerCD can't see hard drives on any of them. each machine has a HP NetRAID controller; the LC2000rs have a NetRAID-1Si and the LH6000rs have an Integrated NetRAID. each controller has three 9GB drives, two mirrored and one hotspare. each machine boots ok (the LC2000rs need "linux

Installed using pkd_add or ports BIND-9.6.0-P1 working fine. 1.But seems can't run under chroot well: ---------------------------------------------------------- Jan 27 13:54:08 ns named[36447]: starting BIND 9.6.0-P1 -c named.conf -t /var/named -u bind Jan 27 13:54:08 ns named[36447]: built with '--localstatedir=/var' '--disable-linux-caps'

I started the named server on CentOS and it seems to resolve DNS request OK, but it does not seem to retain the info for very long. From what I can tell using "dig", a domain's ip address is retained for less than 12 hours. So in the morning, it takes 4+ seconds to resolve again the first time. Is there an adjustment somewhere for this or is the caching named support not enabled by

I don't know why I haven't signed up for this list before since we use CentOS all over the place. The list is very useful and it is good for me to participate and "give back" to the community. Anywho, I wanted to post this response to a thread that was created back in November 2008 about the ntop daemon failing to start. I'm currently setting up ntop as a NetFlow &

I have the following kernels on my /boot: 2.6.18-128.1.6 2.6.18-92.1.18 2.6.18-92.1.22 I'm low on /boot space and need to remove the oldest version. It appears that I cannot use yum to remove since all of the versions are the same (only the release is different). I believe that I can use rpm to remove the old version, but I also need to remove them from the grub.conf. Any other

hello folks! on this page (http://xapian.org/download) you have links to the Fink packages for xapian-core and omega; you may be interested to know that i've packaged the Xapian Python bindings. i'm working on similar packages for the Ruby and PHP bindings, and i'd be happy to inform you once they've been pushed out to the mirrors. -steve -- If this were played upon a

Hello, I have been asked to come up with a strategy for centralized patch management of our linux servers. Today, this is only centos and rhel. What is everyone else doing in this arena? Thanks!

Hi all, I've set up a simple domain using Samba 4.4.2 from source under Ubuntu 16.04. I accepted the usual defaults and basically followed wiki.samba.org to the letter. The main thing is I'm using Samba's internal DNS and not Bind (Bind is not even installed on the system). In the log.samba file on the first DC I kept getting this: [2016/04/28 17:01:02.716292, 0]

Hi list, here is what happened: today I noticed some resolution's problems on my network. I did a "service named status" and here was the output: # /etc/init.d/named status rndc: connection to remote host closed This may indicate that the remote server is using an older version of the command protocol, this host is not authorized to connect, or the key is invalid. In the

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;

On 4/28/2016 1:05 PM, Rowland penny wrote: > On 28/04/16 17:21, Wayne Merricks wrote: >> Hi all, >> >> I've set up a simple domain using Samba 4.4.2 from source under >> Ubuntu 16.04. >> >> I accepted the usual defaults and basically followed wiki.samba.org >> to the letter. The main thing is I'm using Samba's internal DNS and >>

I just downloaded the bind-chroot rpm and looked into it with Archive manager (so I am lazy), and no files, just the chroot tree. I am assuming there is some script that Archive manager does not show, or I am just missing it, because the ROOTDIR= did get added to /etc/sysconfig/named (and the one in the bind rpm is without this line). Just interesting that if you chroot, you are expected to

My BIND9.6.0 on FreeBSD 6.2 works fine when I manually start with: root@ns2# named -4 -S 1024 -c /etc/namedb/named.conf But it won't start on boot and no error messages or log. And it won't start using rndc, it cause error message. Why does the error shows port 953 when I specified for port 53 in the config? rndc: connect failed: 127.0.0.1#953: connection refused Below are

My AD domain (SerNET S4 4.5.3) using S4's internal DNS, and always has. So why is it now constantly logging an error of - [2017/01/13 12:53:00.152754, 0] ../lib/util/util_runcmd.c:316(samba_runcmd_io_handler) /usr/sbin/rndc: Failed to exec child - No such file or directory - after attempting to add a 2008R2 DC. I do not recall seeing this error previously [not prior to