Sponsored Content
Full Discussion: Chroot DNS RHEL6
Operating Systems Linux Red Hat Chroot DNS RHEL6 Post 302854375 by Duffs22 on Tuesday 17th of September 2013 10:33:21 AM
Old 09-17-2013
Chroot DNS RHEL6

Hi,
Just installed BIND on rhel6 as a primary new DNS server and all went well, digging and resolving as it should.
However, all zone files are listed in the /var/named dir as well as the /var/named/chroot/var/named. Although no dynamic links are shown, they are. This doesn't seem secure to me, is this how chroot should look in rhel6?
Can anyone advise?
R,
D.
 

10 More Discussions You Might Find Interesting

1. Linux

chroot?

If i were to create a new user for my ftp would chroot be the proper command to set there root directory as the file i've put all my FTP stuff in? Also would that jail them, or would they beable to get out of the set directory? (0 Replies)
Discussion started by: byblyk
0 Replies

2. AIX

chroot environment

Hi!! I'm currently running AIX 4.3.3 and i'm trying to setup a chroot environment for the users who use SFTP, i spend a lot time SFTW but i can't make it work. I got openssh3.9p1 whit the chroot patch. Any help is greatly appreciated. (0 Replies)
Discussion started by: samurai79
0 Replies

3. Solaris

Solaris DNS Client For Microsoft DNS Server

hey guys, how to add soalris box as a microsoft DNS Client ? and how to register in the microsoft DNS ?? i managed to query from the DNS server after adding /etc/resolve.conf and editing /etc/nsswitch.conf but i need to register the soalris server (dns Client) into Microsoft DNS automatically.... (3 Replies)
Discussion started by: mduweik
3 Replies

4. UNIX for Advanced & Expert Users

DNS server choice: Windows DNS vs Linux BIND

I'd like to get some opnions on choosing DNS server: Windows DNS vs Linux BIND comparrsion: 1) managment, easy of use 2) Security 3) features 4) peformance 5) ?? I personally prefer Windows DNS server for management, it supports GUI and command line. But I am not sure about security... (2 Replies)
Discussion started by: honglus
2 Replies

5. AIX

DNS with chroot in aix 5.3

i am planning to configure the DNS server with restricted environment by chroot. Can anybody help me that what are all the filesets required to configure DNS with Chroot for aix 5.3 os. And also i need to run the bind with non root user. How can i configure that. I tried googling and... (1 Reply)
Discussion started by: kmvinay
1 Replies

6. Red Hat

DHCP & DNS - Clients get IP but don't register in DNS

I am trying to setup a CentOS 6.2 server that will be doing 3 things DHCP, DNS & Samba for a very small office (2 users). The idea being this will replace a very old Win2k server. The users are all windows based clients so only the server will be Linux based. I've installed CentOS 6.2 with... (4 Replies)
Discussion started by: FireBIade
4 Replies

7. Solaris

BIND in chroot

Hi all, I'm trying to start named in chroot environment manually but i'm getting the following error bash-3.00# cat /etc/release Solaris 10 6/06 s10s_u2wos_09a SPARC Copyright 2006 Sun Microsystems, Inc. All Rights Reserved. Use is... (1 Reply)
Discussion started by: h@foorsa.biz
1 Replies

8. UNIX for Dummies Questions & Answers

[Solved] Not able to do a chroot.

Hi all, I have two doms on my machine. I boot my machine from an rfs in one dom1 and mount the other rfs in the other dom2 at /media. Now I wanted to restrict access of users on dom2 to only their home directories. I do not want them to access any other directories on dom1 or dom2. So I mounted... (2 Replies)
Discussion started by: sai2krishna
2 Replies

9. Homework & Coursework Questions

Configure DNS in rhel6.3

Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted! 1. The problem statement, all variables and given/known data: cant configure dns in virtual box. im using rhel6.3. i have a cd containing rhel which the professor provided us.... (2 Replies)
Discussion started by: rpmacaspac
2 Replies

10. Solaris

DNS client added to DNS server but not working

Hi, We have built a new server (RHEL VM)and added that IP/hostname into dns zone configs file on DNS server (Solaris 10). Reloaded the configuration using and added nameserver into resolv.conf on client. But when I am trying nslookup, its not getting resolved. The nameserver is not able to... (8 Replies)
Discussion started by: snchaudhari2
8 Replies
NAMED(8)							       BIND9								  NAMED(8)

