nslookup *** Can't initialize resolver Post: 302075029

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Variable Initialize

Hi, i m trying to loop a variable value, Basically i m reading variable value from an input file and using in rest of the program. Bu my problem is when i first time read value and assign to variable it works fine, but in second read it concatinate second value to first value with a LF. I want to...

2. SCO

initialize lp job

I use SCO UNIX from 2 years I need a command or procedure to make all log files empty and restart all counters like lp job number :( :confused: :(

3. HP-UX

Can not initialize the floppy

Hello Everyone, Has anyboby ever come across the problem when fd refuses to get initialised. I try to use mediainit command, the fd is being accessed (the fd's LIT is green for some secs) but then I get the message - "Initialize media command failed - permission denied" I checked the diskette,...

4. UNIX and Linux Applications

BIND (Name Server & Resolver)

Hi, i'm looking information about how BIND (Name Server & Resolver) works... And how Server/Client communicates... I found a lot of information of what BIND is and how to configure it, but nothing about how it works, does anybody know where i can found something useful?? I don't need code, just...

5. Shell Programming and Scripting

initialize file to zero

hi can anyone tell how to initialize a file to zero

6. Shell Programming and Scripting

Initialize a variable

Hi All, Please can you advise on how can I initialize a variable with a line. Suppose i want to initialize x with line redirects.www.virginatlantic.com.conf Best Regards, Shazin

7. Red Hat

Fedora Initialize disklabel

What is the point of Fedora Initialize disklabel and how does it work? How do I check what my current Fedora's disklabel is initialized to?

8. Shell Programming and Scripting

initialize a variable only once

hi, i have a script which needs to be run every 10 minutes.This is achieved using crontab utility, it is checking Number of calls on a service... if number of calls are not increasing then it will stop the service else do nothing. Now in the script, i fetch the current value in variable...

9. Web Development

(WHM) Primary Resolver and Nameserver confusion

Okay, I know generally how the internet works but here I am confused. Every website that I've worked on prior to this had a vendor providing Nameserver services -Meaning that I just pointed my DNS to their server and they do the rest. Now, I am confused by what the Primary Resolver is...

LEARN ABOUT REDHAT

lwresd

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)