Difference between revisions of "How to use two HDAs on the same network"

From Amahi Wiki
Jump to: navigation, search
Line 8: Line 8:
  
 
  cat > named.patch << 'EOF'
 
  cat > named.patch << 'EOF'
  *** /usr/bin/hdactl 2010-05-17 12:04:57.994266656 -0400
+
  *** /usr/bin/hdactl 2010-06-16 21:55:38.000000000 -0400
  --- /usr/bin/hdactl.new 2010-05-17 12:06:28.151265690 -0400
+
  --- /usr/bin/hdactl.new 2010-08-03 07:49:22.083756431 -0400
 
  ***************
 
  ***************
 
  *** 255,260 ****
 
  *** 255,260 ****
Line 17: Line 17:
 
   printf $hda "};\n\n";
 
   printf $hda "};\n\n";
 
  +  
 
  +  
  + printf $hda "zone \"home.com\" IN {\n";
+
  +         printf $hda "zone \"home.com\" IN {\n";
  + printf $hda "\ttype slave;\n";
+
  +         printf $hda "\ttype slave;\n";
  + printf $hda "\tmasters { 192.168.1.10; };\n";
+
  +         printf $hda "\tmasters { 192.168.1.10; };\n";
  + printf $hda "};\n\n";
+
  +         printf $hda "};\n\n";
 
   }
 
   }
 
    
 
    

Revision as of 11:51, 3 August 2010

Make sure both HDA use different domain names.

You'll need to re-apply this fix on every update of hdactl.

You'll need to run the commands below on both your HDAs.
On your main HDA: replace home.com with your second HDA domain name, and 192.168.1.10 with your second HDA real IP address.
On your second HDA: replace home.com with your main HDA domain name, and 192.168.1.10 with you HDA real IP address.

cat > named.patch << 'EOF'
*** /usr/bin/hdactl	2010-06-16 21:55:38.000000000 -0400
--- /usr/bin/hdactl.new	2010-08-03 07:49:22.083756431 -0400
***************
*** 255,260 ****
--- 255,265 ----
          printf $hda "\tallow-update { key ddnskey; };\n";
          printf $hda "\tcheck-names ignore;\n";
  	printf $hda "};\n\n";
+ 
+         printf $hda "zone \"home.com\" IN {\n";
+         printf $hda "\ttype slave;\n";
+         printf $hda "\tmasters { 192.168.1.10; };\n";
+         printf $hda "};\n\n";
  }
  
  sub print_void_info {
EOF
patch -p0 < named.patch
service hdactl restart