设为首页 收藏本站
查看: 2917|回复: 1

[经验分享] 架设RHCE考试服务器

[复制链接]

尚未签到

发表于 2015-4-18 10:24:13 | 显示全部楼层 |阅读模式
之前给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-servers  172.24.254.254;
#
  option time-offset    -18000;  # Eastern Standard Time
#  option ntp-servers    192.168.1.1;
#  option netbios-name-servers  192.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



$TTL  86400
@  IN  SOA  @  root.ns (
        42  ;
        3H  ;
        15M  ;
        1W  ;
        1D  );
    IN  NS  ns
ns    IN  A  172.24.254.254
server1    IN  A  172.24.254.254
station18  IN  A  172.24.254.18
www18    IN  CNAME  station18





NIS:

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

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

#vi /etc/ypserv.conf

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

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

运维网声明 1、欢迎大家加入本站运维交流群:群②:261659950 群⑤:202807635 群⑦870801961 群⑧679858003
2、本站所有主题由该帖子作者发表,该帖子作者与运维网享有帖子相关版权
3、所有作品的著作权均归原作者享有,请您和我们一样尊重他人的著作权等合法权益。如果您对作品感到满意,请购买正版
4、禁止制作、复制、发布和传播具有反动、淫秽、色情、暴力、凶杀等内容的信息,一经发现立即删除。若您因此触犯法律,一切后果自负,我们对此不承担任何责任
5、所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其内容的准确性、可靠性、正当性、安全性、合法性等负责,亦不承担任何法律责任
6、所有作品仅供您个人学习、研究或欣赏,不得用于商业或者其他用途,否则,一切后果均由您自己承担,我们对此不承担任何法律责任
7、如涉及侵犯版权等问题,请您及时通知我们,我们将立即采取措施予以解决
8、联系人Email:admin@iyunv.com 网址:www.yunweiku.com

所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其承担任何法律责任,如涉及侵犯版权等问题,请您及时通知我们,我们将立即处理,联系人Email:kefu@iyunv.com,QQ:1061981298 本贴地址:https://www.yunweiku.com/thread-58393-1-1.html 上篇帖子: 邁向 RHCE 之路 (Day26) 下篇帖子: 2012年4月RHCE6.0考试心得
累计签到:219 天
连续签到:1 天
发表于 2017-8-30 13:51:00 | 显示全部楼层
确实是个好文章,可惜写的乱。

运维网声明 1、欢迎大家加入本站运维交流群:群②:261659950 群⑤:202807635 群⑦870801961 群⑧679858003
2、本站所有主题由该帖子作者发表,该帖子作者与运维网享有帖子相关版权
3、所有作品的著作权均归原作者享有,请您和我们一样尊重他人的著作权等合法权益。如果您对作品感到满意,请购买正版
4、禁止制作、复制、发布和传播具有反动、淫秽、色情、暴力、凶杀等内容的信息,一经发现立即删除。若您因此触犯法律,一切后果自负,我们对此不承担任何责任
5、所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其内容的准确性、可靠性、正当性、安全性、合法性等负责,亦不承担任何法律责任
6、所有作品仅供您个人学习、研究或欣赏,不得用于商业或者其他用途,否则,一切后果均由您自己承担,我们对此不承担任何法律责任
7、如涉及侵犯版权等问题,请您及时通知我们,我们将立即采取措施予以解决
8、联系人Email:admin@iyunv.com 网址:www.yunweiku.com

您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

扫码加入运维网微信交流群X

扫码加入运维网微信交流群

扫描二维码加入运维网微信交流群,最新一手资源尽在官方微信交流群!快快加入我们吧...

扫描微信二维码查看详情

客服E-mail:kefu@iyunv.com 客服QQ:1061981298


QQ群⑦:运维网交流群⑦ QQ群⑧:运维网交流群⑧ k8s群:运维网kubernetes交流群


提醒:禁止发布任何违反国家法律、法规的言论与图片等内容;本站内容均来自个人观点与网络等信息,非本站认同之观点.


本站大部分资源是网友从网上搜集分享而来,其版权均归原作者及其网站所有,我们尊重他人的合法权益,如有内容侵犯您的合法权益,请及时与我们联系进行核实删除!



合作伙伴: 青云cloud

快速回复 返回顶部 返回列表