"Fossies" - the Fresh Open Source Software Archive

Member "webbind_0.98/INSTALL" (5 Jan 2002, 4554 Bytes) of package /linux/misc/dns/old/WeBBind_0.98.tar:


As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard) with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file.

    1 Requirements
    2 =============================================================
    3 Every DNS server must have the filesystem structure indicate below
    4 and the appropriate settings in named.conf (again indicate below).
    5 The named daemon must run under account with the same ID on
    6 every DNS managed .
    7 On WeBBind server that account is used
    8 run the http daemon and to operate on the mounted
    9 filesystem from the named servers.
   10 
   11 ========Filesystem structure for dns servers managed with WeBBind is:
   12 
   13   domain/			(root of exported filesystem)
   14 	/bin			(contain the ndc executable owned by root and 4755)
   15 	/etc			(contain named.conf)
   16 	/var			(contain logs)
   17 	    /run		
   18 	/zones			(contain definition file for zones)
   19 	
   20 ========The entirely structure is owned by the same user ID used for run BIND.
   21 	
   22 	
   23 	
   24 ========Tipically named.conf head . The best part is the activation of log message
   25 	out of original syslogd outpout file.
   26 
   27 	options {
   28         directory "/domain/zones";
   29         pid-file "/domain/var/run/named.pid";
   30         allow-transfer { none; };
   31 };
   32 
   33 logging {
   34         channel logonfile {
   35                         file "/domain/var/named.log" versions 8 size 1M;
   36                         severity info;
   37                         print-category yes;
   38                         print-severity yes;
   39                         print-time yes;
   40                         };
   41         category default { logonfile; };
   42 };
   43 
   44 =============================================================
   45 
   46 
   47 
   48 
   49 Installation
   50 =============================================================
   51 
   52 
   53 1) Designate an HTTP Server PHP capable (with "register_globals=On" and 
   54    session.auto_start=1 in php.ini) to become a WeBBind server.
   55    Expand the WeBBind package in an accessible dir and tuning it for
   56    the web access (i.e.: http.config, .htaccess ). I suggest to create
   57    a simbolic link webbind -> <latest_release>, thus in future the only file
   58    that you have to modify or copy is global.php .
   59    Annotate the user ID who run the httpd instance.
   60 
   61 2) On every BIND server involved make the bind daemon to run with the
   62    same user ID used on WeBBind httpd instance previously coonfigured (this step is required
   63    to proper file read\write operation from WeBBind ) .
   64    Export via NFS the root of the suggested file system structure
   65    of bind server .
   66 
   67 4) On the WeBBind server su'ed to the user ID used for run
   68    the httpd and bind daemons.
   69    Create a base directory owned by this user to use as
   70    WeBBind working directory . 
   71    Into this new directory create the appropriate directory
   72    for use as mount point to the NFS exported file system from
   73    the DNS servers, naming it with the FQDN of the managed DNS servers.
   74 
   75    ============= IMPORTANT !!! ================
   76    The name of the directory must be equal to 
   77    the FQDN of the managed name servers .
   78    ============= IMPORTANT !!! ================
   79    
   80 5) Mount the exported mount filesystem from the named servers to the appropriate dir
   81    in the WeBBind server.
   82 
   83 6) Edit the file global.php to reflect the architetture of your site (look in global.php.template).
   84 
   85 
   86 
   87 Multiple User and Locking
   88 =============================================================
   89 
   90 Hard time to find a method for manage multiple user session but, finally,
   91 the result is pretty good.  Here the details :
   92 
   93 1) Every lock control file is placed under /tmp.
   94 2) Basically two type of locking file exist, one used to lock the zone file in use
   95    by one (/tmp/zone.com.dns.zonelock) and the other (/tmp/webbind.lock) for use by the flock() function 
   96    during the writing on named.conf.
   97 3) If a user exceed the $zflto seconds value during an edit session on a zone, he will
   98    be redirect to the MainPage without commit any modification and clearing the locking file.
   99 4) Any user attempting to edit a zone already locked will be informed with a message containing
  100    the time remained in seconds to next free session.
  101 5) An editing session normally terminated by commit modifications or using bottom link to return at home page
  102    remove the lock on the zone.
  103 6) WARNING: If a user already editing a zone open a new browser instance on the MainPage the current zone
  104             locking file well be removed silently thus accepting other editing session .
  105 
  106 
  107 
  108 
  109 Demo On Line
  110 =============================================================
  111 
  112 You can try WeBBind at http://212.34.217.167/ .
  113 
  114 
  115 
  116 =============================================================
  117 WeBBind - Danilo Paliani <afn23397@afn.org>
  118 http://www.afn.org/~afn23397
  119 =============================================================