Sponsored Content
Full Discussion: DNS daemons
Special Forums IP Networking DNS daemons Post 11116 by eNTer on Thursday 29th of November 2001 06:51:45 AM
Old 11-29-2001
DNS Daemon [bind]

Hi! There is a security problem with some versions of the name daemon, in some cases this daemon gives root access to someone which uses an exploit remotely. To avoid such things you must start bind in a sandbox, chrooted, or as a user which does not have high priviledhes in the system. so, the command line becomes [for most systems]:
# named -u daemon
For a FreeBSD machine the command line is
# named -u bind -g bind if you changed /etc/rc.conf and have specified named_flags="-u bind -g bind" and if you have specified to start the named at boot time with the following line in /etc/rc.conf: named_enable="YES", and in the /etc/named.conf you should specify that the directory is /etc/namedb.
 

9 More Discussions You Might Find Interesting

1. Cybersecurity

root owner of daemons?

Hi all, what happens if i have a service running as root? if it is exploited what would happen? can a hacker actually becomes a hacker and screw up my whole box? thanks (1 Reply)
Discussion started by: xNYx
1 Replies

2. UNIX for Dummies Questions & Answers

Daemons

MYSQL-daemon don't started automatically by system-start. And same trouble with httpd too. I have SuSE 8.0. What can I do ? Thanks.... (6 Replies)
Discussion started by: Pennywize
6 Replies

3. Linux

A doubt on Daemons

Hi there! I'm a bit curious on something about Daemons.... Supose you have two processes say A and B, where B is a daemon. A is totally independent from B. Is there a way for A to find out B's return code? Is there a way for A to find out when B ends? Thanks! (4 Replies)
Discussion started by: marioh
4 Replies

4. Solaris

SUN SOLARIS boot: start daemons

Hi, I have a problem on a Solaris 9 server! After a restart some daemons don't start and I have to start them manually! I thing that everything is ok in the /sbin/rc3 script! And if I run manually the "/etc/init.d/xxx start" the services start without problem. I didn't find anything in... (1 Reply)
Discussion started by: ctap
1 Replies

5. UNIX for Dummies Questions & Answers

Starting daemons at reboot.

I rebooted my server (solaris 5.8) and I had to manually start the cron and mailx daemons. How do I get these to automatically start at reboot? Thanks in advance. (2 Replies)
Discussion started by: shorty
2 Replies

6. Shell Programming and Scripting

piping and backgroud processes (daemons)

Hello to all, I've a strage problem here: a perl script that parses the output of sar -q 300 0 (one line of performace data each 5 min. infinately) works fine from the CLI. It processes one line output every 5 minutes. If i disconnect it from the terminal (executing it with cron, nohup startporc... (2 Replies)
Discussion started by: demwz
2 Replies

7. Shell Programming and Scripting

daemons definition

hi there, can somebody give me a definition for daemons, or example what are they !! and what the use for? i've done some research and all what i found is /etc/... or /usr/bin/... and i haven't quietly got the concept. any ideas !! Thanks. (5 Replies)
Discussion started by: new2Linux
5 Replies

8. HP-UX

status of daemons

Hi there all, Hey, is there a way to get the status of all daemons running on a HPUX? in an easy way? Like the same way how to vieuw the status of packages in cmviewcl. Thanks! (1 Reply)
Discussion started by: draco
1 Replies

9. Solaris

Command to list down all daemons in Solaris

Hi All, Is there any command to list all running daemons in Solaris. I should able to see only running daemons. Regards, SKumar (5 Replies)
Discussion started by: nskumar
5 Replies
named(1M)                                                 System Administration Commands                                                 named(1M)

NAME
named - Internet domain name server SYNOPSIS
named [-fgsv] [-c config-file] [-d debug-level] [-n #cpus] [-p port] [-t directory] [-u user] [-x cache-file] DESCRIPTION
The named utility is a Domain Name System (DNS) server, part of the BIND 9 distribution from ISC. For more information on the DNS, see RFCs 1033, 1034, and 1035. When invoked without arguments, named reads the default configuration file /etc/named.conf, reads any initial data, and listens for queries. OPTIONS
The following options are supported: -c config-file Use config-file as the configuration file instead of the default /etc/named.conf. To ensure that reloading the configura- tion file continues to work after the server has changed its working directory due to to a possible directory option in the configuration file, config-file should be an absolute pathname. -d debug-level Set the daemon's debug level to debug-level. Debugging traces from named become more verbose as the debug level increases. -f Run the server in the foreground (that is, 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, named 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 queries on port port. If not specified, the default is port 53. -s Write memory usage statistics to stdout on exit. This option is mainly of interest to BIND 9 developers and might be removed or changed in a future release. -t directory Change the root directory using chroot(2) to directory after processing the command line arguments, but before reading the configuration file. 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 Set the real user ID using setuid(2) to user after completing privileged operations, such as creating sockets that listen on privileged ports. On Linux, named uses the kernel's capability mechanism to drop all root privileges except the ability to use bind(3SOCKET) to bind to a privileged port and set process resource limits. Unfortunately, this means that the -u option works only when named is run on kernel 2.2.18 or later, or kernel 2.3.99-pre3 or later, since previous kernels did not allow privileges to be retained after setuid(). -v Report the version number and exit. -x cache-file Load data from cache-file into the cache of the default view. This option must not be used. It is of interest only to BIND 9 developers and might be removed or changed in a future release. SIGNALS
In routine operation, signals should not be used to control the nameserver; rndc(1M) should be used instead. SIGHUP Force a reload of the server. SIGINT, SIGTERM Shut down the server. The result of sending any other signals to the server is undefined. CONFIGURATION
The named configuration file is too complex to describe in detail here. A complete description is provided in the BIND 9 Administrator Ref- erence Manual. FILES
/etc/named.conf default configuration file /var/run/named.pid default process-ID file ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | |Availability |SUNWbind9 | |Interface Stability |External | +-----------------------------+-----------------------------+ SEE ALSO
rndc(1M), chroot(2), setuid(2), bind(3SOCKET), attributes(5) RFC 1033, RFC 1034, RFC 1035 BIND 9 Administrator Reference Manual NOTES
Source for BIND9 is available in the SUNWbind9S package. SunOS 5.10 15 Dec 2004 named(1M)
All times are GMT -4. The time now is 06:04 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy