Article ID: 4360, created on Mar 24, 2008, last review on Apr 18, 2012

  • Applies to:
  • Sphera

Symptoms

The Primary DomainDirector has a new configuration file under [DD Base]/etc/named.domains.

Purpose of this file is to be additional repository on DD level of primary VDS domain vs. additional ones (Secondary Domains).

Format of each line in this file is :

'<primary-vds-domain>:<add domain1> <add domain2>....<add domain N>'

At this file is important to know which additional domains must be deleted / changed while disabling / changing the main one.

When trying to upgrade a VDS from SD3.5 to SD3.7, an error appeared :

*ERROR* API Error : [Target Server Name] : The domain [Domain Name] is occupied

1. One of the additional domains was not listed in this file for unknown reason, but was defined in named.conf. When the VDS was disabled on the source server (while Move step1), this domain wasn't deleted from named.conf.

2. When destination server tried to enable the DNS for this VDS, the command with all the list of the domains was send, and that 'lost' domain caused the error.

3. The rollback (which was performed after that) also sent the same DNS-enable command, but from the source SD. Because the problematic domain in named.conf already exists, but all credentials are the same with what source SD tried to add, there is no error. Also this operation rewrote the line in named.domains, but this time with all additional domains in.


 

Resolution

 

Perform the Upgrade again for that VDS, as the rollback fixed the entry in named.domains file.

 


5f478287f7e74fe9b07217d8131cd741 6311ae17c1ee52b36e68aaf4ad066387

Email subscription for changes to this article
Save as PDF