Domain exists on xxx

gate2vn

Verified User
Joined
Nov 9, 2004
Messages
514
Location
Oslo
I have 2 DNS servers. The web server is connecting to them by multi server connections.
On the web server, I have a domain 123.abc.com. Now, changed it to xyz.com successfully (verified on both DNS servers), and wanted to add 123.abc.com as the domain pointer of xyz.com. But DA keeps saying domain exists on dns server.

Double checked on each DNS server, no 123.abc.com. Checking realtime BIND blog in DNS servers, there is no request 123.abc.com or xyz.com.

Testing by changing xyz.com back to 123.abc.com, I cannot do that anymore, with the same answer: Domain exists on xxx

Where can I find the reason for this? I am on DA 1.670
Thanks.
 
Last edited:
Nope. Checked.
We , i had that after domain was made and deleted in the past , i don't know with which procedure.
But never solved , here because not so important for me those 2

So if you have made a domain before and somehow changes or deletion then you have to search here or ask support maybe same old error as then
 
I don't know, it must be present somewhere but I don't know where exactly it's all saved.
If yo have license which is monthly paid, you could try to send in a ticket otherwise maybe @zEitEr might know where to look.
 
Running debug mode, I got this

Checking referer https://webserver-name:2222/evo/user/domain-pointers to webserver-name:2222
Referer check passed: webserver-name:2222=webserver-name:2222
auth.authenticated
Command::doCommand(/CMD_JSON_VALIDATE)
PunyCode::has_utf8(123.abc.com)
Cluster::existsDnsZone('123.abc.com', check_for_parent_domain=true): found parent domain on remote server dnsserver-name for subdomain.
Domain::exists: domain exists in DNS(2): dnsserver-name<br>
<br>

Command::doCommand(/CMD_JSON_VALIDATE) : finished
Command::run: finished /CMD_JSON_VALIDATE

On the DNS server, abc.com exists, but there is no record related to 123.abc.com. Then I manually refreshed the DNS zone of abc.com by adding and removing a record. Tada... now I can add 123.abc.com from the web server.

It looks like DA keeps cache somewhere. But even I tried to restart DA, named services before, it didn't help. Still confused how the cache is working in DA, but at least I get what I wanted to do.
 
Back
Top