Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    XMLRPC Sync and BIND

    Scheduled Pinned Locked Moved HA/CARP/VIPs
    1 Posts 1 Posters 614 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C
      cmhddti
      last edited by cmhddti

      I have a need to sync a BIND configuration using XMLRPC Sync. I have it set up, and it appears to be syncing correctly, but the second BIND server is not working correctly. I'm using 2.4.5-RELEASE-p1 with the BIND 9.14_9 package.

      I have verified that general XMLRPC sync works correctly on the two machines. In the BIND -> Sync settings, I have the primary configured to "Sync to configured system backup server." When I make changes in the GUI on the primary, the GUI in the secondary BIND server updates correctly. Additionally, the named.conf files in /cf/named/etc/namedb look correct, so I think everything is working correctly with the actual config sync. Here's where it gets weird:

      On the secondary server, under the "Resulting Zone Config File" section, the window is blank. On the primary server, there is a proper looking BIND config file, but nothing on the secondary.

      Additionally, the file:

      /cf/named/etc/namedb/(master|slave)/Default/lab-01.zonename.local.DB
      

      on the primary looks like a normal DNS file. However, on the secondary, it is messed up. I can see something that looks like text from the zone, but it's not in any format that I recognize. Here's what the file looks like:

      [2.4.5-RELEASE][root@pfsense-02.lab-01.zonename.local]/root: cat /cf/named/etc/namedb/slave/Default/lab-01.zonename.local.DB   
      _?VOsXlab-01zonenamelocalL
      pfsense-01lab-01zonenamelocal
      zonemasterlab-01zonenamelocal??Q $?+Xlab-01zonenamelocal
      2
      CXlab-01zonenamelocal
      pfsense-01lab-01zonenamelocal!Q'_etcd-server-ssl_tcplab-01zonenamelocal
              Letcd-0lab-01zonenamelocal
              Letcd-1lab-01zonenamelocal
              Letcd-2lab-01zonenamelocal/Xapilab-01zonenamelocal
      2
      3Xapi-intlab-01zonenamelocal
      2
      2X*appslab-01zonenamelocal
      2
      3Xboot-01lab-01zonenamelocal
      2
      c3Xcsah-01lab-01zonenamelocal
      2
      
      2Xetcd-0lab-01zonenamelocal
      2
      
      2Xetcd-1lab-01zonenamelocal
      2
      
      2Xetcd-2lab-01zonenamelocal
      2
      5Xmaster-01lab-01zonenamelocal
      2
      
      5Xmaster-02lab-01zonenamelocal
      2
      
      5Xmaster-03lab-01zonenamelocal
      2
      6X
      pfsense-01lab-01zonenamelocal
      2
      6X
      pfsense-02lab-01zonenamelocal
      2
      7X
        pfsensec-01lab-01zonenamelocal
      2
      5Xworker-01lab-01zonenamelocal
      2
      5Xworker-02lab-01zonenamelocal
      2
      5Xworker-03lab-01zonenamelocal
      2
      5Xworker-04lab-01zonenamelocal
      2
      5Xworker-05lab-01zonenamelocal
      2
      

      This is the file from the primary server:

      [2.4.5-RELEASE][root@pfsense-01.lab-01.zonename.local]/root: cat /cf/named/etc/namedb/master/Default/lab-01.zonename.local.DB
      $TTL 600
      ;
      $ORIGIN lab-01.zonename.local.
      
      ;       Database file lab-01.zonename.local.DB for lab-01.zonename.local zone.
      ;       Do not edit this file!!!
      ;       Zone version 2597523698
      ;
      lab-01.zonename.local.         IN  SOA pfsense-01.lab-01.zonename.local.     zonemaster.lab-01.zonename.local. (
                      2597523698 ; serial
                      1d ; refresh
                      2h ; retry
                      4w ; expire
                      1h ; default_ttl
                      )
      
      ;
      ; Zone Records
      ;
      @        IN NS  pfsense-01.lab-01.zonename.local.
      @        IN A   10.50.10.2
      pfsensec-01      IN A   10.50.10.1
      pfsense-01       IN A   10.50.10.2
      pfsense-02       IN A   10.50.10.3
      api      IN A   10.50.10.4
      api-int          IN A   10.50.10.4
      etcd-0   IN A   10.50.10.11
      etcd-1   IN A   10.50.10.12
      etcd-2   IN A   10.50.10.13
      *.apps   IN A   10.50.10.4
      csah-01 IN A    10.50.10.10
      master-01       IN A    10.50.10.11
      master-02       IN A    10.50.10.12
      master-03       IN A    10.50.10.13
      worker-01       IN A    10.50.10.14
      worker-02       IN A    10.50.10.15
      worker-03       IN A    10.50.10.16
      worker-04       IN A    10.50.10.17
      worker-05       IN A    10.50.10.18
      boot-01 IN A    10.50.10.99
      
      
      ;
      ;custom zone records
      ;
      _etcd-server-ssl._tcp    86400     IN    SRV     0    10    2380    etcd-0
      _etcd-server-ssl._tcp    86400     IN    SRV     0    10    2380    etcd-1
      _etcd-server-ssl._tcp    86400     IN    SRV     0    10    2380    etcd-2
      

      When making changes to the primary zone, the file is not updated. However, if I delete the file on the secondary server and restart named, it regenerates a new file, but it's still in the messed up format.

      Any ideas as to what's going on? It looks like the sync is working, and if I look at the named.conf file, it looks like the configuration on both of the BIND servers is correct, but the actual zone file doesn't look like it's generating properly.

      Thanks in advance for any help anyone can offer!

      1 Reply Last reply Reply Quote 0
      • First post
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.