If your running cPanel DNS Only then 256MB RAM but if your using PowerDNS then 128 would be fine.

VestaCP is kinda good, installed on my VPS now and exploring. One advantage that I like is the Master>Slave DNS Clustering and it's Free as well.

* Reverse DNS Available (On Request)

(Quote)

In my experience, Gmail will accept mail with a valid SPF entry and a valid DKIM header and no reverse DNS entry.

There is a reason for dropping UDP during certain UDP attacks and any DDOS protection experts should know about it. Guarantee no UDP drop is simply not possible if you are going to protect UDP servic…

As the discovery of your domain name is done by the dns part that you don't want to change only a failover ip setup would do that!

As for pointing it to an external address, that would be DNS or a redirect, if I understand you correctly. A .htaccess file with mod_rewrite directives should be in the workflow for that.

DOs panel is beautiful though. Love the free DNS aswell.

Your provider has to set rdns, you can't do it (unless you control the IP allocation).

This is driving me insane, I have set rDns in solusvm & added SPF & Dkim at my domain provider (internetbs) I have also added rDns in WHM add dns zone.

But yes, in short, you've got the idea. Ports 80 and 443 are forwarded to nginx, and nginx will reverse proxy all traffic to the respective VMs, based on the DNS host header. ALL traffic will ultima

Can be done in WHM via the DNS zone editor. Could edit the default template.

speed. You can also get free backups and free DNS hosting. We are proud to offer a 99.95% uptime SLA.

One more cache you can control... your router. Power cycle it and your cable modem/dsl modem/Fios router/whatever. That'll flush its DNS cache.

Phone does DNS lookup from different cached server (Wireless company) than your PC which does the lookup from your ISP's DNS cache. If you're running Windows, try "ipconfig /flushdns&quot

Assuming that I point the DNS correctly, what do I need to do on the proxmox host to allow the browser to utilize the NATed VMs where 'centos-vm.proxmoxhost.com' brings up the CentOS VM's web page and

1and1 sometimes takes hours to update their DNS servers. Did you try to ping repo.mysite.com from your local computer to see whether the IP address is correct?

It's (most likely) a DNS issue. Defining document root in that 1and1 DNS thingy doesn't seem right. That sounds like a shared hosting feature. A subdomain should be a simple A or a CNAME.

Everything seems to be in order in the configs, looks like it's most likely a DNS issue.