Sponsored Content
Special Forums UNIX and Linux Applications BIND (Name Server & Resolver) Post 302227625 by jamison_utter on Thursday 21st of August 2008 04:10:25 PM
Old 08-21-2008
Are you asking more on a fundamental level? That would be just how DNS works, nothing special about BIND in the client/server part.

Cricket Liu has a book that has some first chapters that talk about the basics of DNS.

Does that help?
 

9 More Discussions You Might Find Interesting

1. IP Networking

the bind server can't start

I use the "rndc start" to start the bind server . but the server can't be started. it says "connection refused" I don't know what happened,and how to resolve it. Would somebody can help me? (2 Replies)
Discussion started by: cnyifeng
2 Replies

2. UNIX for Dummies Questions & Answers

nslookup *** Can't initialize resolver

Has anyone seen this message before? I have a DNS problem. Recently DNS has been moved to two new servers, which I can ping. I changed the /etc/resolv.conf to point to these boxes but now I get the *** Can't initialize resolver message. Any ideas? (2 Replies)
Discussion started by: korfnz
2 Replies

3. UNIX for Dummies Questions & Answers

FTP, DNS & BIND

Hi GURUs, I have two queries. 1)I know I can use FTP clients for my File transfer needs, but I want to learn FTP thru command line, any one can point me to some good online resource available to learn FTP command line with examples, of course free except UNIX man pages. 2) Our company has... (4 Replies)
Discussion started by: patras
4 Replies

4. Solaris

How to bind from a NIS slave server

Hi All, I have a client already binded with a NIS master server. Now, I want to bind this particular client to one of NIS slave. How to do it? Thanks, Deepak (2 Replies)
Discussion started by: naw_deepak
2 Replies

5. Debian

nss_ldap failed to bind to LDAP server

Hi every body! I have an debian lenny server with samba and openldap on it. 1. Problem: i can not login ldap user auth.log: nss_ldap: could not connect to any LDAP server as cn=admin,dc=innsbruck,dc=sti,dc=at - Can't contact LDAP server 2. Problem: auth.log: nss_ldap: failed to bind to... (1 Reply)
Discussion started by: magge
1 Replies

6. IP Networking

Freebsd Bind DNS server - multiple subnets

Hello all, I have configured Freebsd 8.1 Bind DNS as DNS server for intrenal domain and clients on one subnet 192.168.10.0/24 . What do I have to change in zone file and in in-addr.arpa zone file if I have two additional subsets 192.168.20.0/24 and 192.168.30.0/24? Do I have to create another... (0 Replies)
Discussion started by: kreno
0 Replies

7. Red Hat

Reporting and administration tool for bind server

Hi Friends, I have two DNS (bind 9) servers (master and slave) running in my network. I want to impliment one reporting and administration tool for these DNS servers. Please suggest me which one is good for this. Regards, Arumon (2 Replies)
Discussion started by: arumon
2 Replies

8. Solaris

BIND DNS Server issue on Solaris 10

Hi all, I have some sort of problem with BIND DNS server my environment as follows. bash-3.00# cat /etc/release Solaris 10 6/06 s10s_u2wos_09a SPARC Copyright 2006 Sun Microsystems, Inc. All Rights Reserved. Use is subject to... (3 Replies)
Discussion started by: h@foorsa.biz
3 Replies

9. Ubuntu

Bind dns server zone file

I have a couple of zone conf files for the BIND server. There are some records that contains the "IN" statement and some do not. But anyway this works. So my question is what this "IN" is intended for? Here is the zone file example: ORIGIN . $ttl 60 example.com. IN SOA ... (4 Replies)
Discussion started by: andriesh
4 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 02:51 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy