DNS and Proxy Manager setup

Back

LBL®DNS & Proxy Manager is a product destined for mission-critical environments therefore only staff who made the course and has passed the examination is authorized to certify the installation and maintenance of products in operation. All Certified People are equipped with temporary license issued by TCOGROUP.

LBL®DNS & Proxy Manager can be installed in two modes, together with LBL®ADC or alone (halo). In both cases it is necessary the specific license LBL®DNS & Proxy Manager to use it. Both installations are similar with the exception of the location of the license.

LBL®DNS & Proxy Manager has been released to cooperate with the DNS Server bind*** or with MS DNS*** that must be installed and functional.

This document is not intended to be a manual for the installation and configuration of DNS BIND*** or MS DNS***, confines itself to give the necessary knowledge to install and configure LBL®DNS & Proxy Manager with services of example. For a complete discussion of the topic DNS please refer to the product documentation or recommendations W3C IETF.

LBL®Management Console

Before proceeding with the installation of the server component is recommended to perform the installation of the component LBL®Management Console to be able to perform the configuration.

For the installation of the component LBL®Management Console refer to manual LBL_ManagementConsole_Installation.pdf available in storage media supplied with the product or through downloads from the reserved area.

Setting the Date and time of the operating system

LBL®DNS & Proxy Manager is not sensitive to time differences on the nodes during the operation. Nevertheless if during operation you may change the date and time of the system some considerations could be distorted as for example calculations of time-out, lease time or considerations on dates of repository (es.: date of the version of the repository of georeferenzazione).

As far as described it is therefore advisable to set the date and time of the system with values as close as possible to the current date and time. The use of the alignment using NTP is recommended.

Start Monitor & Visual Configuration

To run the start of service management from the command line is now sufficient to execute the batch go.sh or go.bat depending on the type of operating system:

Unix-Linux:

# ./Go.sh

MS Windows:

C:\> go.bat

This command runs in interactive mode the server management LBL®Monitor.

From the location where it was previously installed LBL®Management Console, start the program Configuration Visual, login with the address set in the configuration file to the parameter LBL_global_ADDRESS_MANAGEMENT. Immediately

Displays the status of jobs associated with the server  LBL®Monitor:

A05_LBLGoDNSManager – license entry

With the mouse to select the process A05_LBLGoDNSManager and from the contextual menu select “Install License”



You will be prompted to specify the license file to upload (NOTE: Must be called license.xml”):

A05_LBLGoDNSManager – popup menu ‘Properties’


To set the configuration parameters will now be sufficient to select A05_LBLGoDNSManager and with the right mouse button click Properties:


By selecting the panels with the names of the parameters file you can proceed with the configuration.

‘Access to basic process LBL Monitor is also possible through the Web Browser as in previous versions.

The plan addresses

To proceed with the installation of the LBL®DNS & Proxy Manager is necessary to carry out the plan of addresses in a manner appropriate to the needs of the project.

For this installation guide will take for example the need to set in RoundRobin on the domain name www.tcoproject.dev two addresses to which they satisfy the two nodes active-active LBL®ADC Enterprise has 

For each of the instances LBL LoadBalancer® Enterprise has  will be allocated its own address managed by the balancer. Among the different machines that will host LBL®ADC is appropriate for simplicity bear the same information.

The hosts file, /etc/hosts in the environment Unix-Linux and C:\WINDOWS\system32\drivers\etc\hosts in the MS Windows environment, should resemble the following example:

127.0.0.1 Localhost

192.168.43.3 Papaya # Local papaya

192.168.44.4 Papaiaprivate # Private papaya

192.168.45.101 Papaiabackend # Backend papaya

192.168.43.6 Mango # Public mango

192.168.44.5 Mangoproivate # Private mango

192.168.45.100 Mangobackend # Backend mango

192.168.43.136 Grid000 # Address grid node to

192.168.43.138 Grid001 # Address grid node B

The two addresses highlighted in red are related respectively to the node A and Node B and are completely controlled by the instances of balancing  LBL LoadBalancer® Enterprise has. These addresses will be handled by DNS RoundRobin in through a single domain. In the specific case will be taken as an example the domain name www.tcoproject.dev.

It is assumed in the examples below that the DNS to respond in the same machines where are installed instances of balancing addresses: 192.168.43.111 and 192.168.43.112.

BIND: determining correct operation of the DNS

Immediately after the plan addresses and the verification of the correct operation of the

DNS is necessary to determine the positions of the directory of the DNS and note carefully the directory on which the instance BIND acts to associate the names, addresses and services associated with them.

The correct operation of the DNS BIND is easily determinable through the rndc command. Below is the result of this command that in all operating systems respond in the same manner. Go the first time on Node A.

Solaris, Linux, MS Windows (OS independent):

Rndc status

Number of zones: 2

Debug Level: 0

Xfers running: 0

Xfers deferred: 0

Soa queries in progress: 0

Query logging is off

Recursive clients: 0/1000

Tcp clients: 0/100

The server is up and running

In red is highlighted the status of DNS that must be “up-and-running“.

The rndc command is usually located in the following directory:

Solaris:

Hich # rndc

/Usr/sbin/rndc

Linux:

Hich # rndc

/Usr/sbin/rndc

