Why can't I access www.(example.com)?


Our servers are currently configurated using the Plesk Control Panel (versions 9.0.x). Within these version exists a bug where some (but not all) new domains, however created, seam to have their www. entry missing from the DNS servers' configuration files. This prevents the DNS server from issuing an IP address to a www. request, hence www.example.com fails with 'Server not found' when just example.com works fine.


The solution itself is very simple; log onto the Control Panel (if at the Client Level, select the affected domain from the available list), click on DNS and then click Disable & click then Enable once the page is refreshed. This switch off & on removes, re-creates and re-inserts the data correctly back into the DNS server.


There is usually a small delay before the domain comes back online (failed entries are cached in local servers just as with valid ones, however this is usually only for a one hour). If you are still experiencing problems after an hour, please contact our Support Team who will assist you in tracking down the problem. For more information about how DNS caching works, please see our article:


  • 93 Users Found This Useful
Was this answer helpful?

Related Articles

Why can't I access www.(example.com)?

Our servers are currently configurated using the Plesk Control Panel (versions 9.0.x). Within...

Can I host the same website using more than one domain?

Unfortunately, no. Plesk has a fixed system whereby each domain has it's own dedicated web...

Can I install programs such as phpBB and Mambo?

All our accounts provide access to a wide-range of languages and utilities Using these, you are...

Can I view my access and error logs?

By default, you can only view the access and error logs though the Plesk Control Panel. The...

How do I view the statistics for my website?

There are two ways to access the statistics generated by our systems. This solely depends on...