Jason Staudenmayer wrote:
Anything in the log files?
Jason
..·><((((º>
Yes as it turns out, thanks for asking.
Apr 7 15:22:39 box6 named[5097]: starting BIND 9.3.4 -u named -t
/var/named/chroot
Apr 7 15:22:39 box6 named[5097]: found 2 CPUs, using 2 worker threads
Apr 7 15:22:39 box6 named[5097]: loading configuration from
'/etc/named.conf'
Apr 7 15:22:39 box6 named[5097]: /etc/blocking.conf:29: zone
'ad.doubleclick.net': already exists previous definition:
/etc/blocking.conf:15
Apr 7 15:22:39 box6 named[5097]: listening on IPv6 interface lo, ::1#53
Apr 7 15:22:39 box6 named[5097]: listening on IPv4 interface lo,
127.0.0.1#53
Apr 7 15:22:39 box6 named[5097]: /etc/blocking.conf:29: zone
'ad.doubleclick.net' already exists
Apr 7 15:22:39 box6 named[5097]: loading configuration: already exists
Apr 7 15:22:39 box6 named[5097]: exiting (due to fatal error)
I removed the double entry from /var/named/chroot/etc/blocking.conf and
then I was able to start named!
I added some entries to the blocking file late yesterday and I obviously
screwed things up, I never would have guessed entering the same URL
twice would do that?
Thanks for the help.
Bob Goodwin
-----Original Message-----
From: fedora-list-bounces@xxxxxxxxxx
[mailto:fedora-list-bounces@xxxxxxxxxx] On Behalf Of Bob
Goodwin - W2BOD
Sent: Saturday, April 07, 2007 3:26 PM
To: For users of Fedora
Subject: Re: Nameserver Problem Revisited -
Bob Goodwin - W2BOD wrote:
Bob Goodwin - W2BOD wrote:
Tim wrote:
On Sat, 2007-04-07 at 10:42 -0400, Bob Goodwin - W2BOD wrote:
This scheme worked nicely until this morning!
service named status
rndc: connect failed: 127.0.0.1#953: connection refused
service named restart
Stopping named: [FAILED]
Starting named: [FAILED]
Can anyone tell me what might be wrong here? Everything worked well
until this morning.
I can't imagine that I have done anything to cause a problem?
Bob Goodwin
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
