How come I can't stop named?

imsam · 10-26-2004, 09:49 AM

Hi,

When I type "service named stop" nothing happens.

I type "service named status" it tells me that the server is up and running.

Then I type "service named start" it tells me that it's already running.

I'm a newbie and just installed RH9 and using the GUI setup, I selected DNS server setup. However, when I was done w/ setup "named" was not started.

I manually started named and put it under RunLevel 3. Am I making a mistake somewhere?

scowles · 10-26-2004, 11:38 AM

Just so we are on the same page, can you post the following command outputs?

Code:

[root@voyager etc]# service named start
Starting named:                                            [  OK  ]
[root@voyager etc]# service named status                                 
number of zones: 4
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is OFF
server is up and running
[root@voyager etc]# service named stop  
Stopping named:                                            [  OK  ]
[root@voyager etc]# service named status
rndc: connect failed: connection refused

FYI:
service named stop = rndc stop
service named status = rndc status

In short, check /etc/rndc.key, /etc/rndc.conf and /etc/named.conf to make sure your key definitions are correct.

imsam · 10-26-2004, 12:28 PM

Hi,

What I see on the screen is identical to what you put in your post except for the fact that I don't get [OK] after I enter service named stop. It does say Stopping named: but I never get the OK.

Here's what I'm seeing:

Code:

[root@MyTestDNS etc]# service named start
Starting named:                                            [  OK  ]
[root@MyTestDNS etc]# service named status                                 
number of zones: 4
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is OFF
server is up and running
[root@MyTestDNS etc]# service named stop  
Stopping named:
[root@MyTestDNS etc]# service named status                                 
number of zones: 4
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is OFF
server is up and running
[root@MyTestDNS etc]# service named start
named: Already running[root@MyTestDNS etc]#

I checked the rndc.key, rndc.conf and named.conf files. They're all there. I'm not sure what I'm looking for but they're there.

scowles · 10-26-2004, 01:08 PM

I'm at a loss as to why named is not stopping on your system. My goal in having you paste the output of those commands was to verify your rndc keys were properly configured; which they are. The " rndc status" output verified that.

At this point, I would look in /var/log/messages to see if there are any errors associated with stopping named. Maybe checking if there is a newer version of bind available. Check the redhat site to see if there have been any problems logged against bind running on RH9, Something along those lines.

imsam · 10-26-2004, 02:04 PM

Hi,

Scowles thanks for your help. A little research on Google indicates this is a RH related problem. Here's what someone who's having the same exact problem said

Quote:

Just did a redhat kernel upgrade, from 2.4.20-8 to 2.4.20-24.9, which fixed the problem. I can now stop named using rndc without any problems.[/

Now, this brings up another question. Because I'm a newbie, I don't know how to do kernel updates. Could anyone give me an idea about where to get them and how to install them using nothing but the command prompt.

The great thing about this experience is that I'm learning so much about Linux. My DNS setup was for testing and learning purposes so this is working out great.

Again, I'd appreciate some pointer on how to do a kernel update.

baz2 · 10-26-2004, 03:43 PM

Quote:

Originally posted by imsam
Again, I'd appreciate some pointer on how to do a kernel update.

The easiest thing to do is go here . Download the appropriate RPM file for your architecture (hardware). Then, like the instructions say, do a

rpm -Fvh [filenames]

where [filenames] is a list of the RPMs you wish to upgrade.

I better solution would be to upgrade to Fedora Core 2, which will get you into the 2.6x kernel. Then, go to www.fedorafaq.org, get the yum.conf file they have there, and do

yum update

to keep up to date.