zoukankan      html  css  js  c++  java
  • Bind + AD HOWTO

    named目录 bind:bind执行

    http://www.ibiblio.org/gferg/ldp/BIND+AD-HOWTO/

    2. Start configuring

    Alright, let's get started.

    2.1 Compiling Bind

    For complete and detailed compilation and debugging on Bind, please refer to the Bind-HOWTO as this is not covered here.

    First, let's get the latest version:
    wget ftp://ftp.isc.org/isc/bind9/9.2.0/bind-9.2.0.tar.gz

    To unpack and compile:
    tar zxvf bind-9.2.0.tar.gz
    cd bind-9.2.0
    ./configure --prefix=/var/named
    make

    To install (must be root):
    make install

    Now Bind is configured to put all its configuration files in /var/named. If you wish to put it elsewhere you may, but keep in mind that this document will base itself on this location.

    2.2 /etc/named.conf

    First off, we will want to make an ACL for the AD servers on the network assuming you're using 10.10.10.0/24 as internal IP's. This is not necessary, but will make the config file easier to read if you have several AD servers.
    The following information is to be entered in /etc/named.conf in addition to your own options.

      acl "ADservers" {
      10.10.10.2; 10.10.10.3
      };
    

    It is also possible to specify whole network blocks although this is not recommended for security reasons.

    Next, we want to specify the location where the dynamic files entries will be stored. In this example we will use /var/named/etc.

      zone "10.10.10.in-addr.arpa" {
      type master;
      file "reverse/10.10.10.db";
      allow-update {ADservers;};
      };
    
      zone "domain.com" {
      type master;
      file "etc/domain.com.db";
      check-names ignore;
      allow-update {ADservers;};
      };
    
      zone "_msdcs.domain.com" {
      type master;
      file "etc/_msdcs.domain.com.db";
      check-names ignore;
      allow-update {ADservers;};
      };
    
      zone "_sites.domain.com" {
      type master;
      file "etc/_sites.domain.com.db";
      check-names ignore;
      allow-update {ADservers;};
      };
    
      zone "_tcp.domain.com" {
      type master;
      file "etc/_tcp.domain.com.db";
      check-names ignore;
      allow-update {ADservers;};
      };
    
      zone "_udp.domain.com" {
      type master;
      file "etc/_udp.domain.com.db";
      check-names ignore;
      allow-update {ADservers;};
      };
    

    2.3 Touching the dynamic zone files

    The dynamic zone files (_domain.com, _tcp.domain.com, _tcp.domain.com, _udp.domain.com, _msdcs.domain.com and _sites_domain.com) need to exist before we start up the system. Insert the following RR's (Resource Records) into each dynamic zone file. Beware that _tcp.domain.com on line three and $origin _tcp.domain.com on line elleven must be changed to reflect its filename.

    
      $ORIGIN .
      $TTL 86400 ; 1 day
      _tcp.domain.com		 IN	SOA hostname.domain.com. hostmaster.domain.com. (
    								2002010101 ; Todays serial
    								28800 ; refresh (8 hours)
    								7200 ; retry (2 hours)
    								2419200 ; expire (4 weeks)
    								86400 ; minimum (1 day)
    								)
    						NS ns.domain.com.
      $ORIGIN _tcp.domain.com.
    

    2.4 Does it work?

    Do a 'killall named' and 'named' to restart the named daemon. The locator records will automatically update themselves when the client machines are rebooted.
    To verify that everything is in order, do a 'tail -f /var/log/messages'. You should se something that looks like this:

      Jan 01 15:44:21 xxx named[4304]: adding an RR
      Jan 01 15:44:21 xxx named[4304]: journal file etc/domain.com.db.jnl does not exist, creating it
      Jan 01 15:44:22 xxx named[4304]: adding an RR
      Jan 01 15:44:22 xxx named[4304]: journal file etc/_tcp.domain.com.db.jnl does not exist, creating it
      Jan 01 15:44:22 xxx named[4304]: adding an RR
      Jan 01 15:44:22 xxx named[4304]: journal file etc/_msdcs.domain.com.db.jnl does not exist, creating it
      Jan 01 15:44:22 xxx named[4304]: adding an RR
      Jan 01 15:44:22 xxx named[4304]: journal file etc/_udp.domain.com.db.jnl does not exist, creating it
      Jan 01 15:44:22 xxx named[4304]: adding an RR
      Jan 01 15:49:20 xxx named[4304]: journal file etc/_sites.domain.com.db.jnl does not exist, creating
    

    The "journal file etc/_*.domain.com.db.jnl does not exist, creating it" message is generated when a Windows 2000 server (non-AD) attempts to update BIND9 configured with the conf file. This is a good thing.

  • 相关阅读:
    shell 操作钉钉机器人实现告警提醒
    谨慎 mongodb 关于数字操作可能导致类型及精度变化
    数据库如何应对保障大促活动
    SQL Server Alwayson架构下 服务器 各虚拟IP漂移监控告警的功能实现 -1(服务器视角)
    通过 Telegraf + InfluxDB + Grafana 快速搭建监控体系的详细步骤
    MySQL数据库Inception工具学习与测试 笔记
    MongoDB 中数据的替换方法实现 --类Replace()函数功能
    MongoDB 中的【加减乘除】运算
    MySQL索引设计需要考虑哪些因素?
    关于SQL Server 数据库归档的一些思考和改进
  • 原文地址:https://www.cnblogs.com/studio313/p/1504378.html
Copyright © 2011-2022 走看看