Sponsored Content
Top Forums UNIX for Advanced & Expert Users error starting named service in CentOS Post 302721683 by DGPickett on Thursday 25th of October 2012 03:58:34 PM
Old 10-25-2012
Well, you have no zones in your view and only one view (they are supposed to divide things): Two-in-one DNS server with BIND9 | HowtoForge - Linux Howtos and Tutorials
 

10 More Discussions You Might Find Interesting

1. AIX

Service starting Problem

Dear All, When i am start the service netd i am facing the problem 0513-015 The inetd Subsystem could not be started Please check subsystem resources and try again later. please suggest me. It is urgent (1 Reply)
Discussion started by: pernasivam
1 Replies

2. UNIX for Dummies Questions & Answers

Starting a service at startup.

Hi guys I want to start a service and a script SiteMonitor.sh at startup. To start with i have modified /etc/rc.local file. Here is the content of my /etc/rc.local file. #!/bin/sh # # This script will be executed *after* all the other init scripts. # You can put your own... (3 Replies)
Discussion started by: pinga123
3 Replies

3. Linux

named service will not start, connection refused

Hi guys Our secondary named server has an issue when we start the named service: # service named restart Stopping named: rndc: connect failed: connection refused # service named status rndc: connect failed: connection... (1 Reply)
Discussion started by: wbdevilliers
1 Replies

4. Solaris

Service not starting Solaris10

On one of our server inetd service has stuck in transition state , tried restarting it but it does not do any thing and there is no associated inetd process for the same , how can i start it .. w/o rebooting it svcs inetd STATE STIME FMRI online* 16:44:55... (3 Replies)
Discussion started by: fugitive
3 Replies

5. SuSE

named service issue on Suse

Hi Experts, I have a virtual server of SUSE Linux Enterprise Server 10 (x86_64). I am having strange issue of Naming services. Every 1 or 2 hours, named service stops working on this server and then I have to start it from "/etc/init./named start" I am not getting clue, where should I start... (0 Replies)
Discussion started by: solaris_1977
0 Replies

6. Red Hat

Named.conf file missing Centos 5.

hello everyone, I have install centos 5 recently.The file /etc/named.conf not found. I have installed BIND using yum. so now what to do ?? should i create named.conf file manually ??? please help me. thanks, sharlin. :) (1 Reply)
Discussion started by: sharlin
1 Replies

7. Red Hat

Named not starting in CentOS 6.3

I just installed bind* and then configured named.conf and zone files. but when I am stating named its giving below error. # /etc/init.d/named restart Stopping named: Starting named: and in log i... (1 Reply)
Discussion started by: Priy
1 Replies

8. Solaris

Rpcbind service not starting

Hello all, I have read just about every rpcbind not starting thread and article on the internet it seems, but I have not found a solution to my problem as of yet. I have a solaris 10 server that has been running with no problems for a while. The other day it crashed and would not boot to the gui... (2 Replies)
Discussion started by: Madrox72
2 Replies

9. Red Hat

Httpd service not starting... Error "Documentroot must be a directory"

I am working with CentOS 6.5. Indeed the document root /var/www/html is a directory and it is a mount point of one file system (not NFS) I observed, if I unmount that file system, I could able to start httpd. Is it restricted in CentOS 6.X that the Documentroot can not be a mount point? ... (5 Replies)
Discussion started by: atanubanerji
5 Replies

10. Solaris

Error when running starting server service

Hi I have installed using tar a program called rabbitmq, and when I try to start it according to documentation, I get the following error: /usr/local/sbin/rabbitmq_server-3.6.14/sbin# ./rabbitmq-server ./rabbitmq-server: .: local: not found ... (7 Replies)
Discussion started by: fretagi
7 Replies
LWRESD(8)																 LWRESD(8)

NAME
lwresd - lightweight resolver daemon SYNOPSIS
lwresd [ -C config-file ] [ -d debug-level ] [ -f ] [ -g ] [ -i pid-file ] [ -n #cpus ] [ -P port ] [ -p port ] [ -s ] [ -t direc- tory ] [ -u user ] [ -v ] DESCRIPTION
lwresd is the daemon providing name lookup services to clients that use the BIND 9 lightweight resolver library. It is essentially a stripped-down, caching-only name server that answers queries using the BIND 9 lightweight resolver protocol rather than the DNS protocol. lwresd listens for resolver queries on a UDP port on the IPv4 loopback interface, 127.0.0.1. This means that lwresd can only be used by processes running on the local machine. By default UDP port number 921 is used for lightweight resolver requests and responses. Incoming lightweight resolver requests are decoded by the server which then resolves them using the DNS protocol. When the DNS lookup com- pletes, lwresd encodes the answers in the lightweight resolver format and returns them to the client that made the request. If /etc/resolv.conf contains any nameserver entries, lwresd sends recursive DNS queries to those servers. This is similar to the use of forwarders in a caching name server. If no nameserver entries are present, or if forwarding fails, lwresd resolves the queries autonomously starting at the root name servers, using a built-in list of root server hints. OPTIONS
-C config-file Use config-file as the configuration file instead of the default, /etc/resolv.conf. -d debug-level Set the daemon's debug level to debug-level. Debugging traces from lwresd become more verbose as the debug level increases. -f Run the server in the foreground (i.e. do not daemonize). -g Run the server in the foreground and force all logging to stderr. -n #cpus Create #cpus worker threads to take advantage of multiple CPUs. If not specified, lwresd will try to determine the number of CPUs present and create one thread per CPU. If it is unable to determine the number of CPUs, a single worker thread will be created. -P port Listen for lightweight resolver queries on port port. If not specified, the default is port 921. -p port Send DNS lookups to port port. If not specified, the default is port 53. This provides a way of testing the lightweight resolver daemon with a name server that listens for queries on a non-standard port number. -s Write memory usage statistics to stdout on exit. Note: This option is mainly of interest to BIND 9 developers and may be removed or changed in a future release. -t directory chroot() to directory after processing the command line arguments, but before reading the configuration file. Warning: This option should be used in conjunction with the -u option, as chrooting a process running as root doesn't enhance secu- rity on most systems; the way chroot() is defined allows a process with root privileges to escape a chroot jail. -u user setuid() to user after completing privileged operations, such as creating sockets that listen on privileged ports. -v Report the version number and exit. FILES
/etc/resolv.conf The default configuration file. /var/run/lwresd.pid The default process-id file. SEE ALSO
named(8), lwres(3), resolver(5). AUTHOR
Internet Software Consortium BIND9 June 30, 2000 LWRESD(8)
All times are GMT -4. The time now is 05:34 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy