When a domain is not yet pointing to your JSP site, the most common cause is that the DNS change has not fully propagated, or the domain is still resolving to an old destination. In a hosting platform environment, especially when you use a Java/Tomcat setup such as My App Server in Plesk, the domain must point correctly before Apache, Tomcat, SSL, and mail services can work as expected.
For UK customers, this usually means checking the domain’s nameservers, DNS records, and the hosting account configuration before assuming there is a problem with the JSP application itself. In many cases the application is already deployed correctly, but the domain still reaches a previous host, a parking page, or the default web server response.
Why the domain may not point to the JSP site yet
There are several reasons why a domain can appear “not connected” to a JSP hosting site:
- DNS propagation is still in progress after a nameserver or A record update.
- The domain is using the wrong DNS zone or the wrong nameservers.
- The A record still points to an old IP address or another provider.
- The domain is not attached to the correct subscription or hosting account in Plesk.
- The Tomcat/JSP application is deployed correctly, but Apache is not yet routing requests to it.
- SSL is installed, but the domain is still visiting the non-HTTPS version or redirect rules are incomplete.
- Local DNS cache or browser cache is showing an outdated result.
- Mail records are not aligned yet if DNS was changed together with website hosting.
If the site is new, it is normal for DNS changes to take some time before they are visible everywhere. If the site was already live, then a recent update usually means the domain configuration or DNS zone needs review.
How JSP hosting works with a domain in Plesk
In a My App Server setup, the domain is typically handled by the web server layer while the JSP application runs in a private Tomcat or JVM instance. The basic flow is:
- The domain resolves to the hosting server IP through DNS.
- Apache receives the request for the domain.
- Plesk routes the request to the configured Java application or Tomcat service.
- Your JSP, servlet, or WAR application responds.
If any part of this chain is misconfigured, the domain may load a default page, show an error, or not reach the JSP site at all. That is why domain pointing issues are often a DNS problem first, and a hosting mapping problem second.
What to check first
1. Verify the nameservers
If your domain uses external DNS, confirm that the nameservers are the ones intended for your hosting setup. If the nameservers were changed recently, the domain may still be updating across the internet.
Check:
- Whether the domain is using the correct authoritative nameservers
- Whether the DNS zone is managed at the registrar or in the hosting control panel
- Whether the hosting provider’s DNS records are actually active for this domain
2. Check the A record and AAAA record
The domain should point to the correct server IP address. For most JSP hosting setups, the primary record is the A record for the root domain and the www subdomain.
Confirm:
- example.co.uk points to the correct IPv4 address
- www.example.co.uk points to the same place, or is redirected consistently
- The AAAA record does not point somewhere unexpected if IPv6 is enabled
If an incorrect AAAA record exists, some users may reach the wrong location while others reach the correct one, depending on their network and browser.
3. Make sure the domain is added in Plesk
For a Java hosting account, the domain must be present in the correct subscription or hosting space. In Plesk, the domain should be assigned to the subscription where My App Server and Tomcat are configured.
Check whether:
- The domain exists in the correct subscription
- The document root and application paths are set correctly
- The Tomcat or Java service is enabled for that domain
- The web application is deployed to the correct virtual host
4. Confirm the JSP application is deployed
Sometimes the domain is pointing correctly, but the application has not been uploaded, started, or linked. In a JSP hosting environment, verify that the WAR file, servlet app, or exploded application is deployed properly.
Useful checks include:
- The application package is present in the expected directory
- Tomcat is running
- The application context path matches the domain mapping
- There are no startup errors in the application logs
DNS propagation and why it matters
DNS propagation is the time it takes for updated DNS information to be visible across resolvers and networks. Even after you change the domain’s records, some users may continue to see the old site for a while.
Common reasons propagation takes time:
- Cached DNS entries at ISP or resolver level
- Previous TTL values set to a longer duration
- Browser cache or device-level cache
- Corporate or mobile network caching
If you recently switched a domain to a new JSP hosting account, allow time for the new DNS information to spread. During this time, the site may work in one browser or location but not another.
How to tell if propagation is the issue
Propagation is likely if:
- The domain works from some devices but not others
- You can see the site using a direct server IP, but not the domain
- The old website still appears in some places
- DNS tools show different answers from different resolvers
How to verify the domain is pointing correctly
Use these practical checks in order:
- Open the domain in a browser and note the exact result.
- Test both the root domain and the www version.
- Check DNS resolution from a public DNS lookup tool.
- Compare the returned IP address with the hosting server IP in your control panel.
- Review the domain settings in Plesk or the registrar DNS zone.
- Confirm the JSP application is active in My App Server or Tomcat.
If the domain resolves to the right IP but the page still does not load the JSP site, the issue is probably in the web server or application routing rather than DNS.
SSL considerations when the domain is not yet pointing
SSL can make pointing issues look more complex than they are. If a certificate is installed before the domain fully resolves, browsers may show certificate warnings, redirect loops, or a default page that does not match the intended site.
Check the following:
- The SSL certificate covers the correct domain name
- The certificate is installed on the same hosting instance as the JSP app
- HTTP to HTTPS redirects are not sending traffic to an old domain target
- The domain resolves correctly before forcing HTTPS
For best results, confirm that the DNS points to the correct hosting server first, then validate the SSL setup, and only after that finalize redirects.
Mail records and DNS changes
When customers update DNS for a JSP site, mail settings are often changed at the same time. This can cause confusion if the domain appears partly correct for the website but mail stops working or starts behaving unexpectedly.
Review these records separately:
- A record for the website
- MX record for email delivery
- TXT records for SPF, DKIM, and verification
- CNAME records for www or service aliases
A website pointing issue should be solved without accidentally breaking mail routing. If the domain is used for both JSP hosting and email, keep each record type aligned with the intended service.
Apache, Tomcat, and My App Server checks
In a hosting platform with My App Server, the domain can point correctly at DNS level but still not display the expected JSP site if Apache or Tomcat is not configured to serve that domain.
Check Tomcat service status
- Make sure the Tomcat service is running
- Verify the selected Java version is compatible with your application
- Confirm the private JVM or application server has enough allocated resources within the account limits
- Review application logs for startup failures
Check Apache routing
Apache should receive the request and forward it correctly to the Java application when the setup uses a web front end. If the domain shows a default page, Apache may be pointing to the wrong document root or virtual host.
Common routing problems include:
- Incorrect virtual host mapping
- Wrong domain alias configuration
- Application context path mismatch
- Proxy or rewrite rules not matching the intended JSP app
Step-by-step troubleshooting process
Step 1: Confirm where the domain currently resolves
Use a DNS lookup tool or your local network diagnostics to see what IP address the domain returns. Compare that with the hosting server IP in Plesk.
Step 2: Review the DNS zone
Open the DNS zone in the registrar or hosting control panel and check the root domain and www records. Remove or correct any outdated values.
Step 3: Verify the domain in the hosting panel
Make sure the domain is present in the correct subscription, and that the Java application is associated with it. If you use My App Server, confirm the service configuration is active for this domain.
Step 4: Restart or recheck the Java service if needed
If the application was recently deployed, Tomcat may need a restart or a redeploy. After changes, check the service control area in Plesk and review the logs for errors.
Step 5: Test from a clean browser session
Use an incognito window or clear DNS/browser cache. Then test the root domain, www version, and HTTPS version separately.
Step 6: Confirm SSL and redirects
If HTTPS is enabled, ensure the certificate is valid and the redirect target is the same domain you expect. Avoid redirecting to a domain that still points elsewhere.
Typical fixes that resolve the issue
- Update the A record to the correct server IP
- Switch the domain to the correct nameservers
- Wait for DNS propagation to complete
- Attach the domain to the correct Plesk subscription
- Deploy the JSP application to the correct context
- Restart Tomcat or the private Java service
- Correct the HTTPS redirect target
- Remove conflicting AAAA or old CNAME records
Examples of common scenarios
Scenario 1: New domain, new JSP site
The domain was registered recently and the DNS records were set to the new hosting IP. The site does not show immediately. In this case, the problem is usually propagation or a DNS record typo. Confirm that both the root and www records point to the same server.
Scenario 2: Existing domain moved to My App Server
The domain used to point to another host, and now it should load a JSP application from Plesk. If some users still see the old site, the old DNS values are likely cached or the nameserver change has not fully spread.
Scenario 3: Domain resolves correctly but shows the wrong page
This often means DNS is fine, but Apache or Tomcat is not mapped to the correct application. Recheck the domain assignment, application context, and Java service configuration.
Scenario 4: Site works on HTTP but not HTTPS
The DNS is correct, but SSL or redirect configuration is incomplete. Install or reissue the certificate for the right hostname and confirm the redirect points to the same live domain.
When to contact support
Contact support if you have already confirmed the DNS records, nameservers, and domain assignment but the JSP site still does not load correctly. Useful information to include is:
- The domain name
- The expected IP address
- Whether the issue affects root, www, or both
- Whether HTTP, HTTPS, or both are affected
- Any recent DNS, SSL, or Tomcat changes
- Relevant error messages or screenshots
This helps the support team quickly determine whether the issue is DNS, SSL, routing, or application deployment related.
FAQ
How long does it take for a domain to point to a JSP site?
It can take from a few minutes to longer, depending on DNS TTL values, the registrar, and resolver caching. In some cases, changes are visible quickly; in others, propagation takes longer.
Why does the site work on the server IP but not on the domain?
This usually means the hosting application is working, but the DNS record or virtual host mapping is still incorrect.
Can SSL stop a domain from pointing correctly?
SSL does not control DNS, but a misconfigured certificate or redirect can make the site appear broken even when DNS is correct.
Why do I see the old website after changing the DNS?
Old DNS data may still be cached, or one of the records is still pointing to the previous host. Check the A, AAAA, and CNAME records carefully.
Do I need Tomcat running for the domain to work?
If your JSP application depends on Tomcat, yes. The domain may resolve correctly, but the site will not respond properly if the Java service is stopped or not mapped.
Should www and the root domain point to the same place?
Yes, in most cases they should either point to the same hosting destination or one should redirect consistently to the other.
Conclusion
If the domain is not pointing to the JSP site yet, start with DNS, then verify the Plesk domain assignment, and finally check the Tomcat or My App Server configuration. In a managed hosting setup, the issue is often not the JSP code itself, but the connection between the domain name, web server, SSL certificate, and Java application.
Once the A record, nameservers, SSL settings, and application mapping are aligned, the domain should begin serving the correct JSP site normally. If the problem remains after these checks, the fastest next step is to review the logs and contact support with the exact domain and symptoms.