MS Windows (in dependence of the installation directory:

In our example:

C:\TCOProject\bin\BIND\bin\rndc.exe

BIND: Determination directory of the zones of the DNS

Immediately after the plan addresses and verifying the proper operation of the DNS is necessary to determine the positions of the directory of the DNS. BIND describes its characteristics in a profile file that normally takes the name of named.conf. Thus the first step is to check in your operating system the location of this file.

On Solaris normally you can find it in:

/Etc/named.conf

On Linux normally you can find it in:

/Etc/bind/named.conf

On MS Windows is dependent from the installation directory to the request from the autoinstaller. We will take in consideration for this hypothesis:

C:\TCOProject\bin\BIND\etc\named.conf

Once you have verified the location of the file named.conf inside you will find the directory in which you will cricate zones with the namespaces for each domain managed by the DNS. For this example we will consider a installation done on MS Windows. The only differences with respect to an installation on Solaris or Linux are indications of paths (path) where are stored the files of areas with their namespace.

Named.conf

Options {

Directory “C:\TCOProject\bin\BIND\etc\zones”;

Multiple-cnames yes;

};

Key “rndc-key” {

Algorithm hmac-md5;

 Secret “64WJDedFIw3vfJYFVYMTlQ==”;

};

Controls {

  Inet 127.0.0.1 port 953

  Allow { 127.0.0.1; } keys { “rndc-key”; };

};

Areas “.” {

Type hint;

The file ‘root.hints”;

};

Areas of “tcoproject.dev” {

Type master;

File “local/tcoproject.dev.db”;

};

Areas of “43.168.192.in-addr.arpa” {

Type master;

File “local/rev.43.168.192.in-addr.arpa”;

};

Evideanziati in green and red respectively the parameters and their value necessary for the determination of the directories and file zone.

In this example the parameter directory is referred to as the default directory for the zone files  “C:\TCOProject\bin\BIND\etc\zones”.

In the example you can find also two other parameters highlighted. These parameters indicate the location of files that contain the namespace.

Areas of “tcoproject.dev” {

Type master;

File “local/tcoproject.dev.db”;

};

Areas of “43.168.192.in-addr.arpa” {

Type master;

File “local/rev.43.168.192.in-addr.arpa”;

};

Being in the parameters file indicated a relative path both are to be understood as absolute path to the sum of the absolute path indicated in the parameter directory more as indicated on the parameter file

Then the absolute position of the zone file tcoproject.dev will be:

  C:\TCOProject\bin\BIND\etc\Zones\Local\tcoproject.dev.db

While the absolute position of the zone file 43.168.192.in-addr.arpa will be:

  C:\TCOProject\bin\BIND\etc\Zones\Local\rev.43.168.192.in-addr.arpa

These elements are sufficient for the determination of the paths and of the affected files from LBLDNSManager ®. These last two files are in fact subject to dynamic modification in dependence of the verifications of availability of services.

BIND: initial loading namespace in the zone file of DNS

Once you have determined the positions of the zone file the first step is to make operational the DNS with their own namespaces in order to verify functionality. For this purpose we will prepare the two files:

  C:\TCOProject\bin\BIND\etc\Zones\Local\tcoproject.dev.db

$TTL 3

@ IN SOA Ns.tcoproject.dev. hostmaster.tcoproject.dev. (

2010010701 ; Serial, todays date + todays serial #

8H ; Refresh

30m ; Retry

4W ; Expire

10) ; Minimum

NS Ns ; Inet Address of Name Server

Www IN TO 192.168.43.136

Www IN TO 192.168.43.138


  C:\TCOProject\bin\BIND\etc\Zones\Local\rev.43.168.192.in-addr.arpa

$TTL 3

@ IN SOA Ns.tcoproject.dev. hostmaster.tcoproject.dev. (

2010010701 ; Serial, todays date + todays serial #

8H ; Refresh

30m ; Retry

4W ; Expire

10) ; Minimum

NS Ns.tcoproject.dev.

PTR 136 www.tcoproject.dev.

PTR 138 www.tcoproject.dev.

Once completed the populating of zone file you must make them to transpose the instance DNS. For this operation it is sufficient to perform the rndc command followed by the parameter reload:

Solaris, Linux, MS Windows (OS independent):

C:\ rndc reload 

Server reload successful

MS DNS: determining correct operation of the DNS

To check the operation of the DNS Microsoft performed :

Control Panel->Administrative Tools->

—> DNS

MS DNS: Components Required

LBL®DNS & Proxy Manager in MS environment DNS uses the comado “dnscmd.exe” to change during the runtime associations names-domain<>addresses. This command, present by default on Windows 2008 Server must be installed as additional package “Support Tools” for versions of Windows 2003 Server.

For Windows 2003 Server installation directory of the package will determine the position of the control es.: 

C:\Support Tools\

It is recommended to use directory without spaces so as not to have problems during the set of the directory.

For Windows 2008:

C:\Windows\System32

MS DNS: Determination directory

MS DNS can be set during the runtime in two different ways: through the zone file or through explicit commands declared in the parameters of the management program at the command line dnscmd.exe.

Both modes are supported by LBL®DNSManager. In this example we will use the mode with explicit commands declared in the parameters of the management program at the command line dnscmd.exe because normally MS DNS is configured with the repository stored on Active Directory and this mode covers this characteristic.

The only directory to determine in this case are the location of the dnscmd.exe (seen in the previous paragraph) and locate a directory which allows us to contain the scripts that will be dynamically generated by  LBL®DNS & Proxy Manager for popular DNS MS. For the latter purpose we recommend to use a directory next to the directory (LBL_HOME) or even inside (LBL_home). In the example we will use a directory suitably created in:

(LBL_HOME\lib\scriptDNSManager\

In this directory will be deposited scripts for the manipulation of the associations names-domain<>addresses.

MS DNS: initial loading namespace

For the initial loading of the namespace it will seize in the visual interface that Microsoft has provided for this purpose.

Control Panel->Administrative Tools->DNS

In this window you can see the existence of zone tcoproject.dev, previously created, on which andreamo to act in a first time manually and then automatically with  LBLDNSManager ®.

We set the host names with their addresses. Name of the zone more host name will form the “domain”.



Create the first host with the name “www” taking care to create the inverse association through the check button [ ] Create associated pointer (PTR) records.

The association of the inverse resolution addresses<>domain-name deserves some considerations on the basis of the type of installation. These considerations are investigated through the course of certification. In this manual we will limit ourselves to give information concerning the basic settings as an aid to the installation that must be preceded as always by the requirements gathering and definition of the plan addresses and names.

The result we have achieved is an association to the same domain www.tcoproject.dev of two addresses 192.168.43.136 and 192.168.43.138. These addresses will be cyclically rotated from DNS automatically without performing any further action of setting.

Es.: 

If eseguissimo now a ping the effect would not be the same because of the TTL (Time To Live). To lower the TTL there are two modes, or at district level or at the level of single host name. In the examples below with LBL®DNS & Proxy Manager  we will use the TTL associated with the host name so as not to alter any other policies of TTL associated to other hosts on the zone which can have different needs.

C:\Users\Administrator>nslookup www.tcoproject.devServer: localhostAddress: 127.0.0.1Name: www.tcoproject.devAddresses 192.168.43.136:

  192.168.43.138C:\Users\Administrator>nslookup www.tcoproject.devServer: localhostAddress: 127.0.0.1Name: www.tcoproject.devAddresses 192.168.43.138:

  192.168.43.136C:\Users\Administrator>

Note: The reverse zones must have already been created in precedena before this operation

Verification of the correct setting RR of domain in DNS

To verify the correct operation of the DNS must be used in a client the nslookup command. Below the same command used on multiple operating systems. In red are highlighted addresses. The first parameter of nslookup is the domain name that you want to check the second is the address to which replies to the DNS in order to be sure to check the response from the correct DNS.

MS Windows:

C:\>nslookup www.tcoproject.dev 192.168.43.111

*** Cannot find server name for the address 192.168.43.111: Non-existent domain

Server: unknown

Address: 192.168.43.111

Name: www.tcoproject.dev

Addresses:  192.168.43.136, 192.168.43.138

Solaris:

Nslookup www.tcoproject.dev 192.168.43.111

Server: 192.168.43.111

Address: 192.168.43.111

Name: www.tcoproject.dev

Address: 192.168.43.136

Name: www.tcoproject.dev

Address: 192.168.43.138

Linux:

Nslookup www.tcoproject.dev 192.168.43.111

Server: 192.168.43.111

Address: 192.168.43.111

Name: www.tcoproject.dev

Address: 192.168.43.136

Name: www.tcoproject.dev

Address: 192.168.43.138

Verify correct setting reverse-namespace on DNS

To complete the verification of the correct setting must also check if the resolution reverse) has been transposed and set correctly. To this end run below the following commands:

MS Windows:

C:\>nslookup 192.168.43.136 192.168.43.111

*** Cannot find server name for the address 192.168.43.111: Non-existent domain

Server: unknown

Address: 192.168.43.111

Name:    www.tcoproject.dev

Address: 192.168.43.136

C:\>nslookup 192.168.43.138 192.168.43.111

*** Cannot find server name for the address 192.168.43.111: Non-existent domain

Server: unknown

Address: 192.168.43.111

Name:    www.tcoproject.dev

Address: 192.168.43.138

Solaris:

Nslookup 192.168.43.136 192.168.43.111

Server: 192.168.43.111

Address: 192.168.43.111

138.43.168.192.in-addr.arpa name = www.tcoproject.dev.

Nslookup 192.168.43.138 192.168.43.111

Server: 192.168.43.111

Address: 192.168.43.111

138.43.168.192.in-addr.arpa name = www.tcoproject.dev.

Linux:

Nslookup 192.168.43.136 192.168.43.111

Server: 192.168.43.111

Address: 192.168.43.111

138.43.168.192.in-addr.arpa name = www.tcoproject.dev.

Nslookup 192.168.43.138 192.168.43.111

Server: 192.168.43.111

Address: 192.168.43.111

138.43.168.192.in-addr.arpa name = www.tcoproject.dev.

Completion DNS configuration

To complete the configuration rerun the same operations from Chapter 11 Chapter 15 on the node B obtaining the following situation:

In the two nodes (A and B) are installed and configured the DNS so that both respond in the same manner by associating the name www.tcoproject.dev addresses 192.168.43.136 and 192.168.43.138. In this phase the DNS will not verify the existence of these addresses and the operation of the services associated with them, this functionality in fact will be implemented by LBLDNSManager ®.

BIND: Verification template in (LBL_HOME)/lib/templateDNSManager/

In the directory (LBL_HOME)/lib/templateDNSManager/ are contained files for the dynamic construction zones. Specifically are distributed two example files:

  • Tcoproject.dev.db.template
  • Rev.43.168.192.in-addr.arpa.template

These files contain

(LBL_HOME)/lib/templateDNSManager/tcoproject.dev.db.template

%Comment %

; LBL(tm) LoadBalancer

;

; This is a commercial software

;You shall not disclose such Confidential Information and shall use

; It only in accordance with the terms of the license agreement

;

Www.tcoproject.com ;

Www.lblloadbalancer.com ;

; Mailto:Info@tcoproject.com

;

; LBL(tm) LoadBalancer is built on TCOProject(tm) SoftwareLibrary

;LBL and TCOProject are trademarks of F.Pieretti. All rights reserved.

; Template file LBL(r)DNSManager

$TTL 3

@ IN SOA Ns.tcoproject.dev. hostmaster.tcoproject.dev. (

%Serial% ; Serial, todays date + todays serial #

8H ; Refresh

30m ; Retry

4W ; Expire

10) ; Minimum

NS Ns ; Inet Address of Name Server

%Namespaces%

(LBL_HOME)/lib/templateDNSManager/rev.43.168.192.in-addr.arpa.template

%Comment %

; LBL(tm) LoadBalancer

;

; This is a commercial software

;You shall not disclose such Confidential Information and shall use

; It only in accordance with the terms of the license agreement

;

Www.tcoproject.com ;

Www.lblloadbalancer.com ;

; Mailto:Info@tcoproject.com

;

; LBL(tm) LoadBalancer is built on TCOProject(tm) SoftwareLibrary

;LBL and TCOProject are trademarks of F.Pieretti. All rights reserved.

; Template file LBL(r)DNSManager

$TTL 3

@ IN SOA Ns.tcoproject.dev. hostmaster.tcoproject.dev. (

%Serial% ; Serial, todays date + todays serial #

8H ; Refresh

30m ; Retry

4W ; Expire

10) ; Minimum

NS Ns.tcoproject.dev.

%Namespaces%

In both files distributed can be noticed similarities with the zone file set on DNS except tags highlighted in red “%namespaces %” and “%serial %‘. These tags in fact will be populated dynamically according to the rules set in the file (LBL_HOME)/lib/confDNSManager/dnsmanager.xml.

ATTENZIONEI template files in this directory are continuously verified by LBL®DNS & Proxy Manager once started.At every change of these files will be automatically recharged the zones of the DNS. It is recommended that you keep a copy source in another directory and once completed the changes move in this production area.

BIND Configuration (LBL_HOME)/lib/confDNSManager/dnsmanager.xml

The configuration file dnsmanager.xml contains all information for dynamically populate zone files of the DNS by completing the template file. 

The file is formed by two paragraphs; the first <params> describes the general variables while the second ,<zone> that can be repeated more times, defines the zones of the dns. Inside the second paragraph <zone> are defined namespaces and related conditions of verification (HealthCheck) of “vitality services” <namespace>.

<serviceconf>

  <copyright>

  </copyright>

<dnsmanager>

  <params>

   </params>

   <zone>

  <namespace>

    <condition>

    </condition>

  </namespace>

  </zone>

</dnsmanager>

</serviceconf>

For a complete discussion of the individual parameters refer to document LBL®A.A.I. Reference Guide. 

In our case we are going to populate the sample file placed at the disposal of the distribution and below.

Configuration File dnsmanager.xml file included in the distribution:

<?xml version=”1.0″ encoding=”windows-1252″?>

<serviceconf>

<copyright>

    LBL(tm) LoadBalancer

  This is a commercial software

You shall not disclose such Confidential Information and shall use

  It only in accordance with the terms of the license agreement

  Www.tcoproject.com

  Www.lblloadbalancer.com

  Mailto:Info@tcoproject.com

  LBL(tm) LoadBalancer is built on TCOProject(tm) SoftwareLibrary

LBL and TCOProject are trademarks of F.Pieretti. All rights reserved.

  </copyright>

  <dnsmanager>

<params

   Frequency=”60000″

   TemplateDir=”lib/templateDNSManager”

   TemplateSerialWithDate= “true”

   ReloadCommand=”____reload_Cmd_with_absolute_address____es.:C:/work1/bin/named/bin/rndc reload”

   SysCommandRemoteURL=http://localhost:5992/SysCommand””>

</params>

<zone enable= “true”

   NamespaceFile=”__________________es.:C:\work1\bin/named/etc/zones/local/tcoproject.dev.db”

   NamespaceTemplateFile=”__________es.:tcoproject.dev.db.Template”

   NamespaceReverseFile=”___________es.:C:/work1/bin/named/etc/zones/local/rev.43.168.192.in-addr.arpa”

   NamespaceReverseTemplateFile=”___es.:rev.43.168.192.in-addr.arpa.Template”>

   <namespace enable= “true”

   Address=”_______________es.:192.168.43.136″ port=”80″ uriPath=”/HealthCheck” SSL= “false”

   Namespace=”_____________es.:www to 192.168.43.136″

   NamespaceReverse=”______es.:136 PTR www.tcoproject.dev.”/>

   <namespace enable= “true”

   Address=”_______________es.:192.168.43.138″ port=”80″ uriPath=”/HealthCheck” SSL= “false”

   Namespace=”_____________es.:www to 192.168.43.138″

   NamespaceReverse=”______es.:138 PTR www.tcoproject.dev.”/>

</zone>

<sysobserver>

</sysobserver>

  </dnsmanager>

</serviceconf>

In blue are highlighted paragraphs, in green parameter names in red the values of the parameters that normally remain unchanged while in black remained the values to be completed with information about our project.

In paragraph <params>

  • ReloadCommand must be completed with the value of the command to execute for recharge zones in the DNS. The command must be the same as that used for the test manual. It is advisable to indicate the absolute path of the command so as to be exempt from the problems as a result of changes to the environment after the installation which could jeopardize its operation. In our example it is “C:/TCOProject/bin/bind/bin/rndc reload

    In paragraph <zone>

  • NamespaceFile is the zone file of DNS. This value must be completed with the absolute path and name of the file previously set by hand in the directories of the area of the DNS. In our example: 

    C:\TCOProject\bin\BIND\etc\Zones\Local\tcoproject.dev.db

  • NamespaceTemplateFile is the template file that serves as a track for the dynamic generation of associations name<>addresses. May be completed with either an absolute path or a relative path to the parameter templateDir=”lib/templateDNSManager” in paragraph <params>. In our example: “tcoproject.dev.db.template“. The resulting value will then be:

     “(LBL_HOME)/lib/templateDNSManagertcoproject/.dev.db.template” 

    And that is the template file seen previously.

  • NamespaceReverseFile is the zone file for the reverse resolution from address to domain name. This value in our case must be completed with the absolute path and name of the file previously set by hand (perform before a security copy on other directory). In our example:


 “C:\TCOProject\bin\BIND\etc\Zones\Local\rev.43.168.192.in-addr.arpa“.

  • NamespaceReverseTemplateFile is the template file that serves as a track for the dynamic generation of associations address<>names. May be completed with either an absolute path or a relative path to the parameter templateDir=”lib/templateDNSManager”. In our example: 

Rev.43.168.192.in-addr.arpa“. The resulting value will then be:

“(LBL_HOME)/lib/templateDNSManager/Rev.43.168.192.in-addr.arpa” 

And that is the template file seen previously.

In the 1 nd paragraph <namespace>

  • Address is the address to be subjected to health checks to determine the activity and therefore the availability of this name space. The other parameters, port, uriPath and SSL are intuitive. If this address/port/uriPath will be active the namespace described in the parameters below will enter in the new zone files. In our example will be populated with the address that join the services of the node A.192.168.43.136 “
  • Namespace is the fragment of the namespace to insert in the template file in case the test of HealthCheck to succeed. In our example: 

    Www IN TO 192.168.43.136

  • NamespaceReverse is the fragment of the namespace reverse to insert in the template file in case the test of HealthCheck to succeed. In our example: 

136 PTR www.tcoproject.dev.

In the 2 nd paragraph <namespace>

  • Address is the address to be subjected to health checks to determine the activity and therefore the availability of this name space. The other parameters, port, uriPath and SSL are intuitive. If this address/port/uriPath will be active the namespace described in the parameters below will enter in the new zone files. In our example will be populated with the address that join the services of the node B.192.168.43.138 “
  • Namespace is the fragment of the namespace to insert in the template file in case the test of HealthCheck to succeed. In our example: 

    Www IN TO 192.168.43.138

  • NamespaceReverse is the fragment of the namespace reverse to insert in the template file in case the test of HealthCheck to succeed. In our example: 

    138 PTR www.tcoproject.dev.


The configuration file resulting should look like the one below:

Configuration File dnsmanager.xml compltetato starting from the file in the distribution:

<?xml version=”1.0″ encoding=”windows-1252″?>

<serviceconf>

<copyright>

    LBL(tm) LoadBalancer

  This is a commercial software

You shall not disclose such Confidential Information and shall use

  It only in accordance with the terms of the license agreement

  Www.tcoproject.com

  Www.lblloadbalancer.com

  Mailto:Info@tcoproject.com

  LBL(tm) LoadBalancer is built on TCOProject(tm) SoftwareLibrary

LBL and TCOProject are trademarks of F.Pieretti. All rights reserved.

  </copyright>

  <dnsmanager>

Absolute Path containing the area of DNS

<params

     Frequency=”60000″

   TemplateDir=”lib/templateDNSManager”

   TemplateSerialWithDate= “true”

   ReloadCommand=”C:/TCOProject/bin/bind/bin/rndc reload”

   SysCommandRemoteURL=http://localhost:5992/SysCommand””>

</params>

<zone enable= “true”

   NamespaceFile=”C:/TCOProject/bin/bind/etc/zones/local/tcoproject.dev.db”

   NamespaceTemplateFile=tcoproject”.dev.db.template”

   NamespaceReverseFile=”C:/TCOProject/bin/bind/etc/zones/local/rev.43.168.192.in-addr.arpa”

   NamespaceReverseTemplateFile=”Rev.43.168.192.in-addr.arpa.template”>

  <namespace enable= “true”

   Address=192.168.43.136″” port=”80″ uriPath=”/HealthCheck” SSL= “false”

   Namespace=”www IN TO 192.168.43.136″

   NamespaceReverse=”136 PTR www.tcoproject.dev.”/>

   <namespace enable= “true”

   Address=192.168.43.138″” port=”80″ uriPath=”/HealthCheck” SSL= “false”

   Namespace=”www IN TO 192.168.43.138″

     NamespaceReverse=”138 PTR www.tcoproject.dev.”/>

</zone>

<sysobserver>

</sysobserver>

  </dnsmanager>

</serviceconf>

MS DNS: Verification template in (LBL_HOME)/lib/templateDNSManager/

In the directory (LBL_HOME)/lib/templateDNSManager/ are contained files for the dynamic construction of zones or scripts of imnpostazione. Specifically are distributed two file mode example scripts template:

  • Www.dev.db.template
  • Empty.template

These files contain

(LBL_HOME)/lib/templateDNSManager/twww.dev.db.template

@ECHO OFF

REM LBL(tm) LoadBalancer

REM 

REM This is a commercial software

REM You shall not disclose such Confidential Information and shall use

REM it only in accordance with the terms of the license agreement

REM 

REM www.tcoproject.com

REM www.lblloadbalancer.com

REM mailto:Info@tcoproject.com

REM 

REM LBL(tm) LoadBalancer is built on TCOProject(tm) SoftwareLibrary

REM LBL and TCOProject are trademarks of F.Pieretti. All rights reserved.

REM Template file LBL(r)DNSManager

%Namespaces%

Exit 0

(LBL_HOME)/lib/templateDNSManager/empty.template

@ECHO OFF

REM LBL(tm) LoadBalancer

REM 

REM This is a commercial software

REM You shall not disclose such Confidential Information and shall use

REM it only in accordance with the terms of the license agreement

REM 

REM www.tcoproject.com

REM www.lblloadbalancer.com

REM mailto:Info@tcoproject.com

REM 

REM LBL(tm) LoadBalancer is built on TCOProject(tm) SoftwareLibrary

REM LBL and TCOProject are trademarks of F.Pieretti. All rights reserved.

Exit 0

For the Microsoft DNS settings for two template distributed are related to two batch script file that will be populated in relation to the needs of the association domain-name<>addresses. The file (LBL_HOME)/lib/templateDNSManager/twww.dev.db.template contains in its interior the TAG “%namespaces%” that will be populated with the command concerning the namespace to manage. The second file (LBL_HOME)/lib/templateDNSManager/empty.template is instead a batch file to support in this case (not operation). Also this second file is still necessary even if in this case produces no operation.

ATTENZIONEI template files in this directory are continuously verified by LBL®DNS & Proxy Manager once started.At every change of these files will be automatically recharged the zones of the DNS. It is recommended that you keep a copy source in another directory and once completed the changes move in this production area.

MS DNS: Configuration (LBL_HOME)/lib/confDNSManager/dnsmanager.xml

The configuration file dnsmanager.xml contains all information for dynamically populate the zones of the DNS by completing the template file and in this case producing the batch command file. 

The file is formed by two paragraphs; the first <params> describes the general variables while the second ,<zone> that can be repeated more times, defines the zones of the dns. Inside the second paragraph <zone> are defined namespaces and related conditions of verification (HealthCheck) of “vitality services” <namespace>.

<serviceconf>

  <copyright>

  </copyright>

<dnsmanager>

  <params>

   </params>

   <zone>

  <namespace>

    <condition>

    </condition>

  </namespace>

  </zone>

</dnsmanager>

</serviceconf>

For a complete discussion of the individual parameters refer to document LBL®A.A.I. Reference Guide. 

In our case we are going to populate the sample file placed at the disposal of the distribution and below.

Configuration File dnsmanager.xml file included in the distribution:

<?xml version=”1.0″ encoding=”windows-1252″?>

<serviceconf>

<copyright>

    LBL(tm) LoadBalancer

  This is a commercial software

You shall not disclose such Confidential Information and shall use

  It only in accordance with the terms of the license agreement

  Www.tcoproject.com

  Www.lblloadbalancer.com

  Mailto:Info@tcoproject.com

  LBL(tm) LoadBalancer is built on TCOProject(tm) SoftwareLibrary

LBL and TCOProject are trademarks of F.Pieretti. All rights reserved.

  </copyright>

  <dnsmanager>

<params

   Frequency=”60000″

   TemplateDir=”lib/templateDNSManager”

   TemplateSerialWithDate= “true”

   ReloadCommand=”____reload_Cmd_with_absolute_address____es.:C:/work1/bin/named/bin/rndc reload”

   SysCommandRemoteURL=http://localhost:5992/SysCommand””>

</params>

<zone enable= “true”

   NamespaceFile=”__________________es.:C:\work1\bin/named/etc/zones/local/tcoproject.dev.db”

   NamespaceTemplateFile=”__________es.:tcoproject.dev.db.Template”

   NamespaceReverseFile=”___________es.:C:/work1/bin/named/etc/zones/local/rev.43.168.192.in-addr.arpa”

   NamespaceReverseTemplateFile=”___es.:rev.43.168.192.in-addr.arpa.Template”>

   <namespace enable= “true”

   Address=”_______________es.:192.168.43.136″ port=”80″ uriPath=”/HealthCheck” SSL= “false”

   Namespace=”_____________es.:www to 192.168.43.136″

   NamespaceReverse=”______es.:136 PTR www.tcoproject.dev.”/>

   <namespace enable= “true”

   Address=”_______________es.:192.168.43.138″ port=”80″ uriPath=”/HealthCheck” SSL= “false”

   Namespace=”_____________es.:www to 192.168.43.138″

   NamespaceReverse=”______es.:138 PTR www.tcoproject.dev.”/>

</zone>

<sysobserver>

</sysobserver>

  </dnsmanager>

</serviceconf>

In blue are highlighted paragraphs, in green parameter names in red the values of the parameters that normally remain unchanged while in black remained the values to be completed with information about our project. In the case of Microsoft DNS information which we enter are related to the commands of insertion and deletion of host names through the dnscmd.exe.

In paragraph <params>

  • ReloadCommand must be completed with the value of the command to execute for recharge zones in the DNS. The command must be the same as that used for the test manual. It is advisable to indicate the absolute path of the command so as to be exempt from the problems as a result of changes to the environment after the installation which could jeopardize its operation. In the specific case, MS DNS, will be the resulting command from the processing in our example:

    C:\work1\bin\TCOProject\LBLLoadBalancer_MONITOR_007_000_000RC002\lib\scriptDNSManager\reloadMSDns.bat

    In paragraph <zone>

  • NamespaceFile is the batch file resulting from the detection of active services and mapping them to each other at the level of “domain” in DNS. This value corresponds in this case to reloadCommand seen previously. In our example: 

    C:\work1\bin\TCOProject\LBLLoadBalancer_MONITOR_007_000_000RC002\lib\scriptDNSManager\reloadMSDns.bat

  • NamespaceTemplateFile is the template file that serves as a track for the dynamic generation of associations name<>addresses. May be completed with either an absolute path or a relative path to the parameter templateDir=”lib/templateDNSManager” in paragraph <params>. In our example: 

    Www.dev.db.template

     The resulting value by adding the content of the parameter templateDir  will then be:

     “(LBL_HOME)/lib/templateDNSManager/www.dev.db.template” 

    And that is the template file seen previously.

  • NamespaceReverseFile is the batch file to populate the areas for the reverse resolution from address to domain name. This value in our case must be completed with the absolute path and the file name empty.bat. This file is not in this case taken into consideration. In our example:


 “C:\work1\bin\TCOProject\LBLLoadBalancer_MONITOR_007_000_000RC002\lib\scriptDNSManager\empty.bat“.

  • NamespaceReverseTemplateFile is the template file that serves as a track for the dynamic generation of associations address<>names. May be completed with either an absolute path or a relative path to the parameter templateDir=”lib/templateDNSManager”. In our example: 

Empty.template“. 

The resulting value by adding the content of the parameter templateDir  will then be:

“(LBL_HOME)/lib/templateDNSManager/empty.template” 

And that is the template file seen previously.

Note: In this case is not taken into consideration.

In the 1 nd paragraph <namespace>

  • Address is the address to be subjected to health checks to determine the activity and therefore the availability of this name space. The other parameters, port, uriPath and SSL are intuitive. If this address/port/uriPath will be active the namespace described in the parameters below will enter in the new zone files. In our example will be populated with the address that join the services of the node A.192.168.43.136 “
  • Namespace is the fragment of the batch file for the populating of host names to be inserted in the template file in case the test of HealthCheck to succeed. In our example: 

    Dnscmd /recordadd tcoproject.dev www CreatePTR /10 to 192.168.43.136

    Note: The parameter /CreatePTR is accepted only by release Windows 2008 Server. In previous versions should be removed.

    Note1: The value 10 after the parameter /CreatePTR is the TTL for this record. It is recommended not to fall under the 5 seconds.

  • NamespaceInactive is the fragment of the batch file for the populating of host names to be inserted in the template file in case the test of HealthCheck not successful. In our example: 

    Dnscmd /recorddelete tcoproject.dev www to 192.168.43.136 /F

  • NamespaceReverse in our example should be deleted from dnsmanager.xml because or you have to manually enter all the inverse resolutions or from Windows 2008, command of populating associations mini-domains<>addresses automatically generates and automatically removes the inverse resolutions.

    In the 2 nd paragraph <namespace>

  • Address is the address to be subjected to health checks to determine the activity and therefore the availability of this name space. The other parameters, port, uriPath and SSL are intuitive. If this address/port/uriPath will be active the namespace described in the parameters below will enter in the new zone files. In our example will be populated with the address that join the services of the node B.192.168.43.138 “
  • Namespace is the fragment of the batch file for the populating of host names to be inserted in the template file in case the test of HealthCheck to succeed. In our example: 

    Dnscmd /recordadd tcoproject.dev www CreatePTR /10 to 192.168.43.138

    Note: The parameter /CreatePTR is accepted only by release Windows 2008 Server. In previous versions should be removed.

  • NamespaceInactive is the fragment of the batch file for the populating of host names to be inserted in the template file in case the test of HealthCheck not successful. In our example: 

    Dnscmd /recorddelete tcoproject.dev www to 192.168.43.138 /F

  • NamespaceReverse in our example should be deleted from dnsmanager.xml because or you have to manually enter all the inverse resolutions or from Windows 2008, command of populating associations mini-domains<>addresses automatically generates and automatically removes the inverse resolutions.


The configuration file resulting should look like the one below:

Configuration File dnsmanager.xml compltetato starting from the file in the distribution:

<?xml version=”1.0″ encoding=”windows-1252″?>

<serviceconf>

<copyright>

     LBL(tm) LoadBalancer

  This is a commercial software

You shall not disclose such Confidential Information and shall use

  It only in accordance with the terms of the license agreement

  Www.tcoproject.com

  Www.lblloadbalancer.com

  Mailto:Info@tcoproject.com

  LBL(tm) LoadBalancer is built on TCOProject(tm) SoftwareLibrary

LBL and TCOProject are trademarks of F.Pieretti. All rights reserved.

  </copyright>

  <dnsmanager>

<params

   Frequency=”60000″

   TemplateDir=”lIb/templateDNSManager”

   TemplateSerialWithDate= “true”

   ReloadCommand=”C:\work1\bin\TCOProject\LBLLoadBalancer_MONITOR_007_000_000RC002\lib\scriptDNSManager\reloadMSDns.bat”

   SysCommandRemoteURL=https://localhost:5992/SysCommand””>

</params>

<zone enable= “true”

   NamespaceFile=”C:\work1\bin\TCOProject\LBLLoadBalancer_MONITOR_007_000_000RC002\lib\scriptDNSManager\reloadMSDns.bat”

   NamespaceTemplateFile=”www.dev.db.template”

   NamespaceReverseFile=”C:\work1\bin\TCOProject\LBLLoadBalancer_MONITOR_007_000_000RC002\lib\scriptDNSManager\empty.bat”

   NamespaceReverseTemplateFile=”empty.template”>

  <namespace enable= “true”

   Address=192.168.43.136″” port=”8080 uriPath “=”/” SSL= “false”

   Namespace=”dnscmd /recordadd tcoproject.dev www CreatePTR /10 to 192.168.43.136″

   NamespaceInactive=”dnscmd /recorddelete tcoproject.dev www to 192.168.43.136 /F”/>

  <namespace enable= “true”

   Address=192.168.43.138″” port=8181″” uriPath=”/” SSL= “false”

   Namespace=”dnscmd /recordadd tcoproject.dev www CreatePTR /10 to 192.168.43.138″

   NamespaceInactive=”dnscmd /recorddelete tcoproject.dev www to 192.168.43.138 /F”/>

  </zone>

<sysobserver>

  <service name=”syslog” id=”syslogdnsmanager”/>

</sysobserver>

</dnsmanager>

</serviceconf>

BIND: Start LBLDNSManager ®


The start of LBL®DNS & Proxy Manager will be similar to the start of the other processes through the automatic start of LBL®Monitor or through its WebConsole.

Start 

The startup of this service go to check the log files to see the successful regeneration of the areas of the DNS and the actual reload to work of the rndc command.

Fragment of the log file with the recording of the event of regeneration and dynamic loading of the DNS with the new situation:

|WARNING|1.6.0_16|UserService.dnsmanager|msw2000Srv000mg|1269171902765|20100321-12:45:02|Namespaces zone files Regeneration…||

|WARNING|1.6.0_16|UserService.dnsmanager|msw2000Srv000mg|1269171902890|20100321-12:45:02|New Namespace: C:/TCOProject/bin/bind/etc/zones/local/tcoproject.dev.db from template: C:\\TCOProject\\bin\\LBLLoadBalancer_MONITOR_007_000_000RC002/lib/templateDNSManager/tcoproject.dev.db.template

; LBL and TCOProject are trademarks of F.Pieretti

;

; THIS IS AN AUTOMATIC GENERATED FILE FROM LBL(r)DNSManager

; DO NOT MODIFY MANUALLY

; LBL(r)Rel.=7.0

; LastUpdate=20100321124502

; TemplateFile=C:\\TCOProject\\bin\\LBLLoadBalancer_MONITOR_007_000_000RC002/lib/templateDNSManager/tcoproject.dev.db.template

;

; LBL(tm) LoadBalancer

;

; This is a commercial software

;You shall not disclose such Confidential Information and shall use

; It only in accordance with the terms of the license agreement

;

Www.tcoproject.com ;

Www.lblloadbalancer.com ;

; Mailto:Info@tcoproject.com

;

; LBL(tm) LoadBalancer is built on TCOProject(tm) SoftwareLibrary

;LBL and TCOProject are trademarks of F.Pieretti. All rights reserved.

; Template file LBL(r)DNSManager

$TTL 3

@ IN SOA Ns.tcoproject.dev. hostmaster.tcoproject.dev. (

2010032101 ; Serial, todays date + todays serial #

8H ; Refresh

30m ; Retry

4W ; Expire

10) ; Minimum

NS Ns ; Inet Address of Name Server

Www IN TO 192.168.43.136

Www IN TO 192.168.43.138

New ReverseNamespace: C:/TCOProject/bin/bind/etc/zones/local/tcoproject.dev.db from template: C:\\TCOProject\\bin\\LBLLoadBalancer_MONITOR_007_000_000RC002/lib/templateDNSManager/rev.43.168.192.in-addr.arpa.template

; LBL and TCOProject are trademarks of F.Pieretti

;

; THIS IS AN AUTOMATIC GENERATED FILE FROM LBL(r)DNSManager

; DO NOT MODIFY MANUALLY

; LBL(r)Rel.=7.0

; LastUpdate=20100321124502

; TemplateFile=C:\\TCOProject\\bin\\LBLLoadBalancer_MONITOR_007_000_000RC002/lib/templateDNSManager/rev.43.168.192.in-addr.arpa.template

;

; LBL(tm) LoadBalancer

;

; This is a commercial software

;You shall not disclose such Confidential Information and shall use

; It only in accordance with the terms of the license agreement

;

Www.tcoproject.com ;

Www.lblloadbalancer.com ;

; Mailto:Info@tcoproject.com

;

; LBL(tm) LoadBalancer is built on TCOProject(tm) SoftwareLibrary

;LBL and TCOProject are trademarks of F.Pieretti. All rights reserved.

; Template file LBL(r)DNSManager

$TTL 3

@ IN SOA Ns.tcoproject.dev. hostmaster.tcoproject.dev. (

2010032101 ; Serial, todays date + todays serial #

8H ; Refresh

30m ; Retry

4W ; Expire

10) ; Minimum

NS Ns.tcoproject.dev.

PTR 136 www.tcoproject.dev.

PTR 138 www.tcoproject.dev.

||

|WARNING|1.6.0_16|UserService.dnsmanager|msw2000Srv000mg|1269171903000|20100321-12:45:03|Namespaces areas regenerated files!||

|WARNING|1.6.0_16|UserService.dnsmanager|msw2000Srv000mg|1269171903000|20100321-12:45:03|DNS namespaces zones realoading files…||

|WARNING|1.6.0_16|UserService.dnsmanager|msw2000Srv000mg|1269171904984|20100321-12:45:04|DNS namespaces zones realoaded files!||

In red are highlighted the signs of both the beginning of the regeneration step is the occurred reloading of the DNS with the new situation. The process from here onwards will be completely automatic. The log file will also indicate the new images generated in such a way as to be able to check immediately from the actual correctness of parameterisation.

BIND: Actual Verification modification of zone file

To verify the actual change of zone file at the disposal of the DNS is positioned on the directory containing DNS zones. In our example, check the contents of the files that should be changed to:

C:\TCOProject\bin\BIND\etc\Zones\Local\tcoproject.dev.db

; LBL and TCOProject are trademarks of F.Pieretti

;

; THIS IS AN AUTOMATIC GENERATED FILE FROM LBL(r)DNSManager

; DO NOT MODIFY MANUALLY

; LBL(r)Rel.=6.1

; LastUpdate=20100108134223

; TemplateFile=C:\TCOProject\bin\LBLLoadBalancer_dnsmanager_006_001_000RC012/lib/templateDNSManager/tcoproject.dev.db.template

;

; LBL(tm) LoadBalancer

;

; This is a commercial software

;You shall not disclose such Confidential Information and shall use

; It only in accordance with the terms of the license agreement

;

Www.tcoproject.com ;

Www.lblloadbalancer.com ;

; Mailto:Info@tcoproject.com

;

; LBL(tm) LoadBalancer is built on TCOProject(tm) SoftwareLibrary

;LBL and TCOProject are trademarks of F.Pieretti. All rights reserved.

; Template file LBL(r)DNSManager

$TTL 3

@ IN SOA Ns.tcoproject.dev. hostmaster.tcoproject.dev. (

2010010803 ; Serial, todays date + todays serial #

8H ; Refresh

30m ; Retry

4W ; Expire

10) ; Minimum

NS Ns ; Inet Address of Name Server

Www IN TO 192.168.43.136

Www IN TO 192.168.43.138

C:\TCOProject\bin\BIND\etc\Zones\Local\rev.43.168.192.in-addr.arpa

; LBL and TCOProject are trademarks of F.Pieretti

;

; THIS IS AN AUTOMATIC GENERATED FILE FROM LBL(r)DNSManager

; DO NOT MODIFY MANUALLY

; LBL(r)Rel.=6.1

; LastUpdate=20100108134223

; TemplateFile=C:\TCOProject\bin\LBLLoadBalancer_dnsmanager_006_001_000RC012/lib/templateDNSManager/rev.43.168.192.in-addr.arpa.template

;

; LBL(tm) LoadBalancer

;

; This is a commercial software

;You shall not disclose such Confidential Information and shall use

; It only in accordance with the terms of the license agreement

;

Www.tcoproject.com ;

Www.lblloadbalancer.com ;

; Mailto:Info@tcoproject.com

;

; LBL(tm) LoadBalancer is built on TCOProject(tm) SoftwareLibrary

;LBL and TCOProject are trademarks of F.Pieretti. All rights reserved.

; Template file LBL(r)DNSManager

$TTL 3

@ IN SOA Ns.tcoproject.dev. hostmaster.tcoproject.dev. (

2010010803 ; Serial, todays date + todays serial #

8H ; Refresh

30m ; Retry

4W ; Expire

10) ; Minimum

NS Ns.tcoproject.dev.

PTR 136 www.tcoproject.dev.

PTR 138 www.tcoproject.dev.

MS DNS: Start LBLDNSManager ®

The start of LBL®DNS & Proxy Manager will be similar to the start of the other processes through the automatic start of LBL®Monitor or through its WebConsole.

The startup of this service go to check the log files to see the successful regeneration of the areas of the DNS and the actual reload to work of the rndc command.

Start 

Fragment of the log file with the recording of the event of regeneration and dynamic loading of the DNS with the new situation:

|WARNING|1.6.0_11|UserService.dnsmanager|WIN-UF4APZRA30L|1269171351759|20100321-12:35:51|Namespaces zone files Regeneration…||

|WARNING|1.6.0_11|UserService.dnsmanager|WIN-UF4APZRA30L|1269171351779|20100321-12:35:51|New Namespace: C:\\work1\\bin\\TCOProject\\LBLLoadBalancer_MONITOR_007_000_000RC002\\lib\\scriptDNSManager\\reloadMSDns.bat from template: C:\\work1\\bin\\TCOProject\\LBLLoadBalancer_MONITOR_007_000_000RC002/lib/templateDNSManager/www.dev.db.template

@ECHO OFF

REM LBL(tm) LoadBalancer

REM 

REM This is a commercial software

REM You shall not disclose such Confidential Information and shall use

REM it only in accordance with the terms of the license agreement

REM 

REM www.tcoproject.com

REM www.lblloadbalancer.com

REM mailto:Info@tcoproject.com

REM 

REM LBL(tm) LoadBalancer is built on TCOProject(tm) SoftwareLibrary

REM LBL and TCOProject are trademarks of F.Pieretti. All rights reserved.

REM Template file LBL(r)DNSManager

Dnscmd /recordadd tcoproject.dev www CreatePTR /10 to 192.168.43.136

Dnscmd /recordadd tcoproject.dev www CreatePTR /10 to 192.168.43.138

Exit 0

New ReverseNamespace: C:\\work1\\bin\\TCOProject\\LBLLoadBalancer_MONITOR_007_000_000RC002\\lib\\scriptDNSManager\\reloadMSDns.bat from template: C:\\work1\\bin\\TCOProject\\LBLLoadBalancer_MONITOR_007_000_000RC002/lib/templateDNSManager/empty.template

@ECHO OFF

REM LBL(tm) LoadBalancer

REM 

REM This is a commercial software

REM You shall not disclose such Confidential Information and shall use

REM it only in accordance with the terms of the license agreement

REM 

REM www.tcoproject.com

REM www.lblloadbalancer.com

REM mailto:Info@tcoproject.com

REM 

REM LBL(tm) LoadBalancer is built on TCOProject(tm) SoftwareLibrary

REM LBL and TCOProject are trademarks of F.Pieretti. All rights reserved.

Exit 0

||

|WARNING|1.6.0_11|UserService.dnsmanager|WIN-UF4APZRA30L|1269171351779|20100321-12:35:51|Namespaces areas regenerated files!||

|WARNING|1.6.0_11|UserService.dnsmanager|WIN-UF4APZRA30L|1269171351789|20100321-12:35:51|DNS namespaces zones realoading files…||

|WARNING|1.6.0_11|UserService.dnsmanager|WIN-UF4APZRA30L|1269171354366|20100321-12:35:54|DNS namespaces zones realoaded files!||

In red are highlighted the signs of both the beginning of the regeneration step is the occurred reloading of the DNS with the new situation. The process from here onwards will be completely automatic. The log file will also indicate the new images generated in such a way as to be able to check immediately from the actual correctness of parameterisation.

BIND: Actual Verification modification of zone file

To verify the actual change of zone file at the disposal of the DNS is positioned on the directory containing DNS zones. In our example, check the contents of the files that should be changed to:

C:\TCOProject\bin\BIND\etc\Zones\Local\tcoproject.dev.db

; LBL and TCOProject are trademarks of F.Pieretti

;

; THIS IS AN AUTOMATIC GENERATED FILE FROM LBL(r)DNSManager

; DO NOT MODIFY MANUALLY

; LBL(r)Rel.=6.1

; LastUpdate=20100108134223

; TemplateFile=C:\TCOProject\bin\LBLLoadBalancer_dnsmanager_006_001_000RC012/lib/templateDNSManager/tcoproject.dev.db.template

;

; LBL(tm) LoadBalancer

;

; This is a commercial software

;You shall not disclose such Confidential Information and shall use

; It only in accordance with the terms of the license agreement

;

Www.tcoproject.com ;

Www.lblloadbalancer.com ;

; Mailto:Info@tcoproject.com

;

; LBL(tm) LoadBalancer is built on TCOProject(tm) SoftwareLibrary

;LBL and TCOProject are trademarks of F.Pieretti. All rights reserved.

; Template file LBL(r)DNSManager

$TTL 3

@ IN SOA Ns.tcoproject.dev. hostmaster.tcoproject.dev. (

2010010803 ; Serial, todays date + todays serial #

8H ; Refresh

30m ; Retry

4W ; Expire

10) ; Minimum

NS Ns ; Inet Address of Name Server

Www IN TO 192.168.43.136

Www IN TO 192.168.43.138

C:\TCOProject\bin\BIND\etc\Zones\Local\rev.43.168.192.in-addr.arpa

; LBL and TCOProject are trademarks of F.Pieretti

;

; THIS IS AN AUTOMATIC GENERATED FILE FROM LBL(r)DNSManager

; DO NOT MODIFY MANUALLY

; LBL(r)Rel.=6.1

; LastUpdate=20100108134223

; TemplateFile=C:\TCOProject\bin\LBLLoadBalancer_dnsmanager_006_001_000RC012/lib/templateDNSManager/rev.43.168.192.in-addr.arpa.template

;

; LBL(tm) LoadBalancer

;

; This is a commercial software

;You shall not disclose such Confidential Information and shall use

; It only in accordance with the terms of the license agreement

;

Www.tcoproject.com ;

Www.lblloadbalancer.com ;

; Mailto:Info@tcoproject.com

;

; LBL(tm) LoadBalancer is built on TCOProject(tm) SoftwareLibrary

;LBL and TCOProject are trademarks of F.Pieretti. All rights reserved.

; Template file LBL(r)DNSManager

$TTL 3

@ IN SOA Ns.tcoproject.dev. hostmaster.tcoproject.dev. (

2010010803 ; Serial, todays date + todays serial #

8H ; Refresh

30m ; Retry

4W ; Expire

10) ; Minimum

NS Ns.tcoproject.dev.

PTR 136 www.tcoproject.dev.

PTR 138 www.tcoproject.dev.

Configuration (LBL_HOME)/lib/confMonitor/A05_LBLGoDNSManager.xml

This file is already configured for full The only caveat is that of modifying the parameter of start by manual in automatic so that at the start of LBL®monitor these is automatically started. If the job was started these will be stopped and then restarted.

The fragment of the file (LBL_HOME)/lib/confMonitor/A05_LBLGoDNSManager.xml

  </copyright>

<A05_LBLGoDNSManager>

<!– 

  Start: automatic (default), manual

  –>

<process enable=”true”

 Description=”lbl(r)LoadBalancer DNSManager”

 Start=”automatic

 NumberTryStartOnFailure=”-1″

 WaitBeforeKill=”115000″

 SysCommand=”tr…

BIND: manual modification of the Serial Number

The serial number is an important element because it allows any secondary DNS to check the alignment of the changes. LBL®DNS & Proxy Manager automatically manages its increase. The increment can be represented by a progressive concerning the date expressed in YYYYMMDDss (where ss is a number comprised between 01 and 99) or with a progressive between +1 and +2^32. By recommendation (RFC) both these behaviors are valid even if the most widespread is surely YYYYMMDDss. IN LBL®DNS & Proxy Manager this behavior is influenced by the parameter templateSerialWithDate in dnsmanager file.xml in paragraph <params>. By default, this parameter is set to templateSerialWithDate= “true”.

In some circumstances it may be necessary to set a given Serial Number. To do this it is sufficient to perform the following operations.

 

For each template the progressive of the Serial Number is kept on a file in the same directory as the template and takes its name from the template to which is added a extension “_Serial“. In our example the resulting files will then be: 

  • (LBL_HOME)/lib/templateDNSManager/tcoproject.dev.db.template_Serial
  • (LBL_HOME)/lib/templateDNSManager/rev.43.168.192.in-addr.arpa.template_Serial

These files contain the latest progressive and then in our case both will contain the value:  2010010803 where 03 is the progressive.

To change the progressive is sufficient to change this value with an editor . 

From  2010010803

At  2010010809

LBL®DNS & Proxy Manager by periodically checking the status of the file is unaware of the change and will reload the new zone files in the DNS with the New Serial Number  2010010810.

Different scenarios: Business Continuity, Disaster Recovery

LBL®DNS & Proxy Manager can be effectively used for activities that comprise processes of Business Continuity and Disaster Recovery. In fact it is possible to condition the attribution of a namespace in dependence of the existence of other services. In other words if the main service is active will not be populated the zone file with the address of the secondary. This feature allows you to quickly build an infrastructure of BC OR DR leaving LBL®DNS & Proxy Manager the task of assigning the operability of a site and then concentrate the staff engaged in the switch on the activities related to the activation application. Once the operation will be restored in one of two sites  LBL®DNS & Proxy Manager will make the allocation name<>address and<>name automatically.

To set the condition is very simple and it is sufficient to indicate on the paragraph <namespace> Conditions of up an address. Below a fragment of the file dnsmanager.xml that affects the up the address 192.168.43.136 to presence of activities present addresses 192.168.43.138 and 192.168.43.144. If even only one of the addresses parameterised on condition are active address 192.168.43.136 will not be populated in the area of DNS.

<zone enable= “true”

   NamespaceFile=”C:/work1/bin/named/etc/zones/local/tcoproject.dev.db”

   NamespaceTemplateFile=tcoproject”.dev.db.Template”

   NamespaceReverseFile=”C:/work1/bin/named/etc/zones/local/rev.43.168.192.in-addr.arpa”

   NamespaceReverseTemplateFile=”Rev.43.168.192.in-addr.arpa.template”>

  <namespace enable= “true”

   Address=192.168.43.136″” port=”80″ uriPath=”/HealthCheck SSL”= “false”

   Namespace=”www IN TO 192.168.43.136″

   NamespaceReverse=”136 PTR www.tcoproject.dev.”>

   <condition enable= “true” address=192.168.43.138″” port=”80″ uriPath=”/HealthCheck” SSL= “false”/>

  <condition enable= “true” address=192.168.43.144″” port=”80″ uriPath=”/HealthCheck” SSL= “false”/>

  </namespace>

  <namespace enable= “true”

   Address=192.168.43.138″” port=”80″ uriPath=”/HealthCheck” SSL= “false”

   Namespace=”www IN TO 192.168.43.138″

   NamespaceReverse=”138 PTR www.tcoproject.dev.”>

   <condition enable= “true” address=192.168.43.136″” port=”80″ uriPath=”/HealthCheck” SSL= “false”/>

  <condition enable= “true” address=192.168.43.144″” port=”80″ uriPath=”/HealthCheck” SSL= “false”/>

   </namespace>

 

BIND: Negative Cache prevention

LBL®DNS & Proxy Manager to avoid negative-cache in the client has been studied for never set an allocation empty name<>address or address<>name. In case none of the sites/nodes are active LBL®DNS & Proxy Manager Assigns automatically the first namespace on paragraph <zone> which belongs. 

In this case for example if all services were not in activity however the zone file would be populated with the first namespace: www in to 192.168.43.136  and the first namespace-reverse: 136 PTR www.tcoproject.dev.

<zone enable= “true”

   NamespaceFile=”C:/work1/bin/named/etc/zones/local/tcoproject.dev.db”

   NamespaceTemplateFile=tcoproject”.dev.db.Template”

   NamespaceReverseFile=”C:/work1/bin/named/etc/zones/local/rev.43.168.192.in-addr.arpa”

   NamespaceReverseTemplateFile=”Rev.43.168.192.in-addr.arpa.template”>

  <namespace enable= “true”

   Address=192.168.43.136″” port=”80″ uriPath=”/HealthCheck” SSL= “false”

   Namespace=”www IN TO 192.168.43.136″

   NamespaceReverse=”136 PTR www.tcoproject.dev.”>

   <condition enable= “true” address=192.168.43.138″” port=”80″ uriPath=”/HealthCheck” SSL= “false”/>

  <condition enable= “true” address=192.168.43.144″” port=”80″ uriPath=”/HealthCheck” SSL= “false”/>

  </namespace>

  <namespace enable= “true”

   Address=192.168.43.138″” port=”80″ uriPath=”/HealthCheck” SSL= “false”

   Namespace=”www IN TO 192.168.43.138″

   NamespaceReverse=”138 PTR www.tcoproject.dev.”>

   <condition enable= “true” address=192.168.43.136″” port=”80″ uriPath=”/HealthCheck” SSL= “false”/>

  <condition enable= “true” address=192.168.43.144″” port=”80″ uriPath=”/HealthCheck” SSL= “false”/>

   </namespace>

It is also possible to indicate a further address in case both sites are not available. In this case can be arranged a page of courtesy to users. This address is not subjected to further HealthCheck and then it will be otherwise proposed as valid even if non-existent avoiding negative-cache. To set these values is sufficient in paragraph <zone> enhance the parameters namespaceNegativeCachePrevention namespaceReverseNegativeCachePrevention and as in the fragment of dnsmanager.xml:

<zone enable= “true”

   NamespaceFile=”C:/work1/bin/named/etc/zones/local/tcoproject.dev.db”

   NamespaceTemplateFile=tcoproject”.dev.db.Template”

   NamespaceReverseFile=”C:/work1/bin/named/etc/zones/local/rev.43.168.192.in-addr.arpa”

   NamespaceReverseTemplateFile=”Rev.43.168.192.in-addr.arpa.template”    

   NamespaceNegativeCachePrevention=”www IN TO 192.168.43.144″

   NamespaceReverseNegativeCachePrevention=”144 PTR www.tcoproject.dev.”>

  <namespace enable= “true”

   Address=192.168.43.136″” port=”80″ uriPath=”/HealthCheck” SSL= “false”

   Namespace=”www IN TO 192.168.43.136″

   NamespaceReverse=”136 PTR www.tcoproject.dev.”>

   <condition enable= “true” address=192.168.43.138″” port=”80″ uriPath=”/HealthCheck” SSL= “false”/>

  <condition enable= “true” address=192.168.43.144″” port=”80″ uriPath=”/HealthCheck” SSL= “false”/>

  </namespace>

  <namespace enable= “true”

   Address=192.168.43.138″” port=”80″ uriPath=”/HealthCheck” SSL= “false”

   Namespace=”www IN TO 192.168.43.138″

   NamespaceReverse=”138 PTR www.tcoproject.dev.”>

   <condition enable= “true” address=192.168.43.136″” port=”80″ uriPath=”/HealthCheck” SSL= “false”/>

  <condition enable= “true” address=192.168.43.144″” port=”80″ uriPath=”/HealthCheck” SSL= “false”/>

   </namespace>

In this case the lack of activity on the sites addressed with 192.168.43.136 192.168.43.138 and DNS to request the name www.tcoproject.dev will respond with the address 192.168.43.144. Even at a subsequent reboot of one of the two sites until the HealtCheck on address 192.168.43.144 will be active will not be loaded zones on DNS with addresses 192.168.43.136 or 138.

It is good to remember that clients are strongly influenced by their cache and that once a site is recommended to remove completely the availability of the address entered in  namespaceNegativeCachePrevention namespaceReverseNegativeCachePrevention and. This result can be obtained easily through the functionality of LBL®ADC or through the service LBL®IP Network Card Redundancy present in every distribution LBL®. In other configurations where there are no LBL®ADC or service LBL®IP Network Card Redundancy is recommended integration with existing procedures.

MS DNS cache negative prevention

LBL®DNS & Proxy Manager to avoid negative-cache in the client has been studied for never set an allocation empty name<>address or address<>name. In case none of the sites/nodes are active LBL®DNS & Proxy Manager Assigns automatically the first namespace on paragraph <zone> which belongs. 

In this case for example if all services were not in activity however the zone file would be populated with the first namespace: dnscmd /recordadd tcoproject.dev www CreatePTR /10 to 192.168.43.136.

   TemplateSerialWithDate= “true”

   ReloadCommand=”C:\work1\bin\TCOProject\LBLLoadBalancer_MONITOR_007_000_000RC002\lib\scriptDNSManager\reloadMSDns.bat”

   SysCommandRemoteURL=https://localhost:5992/SysCommand””>

</params>

<zone enable= “true”

   NamespaceFile=”C:\work1\bin\TCOProject\LBLLoadBalancer_MONITOR_007_000_000RC002\lib\scriptDNSManager\reloadMSDns.bat”

   NamespaceTemplateFile=”www.dev.db.template”

   NamespaceReverseFile=”C:\work1\bin\TCOProject\LBLLoadBalancer_MONITOR_007_000_000RC002\lib\scriptDNSManager\empty.bat”

   NamespaceReverseTemplateFile=”empty.template”>

  <namespace enable= “true”

   Address=192.168.43.136″” port=”8080 uriPath “=”/” SSL= “false”

   Namespace=”dnscmd /recordadd tcoproject.dev www CreatePTR /10 to 192.168.43.136″

   NamespaceInactive=”dnscmd /recorddelete tcoproject.dev www to 192.168.43.136 /F”/>

  <namespace enable= “true”

   Address=192.168.43.138″” port=8181″” uriPath=”/” SSL= “false”

   Namespace=”dnscmd /recordadd tcoproject.dev www CreatePTR /10 to 192.168.43.138″

   NamespaceInactive=”dnscmd /recorddelete tcoproject.dev www to 192.168.43.138 /F”/>

   </zone>

<sysobserver>

It is also possible to indicate a further address in case both sites are not available. In this case can be arranged a page of courtesy to users. This address is not subjected to further HealthCheck and then it will be otherwise proposed as valid even if non-existent avoiding negative-cache. To set these values is sufficient in paragraph <zone> enhance the parameters namespaceNegativeCachePrevention namespaceReverseNegativeCachePrevention and as in the fragment of dnsmanager.xml:

   

   TemplateSerialWithDate= “true”

   ReloadCommand=”C:\work1\bin\TCOProject\LBLLoadBalancer_MONITOR_007_000_000RC002\lib\scriptDNSManager\reloadMSDns.bat”

   SysCommandRemoteURL=https://localhost:5992/SysCommand””>

</params>

<zone enable= “true”

   NamespaceFile=”C:\work1\bin\TCOProject\LBLLoadBalancer_MONITOR_007_000_000RC002\lib\scriptDNSManager\reloadMSDns.bat”

   NamespaceTemplateFile=”www.dev.db.template”

   NamespaceReverseFile=”C:\work1\bin\TCOProject\LBLLoadBalancer_MONITOR_007_000_000RC002\lib\scriptDNSManager\empty.bat”

   NamespaceReverseTemplateFile=”empty.template”

   NamespaceNegativeCachePrevention=”dnscmd /recordadd tcoproject.dev www CreatePTR /10 to 192.168.43.144″>

  <namespace enable= “true”

   Address=192.168.43.136″” port=”8080 uriPath “=”/” SSL= “false”

   Namespace=”dnscmd /recordadd tcoproject.dev www CreatePTR /10 to 192.168.43.136″

   NamespaceInactive=”dnscmd /recorddelete tcoproject.dev www to 192.168.43.136 /F”/>

  <namespace enable= “true”

   Address=192.168.43.138″” port=8181″” uriPath=”/” SSL= “false”

   Namespace=”dnscmd /recordadd tcoproject.dev www CreatePTR /10 to 192.168.43.138″

   NamespaceInactive=”dnscmd /recorddelete tcoproject.dev www to 192.168.43.138 /F”/>

   </zone>

<sysobserver>

In this case the lack of activity on the sites addressed with 192.168.43.136 192.168.43.138 and DNS to request the name www.tcoproject.dev will respond with the address 192.168.43.144. Even at a subsequent reboot of one of the two sites until the HealtCheck on address 192.168.43.144 will be active will not be loaded zones on DNS with addresses 192.168.43.136 or 138.

It is good to remember that clients are strongly influenced by their cache and that once a site is recommended to remove completely the availability of the address entered in  namespaceNegativeCachePrevention namespaceReverseNegativeCachePrevention and. This result can be obtained easily through the functionality of LBL®ADC or through the service LBL®IP Network Card Redundancy present in every distribution LBL®. In other configurations where there are no LBL®ADC or service LBL®IP Network Card Redundancy is recommended integration with existing procedures.

Check release and updates

At the start of the processes LBL®A.A.I. verifies the release in site www.tcoproject.com. The data sent to the site does not contain sensitive data but show only:

Rel=99.99.99; license:127123163*****; IP=99999999; RL=9

Rel: it is the release and the version of the product

License: is the distinctive part of the license in use

IP: is a digest of control

R1: is the Run Level LBL®

The control of release can be deactivated through the parameter “-ncu” at startup processes as shown below in the profile of the launch. In the case it is deactivated or this message cannot reach www.tcoproject.com TCOGROUP srl will not be able to provide indications proactive patch or urgent notifications related to safety.

Es.: 

<process enable=”true”

Description=”lbl(r)LoadBalancer Standard Edition”

Start=”Automatic”

NumberTryStartOnFailure=”-1″

WaitBeforeKill=”80000″

WaitBeforeKillOnFailure=”10000″

ManagementPort=”5900″

ConfDir=”lib/conf”

The runLevel=”2″>

  <start osName=”Windows”>

  <env>CLASSPATH=lib;lib\LBLLoadBalancer.jar</env> 

  <workingDir></workingDir>

<Exec>java -Xrs -server -XX:-UseGCOverheadLimit – Xss256k

  – XX:+AggressiveHeap

  %LBL_exec_defines%

  – DLBL_INTERACTIVE_CMD=true 

  Loadbalancer.starter.LBLServerStarterApp – ncu </exec>

<logDirFiles>lib\logs</logDirFiles>

</Start>

To disable verification of release even the start of LBL Monitor set parameter – ncu (NoCheckUpdate), even at the initial start bacth (or service). 

Go.bat:

PATH=”%LBL_JAVA_HOME%\bin”;%PATH%

Cd /d “%LBL_HOME%”

Set WHAT=loadbalancer.starter.LBLServerStarterApp

Set the classpath=lib;lib\LBLLoadBalancer.jar;lib\extLib\mail.jar

Java -server -XX:-UseGCOverheadLimit -Xms256m -Xmx256M – DLBL_RUNLEVEL=0 – DLBL_MONITOR=true – DLBL_INTERACTIVE_CMD=true %WHAT % -nc