Domain resolves always to old parent domain (when was used as alias)

[gkot1500]

There is a client that uses 3 domains (1 + 2 alias)
dom1.com

with 2 domain alias
dom2.com
dom3.com

Client decided to create a brand new website for domain dom3.com

I deleted the alias for dom3.com and created a new subscription on the same server, same ip.
After 4 days the dom3.com resolves to dom1.com. Is this normal?
The nameservers are idem for both 3 domains. Is there a way that plesk ("unchain") the domain alias?

Thanks

 

[IgorG]

created a new subscription on the same server, same ip

What do you mean exactly:

dom3.com resolves to dom1.com

?

 

[gkot1500]

The ip in plesk panel is shared.
I mean that dom3.com (with the new subscription) "looks" the dom1.com as it was all these years.

Here are the links:
Subscription
http://www.synagermoi.com.gr

The alias
http://www.easyalarm.gr

and the new subscription that i've created
http://www.easy-alarm.gr

The easy-alarm domain was in the past years alias of the synagermoi.com.gr.
I deleted the alias 5 days ago and now should words as subscription.

 

[IgorG]

First of all I would check their document root directories.

 

[gkot1500]

Thanks Igor
So, i've checked the psa database and all the records on both subscriptions (synagermoi.com.gr/ easy-alarm.gr)

The settings in tables:
configurations
dns_recs
dns_zone
domains
hosting
domainaliases and
sys_users

seems OK.

Especially the 2 files that includes the document root directories are doubled checked:

>> configurations table> col. file> Configurations-file.bin> where guided me to check the
/var/www/vhosts/easy-alarm.gr/conf/xxx_httpd.include:

DocumentRoot "/var/www/vhosts/easy-alarm.gr/httpdocs"

This is OK

>> hosting table> col. www_root> bin file

/var/www/vhosts/easy-alarm.gr/httpdocs

This is OK

I've also checked that the ftp server works fine and gives me access to the right folder of the new subscription (easy-alarm.gr)
It seems that only the webserver is stacked on the old root

Any more idea where i can check?

 

[gkot1500]

Ok my last sentence gave me the solution... OMG was so simple

It seems that only the webserver is stacked on the old root

Just restarted the apache service and the new root is serviced!

Thanks anyway for your help