Search Engine: Elastic

Article ID: 132439, created on Mar 26, 2018, last review on Mar 26, 2018

  • Applies to:
  • Business Automation 7.2

Question

The domain was registered in OA as domain registered elsewhere (with NSes set to OA), later customer decided to transfer the domain (through BA). As a result of transfer the domain lost its hosting OA (DNS hosting was changed to External). Why did it happen, if before the transfer NSes were already correct, set to OA?

Answer

The domain service template has an option Name Servers for Domain Transfer set to Leave existing name servers. The system does the following:

a) asks plugin with the method GetDomainNameServers -> writes the NS if received

b) if the plugin method is not implemented, or there is no reply there is an attempt to get NSes with the system methods -> writes these NSes

valid since OSA 7.1 (change is made in scope of the feature "Ability to specify external nameservers during domain registration/transfer")

c) gets the data written on step a or b with the method DomainInfoGet_API

d) get the list of NSes from OA, by pem.getDomainNameServers

e) compares the list from c and d. If the records are equal BA send request pem.addDomain with the parameter external_domain set to 0, otherwise - set to `1'. In case of external domain, NS records from BA are left, domain in OA gets External hosting, no DNS resource usage on the subscription.

It is important for the domain plugin to return the records in the correct way - without dot at the end of the record. The records:

ns1.server.com.

and

ns1.server.com 

are considered as different records. So, you may need to adjust custom plugin.

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 ef171e3fccb12bd8e09076a7b49212c0 b2c3b33425dfc50c7d41a2efaa7f84f3

Email subscription for changes to this article
Save as PDF