赵小黑 发表于 2015-4-18 10:24:13

架设RHCE考试服务器

之前给RHCT模考的同学配过一个考试服务器,哈哈,不错。现在又考CE了,其实也差不多,早就配好了,今天有时间总结一下吧。

前几天冲哥配的考试服务器本来想拷过来,太大了。就没有拷。


其实服务器里面最重要的就是DHCP,DNS和一个NIS服务器了,别的也没啥,要想只达到功能上的要求,挺简单的,我就简单的配一下吧。

DHCP:

把example copy过来。直接盖了/etc/dhcpd.conf得了,里面本来也没啥。

ddns-update-style interim;
ignore client-updates;

subnet 172.24.0.0 netmask 255.255.0.0 {

# --- default gateway
option routers      172.24.254.254;
#option subnet-mask    255.255.0.0;
#
#option nis-domain    "domain.org";
option domain-name    "example.com";
option domain-name-servers172.24.254.254;
#
option time-offset    -18000;# Eastern Standard Time
#option ntp-servers    192.168.1.1;
#option netbios-name-servers192.168.1.1;
# --- Selects point-to-point node (default is hybrid). Don't change this unless
# -- you understand Netbios very well
#option netbios-node-type 2;
#
range dynamic-bootp 172.24.254.18 172.24.254.254;
default-lease-time 21600;
max-lease-time 43200;

# we want the nameserver to appear at a fixed address
host station18 {
    hardware ethernet 00:0C:29:C0:E8:9E;
                #这个是我绑的一个MAC。
    fixed-address 172.24.254.18;
    option host-name "station18";
}
}


完事了。

DNS:

还是一样,把named.conf copy过来。一把注释



//
// Sample named.conf BIND DNS server 'named' configuration file
// for the Red Hat BIND distribution.
//
// See the BIND Administrator's Reference Manual (ARM) for details, in:
//   file:///usr/share/doc/bind-*/arm/Bv9ARM.html
// Also see the BIND Configuration GUI : /usr/bin/system-config-bind and
// its manual.
//
options
{
/* make named use port 53 for the source of all queries, to allow
         * firewalls to block all ports except 53:
         */
query-source    port 53;
query-source-v6 port 53;

// Put files that named is allowed to write in the data/ directory:
directory "/var/named"; // the default
dump-file   "data/cache_dump.db";
      statistics-file   "data/named_stats.txt";
      memstatistics-file   "data/named_mem_stats.txt";

};
zone "example.com" {
type master;
file "example.com";
};
logging
{
/*      If you want to enable debugging, eg. using the 'rndc trace' command,
*      named will try to write the 'named.run' file in the $directory (/var/named).
*      By default, SELinux policy does not allow named to modify the /var/named directory,
*      so put the default debug log file in data/ :
*/
      channel default_debug {
                file "data/named.run";
                severity dynamic;
      };
};
//
// All BIND 9 zones are in a "view", which allow different zones to be served
// to different types of client addresses, and for options to be set for groups
// of zones.
//
// By default, if named.conf contains no "view" clauses, all zones are in the
// "default" view, which matches all clients.
//
// If named.conf contains any "view" clause, then all zones MUST be in a view;
// so it is recommended to start off using views to avoid having to restructure
// your configuration files in the future.
//
//view "localhost_resolver"
//{
/* This view sets up named to be a localhost resolver ( caching only nameserver ).
* If all you want is a caching-only nameserver, then you need only define this view:
*/
//match-clients   { localhost; };
//match-destinations{ localhost; };
//recursion yes;
# all views must contain the root hints zone:
//include "/etc/named.root.hints";

      /* these are zones that contain definitions for all the localhost
         * names and addresses, as recommended in RFC1912 - these names should
   * ONLY be served to localhost clients:
   */
//include "/etc/named.rfc1912.zones";
//};
//view "internal"
//{
/* This view will contain zones you want to serve only to "internal" clients
   that connect via your directly attached LAN interfaces - "localnets" .
*/
//match-clients    { localnets; };
//match-destinations{ localnets; };
//recursion yes;
// all views must contain the root hints zone:
//include "/etc/named.root.hints";

      // include "named.rfc1912.zones";
// you should not serve your rfc1912 names to non-localhost clients.

// These are your "authoritative" internal zones, and would probably
// also be included in the "localhost_resolver" view above :

//zone "my.internal.zone" {
//    type master;
//    file "my.internal.zone.db";
//};
//zone "my.slave.internal.zone" {
//    type slave;
//    file "slaves/my.slave.internal.zone.db";
//    masters { /* put master nameserver IPs here */ 127.0.0.1; } ;
    // put slave zones in the slaves/ directory so named can update them
//};
//zone "my.ddns.internal.zone" {
//    type master;
//    allow-update { key ddns_key; };
//    file "slaves/my.ddns.internal.zone.db";
    // put dynamically updateable zones in the slaves/ directory so named can update them
//};      
//};
//key ddns_key
//{
//algorithm hmac-md5;
//secret "use /usr/sbin/dns-keygen to generate TSIG keys";
//};
//view    "external"
//{
/* This view will contain zones you want to serve only to "external" clients
* that have addresses that are not on your directly attached LAN interface subnets:
*/
//match-clients    { !localnets; !localhost; };
//match-destinations{ !localnets; !localhost; };

//recursion no;
// you'd probably want to deny recursion to external clients, so you don't
      // end up providing free DNS service to all takers

// all views must contain the root hints zone:
//include "/etc/named.root.hints";

// These are your "authoritative" external zones, and would probably
      // contain entries for just your web and mail servers:

//zone "my.external.zone" {
//    type master;
//    file "my.external.zone.db";
//};
//};





再配一个zone文件example.com



$TTL86400
@INSOA@root.ns (
      42;
      3H;
      15M;
      1W;
      1D);
    INNSns
ns    INA172.24.254.254
server1    INA172.24.254.254
station18INA172.24.254.18
www18    INCNAMEstation18





NIS:

#useradd -d /rhome/station18/nisuser18
#vi /etc/passwd

?????? 把/rhome/staion18/nisuser18改成/rhome/nisuser18(这一步的目的是让client autofs的时间能显示家目录)

#vi /etc/ypserv.conf

????取掉最后一行注释。

行了,其它就不用说了,今天快停电了就简单地说一下吧。相信有基础的同学能看明白,我只是说说关键的和需要注意的地方而已。

四色定理 发表于 2017-8-30 13:51:00

确实是个好文章,可惜写的乱。
页: [1]
查看完整版本: 架设RHCE考试服务器