[deanhills]

Hi all experts.
I was successful user of freenom free domain in past. but for some reasons my vps data is dismissed. now i try to reprogram my vps ip to freenom domain and all settings goes done successfully. even i update cloudflare support. and all settings done and site shown active. but when i put my domain to activate my server or http page. even apache. they do not reply. any expert help me where i go wrong?

Agreed with @arsalahmed786.  It may take some time for the DNS of your domain to propagate.

For post4vps super geeks to assist you here (I'm not one but am trying to help) you need to provide more information of how you set up the domain.  On the simplest level my own personal advice is to reload your OS - maybe you could ask the staff to do it for you?  I've had issues myself with a paid VPS recently when the VPS host loaded the OS with the wrong host name.  What happened is it could not talk to the new domain, even when I had changed the host name in the panel.  What was interesting though is that I could see the content of the VPS when I used the IP number instead of the domain name.  I guess your problem now taught me that it must have been the Apache configuration that needed tweaking.  So I guess if you don't want to mess around with Apache, the easiest is to start from scratch and get the Staff to help you reload the OS.

If you do want to mess with Apache you need to tweak the configuration .conf file - it may still contain the previous host name so you need to change it to the new host name/domain by going into it as this is where Apache listens when it responds to Port 80. The .conf file should be in a directory that looks much like this one:

/etc/httpd/conf.d

My host name is contained in vesta.conf (not sure what yours is but you can check by reading through the files that are in the above directory) This is the wording in my vesta.conf file - it shows which domains to include:
Include /home/admin/conf/web/domain.us.httpd.conf
Include /home/admin/conf/web/domain2.net.httpd.conf
Include /home/admin/conf/web/domain3.us.httpd.conf
etc

For me it would make sense if the old domain name is still there that you need to change it to the new domain name so Apache will then listen to the domain on Port 80.  If I had done that previously, maybe that would have solved my problem too.  Or who knows, maybe it was just as simple as that I should have restarted Apache.  I only did a reboot of the VPS.  Don't forget to restart Apache.