Overview
This article helps you understand and manage domains in Access Volcanic. You'll learn how to work with live and staging domains, fix staging links in job postings, and manage Domain Name System (DNS) configuration. Domain management ensures your website remains accessible, secure, and properly configured for candidates and clients.
Key benefits
Streamline content management between live and staging domains safely.
Resolve staging links that appear in job postings and integrations.
Configure DNS records and SSL certificates for secure website access.
Implement domain redirects when migrating from old websites.
Complete site ownership verification using supported methods.
Maintain reliable website performance and accessibility for users.
Before you start
Before managing domains, make sure you have:
Admin access to your Access Volcanic platform.
Knowledge of your DNS provider and login credentials.
Understanding of your current domain configuration.
Access to your domain registrar account for DNS changes.
📌 Note: Access Volcanic does not manage your DNS or own your domain. You're responsible for DNS account management and adding provided records correctly.
Understanding your domains
Primary domain
Your primary domain is the live website address that candidates and clients use to access your site.
Examples include https://www.example.com or https://careers.example.co.uk.
Key characteristics:
Changes appear almost immediately after page refresh.
Used for marketing campaigns, job sharing, and public links.
SSL certificate is issued for secure HTTPS access.
Visible to all users and search engines.
Staging domain
Your staging domain is a non-public version used for editing, configuration, and testing.
Key characteristics:
Safe environment for making and reviewing changes.
Updates typically appear on live site due to platform caching.
Reduces risk of users seeing incomplete content.
Not intended for public sharing or marketing use.
📌 Note: You may occasionally see staging URLs in links from integrations. Later sections explain how to recognise and fix these.
Managing content between domains
Recommended editing workflow
To protect user experience and reduce risk:
Edit content on staging where possible.
Review and test changes on staging.
Allow caching to refresh so changes appear on live domain.
Share links using the live domain only.
Benefits include fewer visible errors, consistent user experience, and time to test changes before going public.
Making urgent changes visible immediately
For critical updates that need immediate visibility:
Open the page on your primary domain.
Edit the content and save changes.
Refresh the page in your browser.
Clear browser cache or use incognito browsing if changes aren't visible.
⚠️ Important: Use direct live editing sparingly to avoid disrupting the user experience.
Accessing your live site
If you're stuck on the staging domain:
Check your browser URL.
Replace the staging portion with your live domain.
If redirected to staging, refresh your browser and clear cache.
Use incognito browsing mode if redirection persists.
🤓 Tip: Bookmark your live domain to avoid accidentally using staging links.
Fixing staging links
Why staging links appear
Job links may point to staging instead of live domains when integrations use staging API keys.
Common integrations that may generate staging links:
Example staging link: https://domain.staging.krakatoa.eu-2.volcanic.cloud/job/actor-1.
Impact of staging links
Minimal impact on candidates who are usually redirected correctly.
Jobs process normally through integrations.
Consultants may see and share staging links until configuration is updated.
Recognising staging links
Look for these URL components:
.staging.krakatoa.eu-2.volcanic.cloud
If job or page links contain these elements, they're staging links rather than live domain links.
Requesting integration fixes
To update integration configuration:
Contact support with details about staging domain links.
Explain that job links point to staging domain.
Include example URLs and integration name.
The support team will update your integration settings so new links use your live domain with no downtime or performance impact.
Manual link correction
While waiting for integration updates:
Replace staging domain portion with your live domain.
Keep the same path and slug.
Refresh browser and clear cache if still redirected to staging.
Example correction:
Changing your primary domain
When to change domains
You may need to change your primary domain when:
Purchasing a new domain name.
Rebranding your organisation.
Moving between regional domains (.co.uk to .com).
Requesting domain changes
To change your primary domain:
Submit a support request to Access Volcanic.
Confirm you want to change the primary domain.
Provide the new domain name.
Include internal approval references if relevant.
Access Volcanic will generate required DNS records and provide them in the support case. You must add these records to your DNS provider account.
⚠️ Important: Access Volcanic cannot log into your DNS account for security reasons.
Impact on feeds and integrations
When your primary domain changes:
XML feeds automatically update to use the new domain.
External systems consuming feeds must be updated to use new feed URLs.
Integration partners need notification of the domain change.
Managing DNS
Understanding DNS responsibility
Access Volcanic provides DNS records but doesn't manage your DNS account.
Your responsibilities:
Manage DNS account with your domain provider.
Add provided DNS records exactly as supplied.
Maintain DNS access credentials and account ownership.
Support's role:
Provide required DNS records for site hosting.
Issue SSL certificates through AWS.
Support DNS troubleshooting through provided records.
Finding your DNS provider
If unsure about your DNS provider, use online tools like Who.is or ICANN Lookup.
Typical process:
Open the lookup tool website.
Enter your domain name without protocol or trailing slash.
Review results to identify registrar or DNS host.
📌 Note: These are third-party tools and results aren't guaranteed. Confirm with your IT or domain team.
DNS records from Access Volcanic
Access Volcanic provides DNS records for:
Certificate validation (SSL)
Go-live configuration (A and CNAME records)
Example records include certificate validation CNAME records and go-live A/CNAME records for the platform.
SSL certificates and auto-renewal
How SSL works
Your Access Volcanic site uses SSL certificates for secure HTTPS connections through AWS.
Key points:
SSL certificates are generated and managed by Access Volcanic.
SSL certificates depend on correct SSL-related DNS records.
SSL-related DNS records don't affect other DNS records.
Access Volcanic cannot generate certificates for non-Volcanic sites.
SSL certificate auto-renewal
Your SSL certificate auto-renews annually with no manual action required.
Certificate renewal happens automatically.
Note expiry dates in internal systems for tracking.
Auto-renewal may fail if DNS records are removed or changed incorrectly.
Domain redirects
Why use domain redirects
When moving from an old website to Access Volcanic with a domain change:
Redirect traffic from old domain to new Volcanic domain.
Ensure users with old bookmarks reach the new site automatically.
Support SEO when configured correctly.
Preserve user experience during migration.
Setting up redirects
Setup process:
Log into domain provider account for the old domain.
Look for Domain Forwarding, Redirects, or URL Forwarding settings.
📌 Note: See this domain forwarding guide from GoDaddy as an example.
Create redirect from old domain to new Volcanic domain.
Save changes and allow time for DNS propagation.
Your domain provider has help articles on setting up redirects. Contact their support team if you need guidance.
Understanding permalinks
What is a permalink
A permalink (permanent link) is the URL of a web page intended to stay consistent over time.
Understanding permalink structure helps you manage content, redirects, and SEO effectively.
Permalink structure
A typical permalink has three main parts:
Example breakdown: https://www.example.com/jobs/marketing-manager
Part | Meaning | Example from URL above |
Domain | Main website address | |
Path | Section or category | /jobs |
Slug | Specific page identifier | /marketing-manager |
This structure helps when:
Checking whether links use live or staging domains.
Creating or managing redirects.
Reviewing URLs from an SEO perspective.
Site ownership verification
Many external services require domain ownership verification for Google Search Console or Google Analytics.
📌 Note: See our guides to learn more about setting up Google Analytics and Google Search Console on your website.
Recommended verification methods
Domain property (DNS TXT record)
This method uses a TXT record in your DNS without requiring site code changes.
Summary steps:
Log into Google account for your business.
Go to Google Search Console.
Choose Domain property type.
Enter your domain and click Continue.
Copy the provided TXT record.
Log into your DNS provider and add the TXT record exactly as provided.
Return to Google Search Console and click Verify.
URL prefix property (HTML tag)
This method verifies a specific URL prefix using an HTML meta tag through Page Tags.
Summary steps:
Log into Google account for your website.
Go to Google Search Console.
Select URL prefix property type.
Enter your URL and click Continue.
Choose HTML tag verification method.
Copy the provided meta tag.
Go to the Page Tags section in the Volcanic Admin Area.
Paste meta tag into the Header Code field and save.
Return to Google Search Console and click Verify.
Best practices
Know your domains: Understand live vs staging domains and always share live domains externally.
Use staging for changes: Make configuration changes on staging first and test thoroughly before they appear live.
Watch for staging links: Check for .staging.krakatoa.eu-2.volcanic.cloud in URLs and contact support for integration fixes.
Manage DNS internally: Track your DNS provider, maintain account access, and add records exactly as provided by Access Volcanic.
Monitor SSL and access: SSL auto-renews but depends on correct DNS records. Maintain DNS configuration for reliable certificate renewal.
Plan domain changes carefully: Coordinate DNS updates, feed changes, and integration updates when changing domains.
Use supported verification methods: Choose DNS TXT records or HTML meta tags over unsupported file upload methods for site ownership verification.
📌 Note: Following these guidelines ensures your site remains secure, accessible, and easy to manage.
FAQs
Q1: What's the difference between my live and staging domains?
Answer: Your live domain is the public website address used by candidates and clients. Your staging domain is a non-public version for editing and testing. Always share live domain links externally.
Q2: Why do some job links point to staging instead of live domains?
Answer: This occurs when integrations use staging API keys or are configured against staging environments. Candidates are usually redirected correctly, but contact support to fix the integration configuration.
Q3: Can Access Volcanic manage my DNS?
Answer: No, Access Volcanic provides DNS records but cannot log into your DNS account or manage it for security reasons. You must add provided DNS records through your domain provider.
Q4: How do I fix SSL certificate errors?
Answer: Check that SSL-related DNS records are present and unchanged in your DNS. Contact Access Volcanic support to confirm correct records if errors persist.
Q5: Can I upload verification files to my domain root?
Answer: No, Access Volcanic sites use cloud-based architecture that doesn't support root file uploads. Explain to third parties that your site lacks root file access and request DNS TXT or HTML tag verification methods instead.
Q6: How long does it take to change my primary domain?
Answer: Access Volcanic provides DNS records after you submit a support request. Domain changes become effective after DNS propagation, typically within 24-48 hours.
Q7: Will changing my domain affect my job feeds?
Answer: XML feeds automatically update to use the new domain. External systems consuming those feeds must be updated to use new feed URLs.
Q8: What should I do if I'm stuck on the staging domain?
Answer: Replace the staging portion in your browser URL with your live domain. Clear browser cache and cookies or use incognito mode if redirection persists.
Q9: How do I know if I have DNS problems?
Answer: DNS problems appear when your site is down, browsers report expired SSL certificates, or your domain doesn't resolve to your Volcanic site.
Q10: How do I troubleshoot DNS issues?
Answer: Confirm DNS provider account access, check for recent DNS changes, and revert incorrect changes. Contact Access Volcanic support for DNS record confirmation if issues persist.
Q11: What do SSL certificate errors look like?
Answer: SSL errors appear as "certificate expired" or "connection not secure" messages in your browser. These indicate SSL certificate or DNS record issues that need attention.