Search Engine: Elastic

Article ID: 126589, created on Aug 18, 2015, last review on Jul 14, 2018

  • Applies to:
  • Odin Business Automation Standard 4.5


DNS zones are not synchronized between OBAS and an SSH-manageable name server. The server has Installed status, synchronization between OBAS and the name server can be performed successfully.

Nevertheless, all attempts to get a list of DNS records for some domain from the DNS server in question return empty response, like:

#dig domain.tld any
; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.30.rc1.el6_6.3 <<>> domain.tld any
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60693
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;domain.tld.                         IN      ANY


OBAS server IP address is unreachable from the name server.

For each domain hosted on a name server registered in OBAS there is a record in the named.zones file on that server, for instance

#less /var/named/named.zones
zone "domain.tld" IN {
        type slave;
        masters {; };
        file "";

masters field contains a list of master name servers for a corresponding domain. For domains registered via OBAS there will be by default an IP address of the OBAS server taken from the SERVER_IP value stored in /etc/hspc/hspc.conf on the OBAS server.

If that address is unreachable from the name server in question due to network or firewall configuration or some other reason, DNS records will not propagate from OBAS to the name server.


There are two ways to fix the issue:

  1. Make OBAS IP address reachable from the name server.

  2. Change the IP address of the OBAS server.

624ca542e40215e6f1d39170d8e7ec75 caea8340e2d186a540518d08602aa065 400e18f6ede9f8be5575a475d2d6b0a6 70a5401e8b9354cd1d64d0346f2c4a3e

Email subscription for changes to this article
Save as PDF