NAME
named - Internet domain name server SYNOPSIS
named [-4] [-6] [-c config-file] [-d debug-level] [-E engine-name] [-f] [-g] [-m flag] [-n #cpus] [-p port] [-s] [-S #max-socks] [-t directory] [-U #listeners] [-u user] [-v] [-V] [-x cache-file] DESCRIPTION
named 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 will read the default configuration file /etc/named.conf, read any initial data, and listen for queries. OPTIONS
-4 Use IPv4 only even if the host machine is capable of IPv6. -4 and -6 are mutually exclusive. -6 Use IPv6 only even if the host machine is capable of IPv4. -4 and -6 are mutually exclusive. -c config-file Use config-file as the configuration file instead of the default, /etc/named.conf. To ensure that reloading the configuration 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. -E engine-name Use a crypto hardware (OpenSSL engine) for the crypto operations it supports, for instance re-signing with private keys from a secure key store. When compiled with PKCS#11 support engine-name defaults to pkcs11, the empty name resets it to no engine. -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. -m flag Turn on memory usage debugging flags. Possible flags are usage, trace, record, size, and mctx. These correspond to the ISC_MEM_DEBUGXXXX flags described in <isc/mem.h>. -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. Note: This option is mainly of interest to BIND 9 developers and may be removed or changed in a future release. -S #max-socks Allow named to use up to #max-socks sockets. Warning: This option should be unnecessary for the vast majority of users. The use of this option could even be harmful because the specified value may exceed the limitation of the underlying system API. It is therefore set only when the default configuration causes exhaustion of file descriptors and the operational environment is known to support the specified number of sockets. Note also that the actual maximum number is normally a little fewer than the specified value because named reserves some file descriptors for its internal use. -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 security on most systems; the way chroot(2) is defined allows a process with root privileges to escape a chroot jail. -U #listeners Use #listeners worker threads to listen for incoming UDP packets on each address. If not specified, named will use the number of detected CPUs. If -n has been set to a higher value than the number of CPUs, then -U may be increased as high as that value, but no higher. -u user Setuid to user after completing privileged operations, such as creating sockets that listen on privileged ports. Note: On Linux, named uses the kernel's capability mechanism to drop all root privileges except the ability to bind(2) to a privileged port and set process resource limits. Unfortunately, this means that the -u option only works 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(2). -v Report the version number and exit. -V Report the version number and build options, and exit. -x cache-file Load data from cache-file into the cache of the default view. Warning: This option must not be used. It is only of interest to BIND 9 developers and may be removed or changed in a future release. SIGNALS
In routine operation, signals should not be used to control the nameserver; rndc 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 Reference Manual. named inherits the umask (file creation mode mask) from the parent process. If files created by named, such as journal files, need to have custom permissions, the umask should be set explicitly in the script used to start the named process. FILES
/etc/named.conf The default configuration file. /var/run/named/named.pid The default process-id file. NOTES
Red Hat SELinux BIND Security Profile: By default, Red Hat ships BIND with the most secure SELinux policy that will not prevent normal BIND operation and will prevent exploitation of all known BIND security vulnerabilities . See the selinux(8) man page for information about SElinux. It is not necessary to run named in a chroot environment if the Red Hat SELinux policy for named is enabled. When enabled, this policy is far more secure than a chroot environment. Users are recommended to enable SELinux and remove the bind-chroot package. With this extra security comes some restrictions: By default, the SELinux policy does not allow named to write any master zone database files. Only the root user may create files in the $ROOTDIR/var/named zone database file directory (the options { "directory" } option), where $ROOTDIR is set in /etc/sysconfig/named. The "named" group must be granted read privelege to these files in order for named to be enabled to read them. Any file created in the zone database file directory is automatically assigned the SELinux file context named_zone_t . By default, SELinux prevents any role from modifying named_zone_t files; this means that files in the zone database directory cannot be modified by dynamic DNS (DDNS) updates or zone transfers. The Red Hat BIND distribution and SELinux policy creates three directories where named is allowed to create and modify files: /var/named/slaves, /var/named/dynamic /var/named/data. By placing files you want named to modify, such as slave or DDNS updateable zone files and database / statistics dump files in these directories, named will work normally and no further operator action is required. Files in these directories are automatically assigned the 'named_cache_t' file context, which SELinux allows named to write. Red Hat BIND SDB support: Red Hat ships named with compiled in Simplified Database Backend modules that ISC provides in the "contrib/sdb" directory. Install bind-sdb package if you want use them The SDB modules for LDAP, PostGreSQL, DirDB and SQLite are compiled into named-sdb. See the documentation for the various SDB modules in /usr/share/doc/bind-sdb-*/ . Red Hat system-config-bind: Red Hat provides the system-config-bind GUI to configure named.conf and zone database files. Run the "system-config-bind" command and access the manual by selecting the Help menu. SEE ALSO
RFC 1033, RFC 1034, RFC 1035, named-checkconf(8), named-checkzone(8), rndc(8), lwresd(8), named.conf(5), BIND 9 Administrator Reference Manual. AUTHOR
Internet Systems Consortium COPYRIGHT
Copyright (C) 2004-2009, 2011, 2013 Internet Systems Consortium, Inc. ("ISC") Copyright (C) 2000, 2001, 2003 Internet Software Consortium. BIND9 May 21, 2009 NAMED(8)
All times are GMT -4. The time now is 06:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy