Installing the PTF

Apply the PTF to 3DNS System version 1.0.4, or 3DNS System 1.0.4PTF-01 using the following process:

1. Click here and follow the instructions for using the F5 Networks FTP site.

2. Download the appropriate file to the /var/tmp/ directory on the target 3DNS System:
   • For US 3DNS Systems, download the 3dns104PTF-02dom.tar.gz file.
   • For international 3DNS Systems, download the 3dns104PTF-02int.tar.gz file.

3. Enter the following commands on the command line:

   ndc stop
   kill `cat /var/run/big3d.pid`
   kill `cat /var/run/syslog.pid`
   ps -aux thttpd
   kill pid#
   cd /
   gtar xvzpUf /var/tmp/<file name>

4. Reinstall the big3d utility by selecting Install and Start big3d from the 3DNS Maintenance menu.

5. Restart the syslogd utility.

6. Restart the thttpd web server by selecting Start 3DNS Administration from the 3DNS Maintenance menu.

7. Enter the following on the command line to complete the PTF installation:

   ndc restart

Note: It is very important that you start big3d on all BIG/ip controllers, and then restart named on all 3DNS Systems.

---

What's fixed in this PTF

The current PTF-02 includes the following fix, and also includes fixes originally released in version 1.0.4PTF-01 as described below.

Fixes for version 1.0.4PTF-02

This PTF resolves the following issue:

Fix 2401:  The Round Robin, Global Availability, and Random pool load balancing modes ignore the first pool in the list
These three pool load balancing modes now use the first pool in the list as expected.  Note that this fix does not affect the big3d utility, nor does it require you to make any changes to your current configuration.

In the following sample wideip.conf file, the 3DNS System would first use the Los Angeles pool.  If all virtual servers in the Los Angeles pool went down, the 3DNS System would then use the Tokyo pool.  If all virtual servers in the Tokyo pool went down, the 3DNS System would then use the wideip key address 192.168.102.70.   The New York pool would never be used.  Once you apply the current PTF, however, the 3DNS System would use the New York pool first (as it should), and then move on the Los Angeles pool if all virtual servers in the New York pool went down.

wideip {
   address 192.168.102.70
   port 80
   name "www.domain.com"
   alias "home.domain.com"
   ttl 120
   pool_lbmode ga

   pool {
      name "New York"
      type vsb
      ratio 2
      preferred leastconn
      alternate null
      fallback null
      address 192.168.101.50 ratio 2
      address 192.168.101.60 ratio 1
      address 192.168.101.70 ratio 1
      }

   pool {
      name "Los Angeles"
      type vsb
      ratio 1
      preferred leastconn
      alternate null
      fallback null
      address 192.168.102.50 ratio 3
      address 192.168.102.60 ratio 2
      address 192.168.102.70 ratio 1
      }

   pool {
      name "Tokyo"
      type vsb
      ratio 1
      preferred leastconn
      alternate null
      fallback return_to_dns
      address 192.168.103.50 ratio 3
      address 192.168.103.60 ratio 2
      address 192.168.103.70 ratio 1
      }

   }

Fixes originally released in version 1.0.4PTF-01

• Fix 1863:  MX queries are corrupted when domain names and zone names are identical
  If you used zone names and domain names that were identical, the 3DNS System would return corrupted records. This issue is resolved, and the following example /etc/wideip.conf configuration now works properly. 
    wideip {
    address 192.168.111.111
     name "www.domain.com"
     alias "domain.com"
   pool {
       type "VSb"
       lbmode rr
       address 192.168.111.111
     }
     }
  

  The corresponding excerpt from /var/namedb/db.domain.com would read:

  domain.com. IN MX 10 mx.domain.com
  www.domain.com. IN A 192.168.111.111

• Fix 2247:  The big3d parent process occasionally stops working
  The big3d's parent process occasionally stops working on the BIG/ip Controller when issuing virtual server status commands on behalf of the 3DNS Controller.  Because the 3DNS controller communicates with the BIG/ip Controller using the parent process of big3d, iQuery communication would be stopped. This problem was caused by a race condition betweenbig3d and bigpipe for a system resource.  In the updated software, the race condition is now properly detected, error messages are logged, and queries are resubmitted.

---

Configuring and using the updated software

The PTF does not introduce new software configuration issues.

---

Known issues

There are no known issues at this time.

---

---