Upon initial setup of the site, we will provide the name servers names/IPs for a managed subdomain within our environment. For example, for acme.com with a community at community.acme.com, the subdomain community.acme.com will be managed inside of hosting. The provided name servers will need to be deployed to the root domain and after completion hosting will manage the subdomain for routing, ssl management, ssl domain verification, email identity verification and all items that require dns specifically for that subdomain. It does not change the root domain behavior and can always be revoked at the root domain.
You make a one-time update in your DNS, adding Nameserver (NS) records that delegate control of your community's subdomain (for example, community.companyname.com) to Verint. Verint then manages everything behind that subdomain. Your root domain and all other DNS records stay fully under your control.
Why it benefits you
Less work for your IT team. After the initial setup, there are no DNS change tickets for routine platform updates, scaling, or maintenance.
No expired-certificate outages. We can validate and renew your TLS certificates automatically, so your community never goes down because a cert lapsed.
Faster response during incidents. If we need to fail over, re-route traffic, or put protection in front of the site (WAF, DDoS mitigation), we can act in minutes without waiting on a change window or an approval chain on your side.
Smoother upgrades and migrations. Moving to new infrastructure, regions, or platform versions doesn't require a coordinated cutover with your network team.
Better performance and availability. We can use health-checked records and geo- or latency-based routing to send your users to the best-performing endpoint.
Stronger security hygiene. Because we own both the DNS records and the resources they point to, we can retire records when infrastructure changes, which prevents stale entries and subdomain takeover risk.
Clear accountability. One party owns the stack from DNS to application, which makes troubleshooting faster and SLAs simpler.
What stays with you
Your root domain (companyname.com) and every other subdomain
The ability to revoke the delegation at any time
Visibility into changes, per our change-notification commitments
You make a one-time update in your DNS, adding Nameserver (NS) records that delegate control of your community's subdomain (for example, community.companyname.com) to Verint. Verint then manages everything behind that subdomain. Your root domain and all other DNS records stay fully under your control.
Why it benefits you
Less work for your IT team. After the initial setup, there are no DNS change tickets for routine platform updates, scaling, or maintenance.
No expired-certificate outages. We can validate and renew your TLS certificates automatically, so your community never goes down because a cert lapsed.
Faster response during incidents. If we need to fail over, re-route traffic, or put protection in front of the site (WAF, DDoS mitigation), we can act in minutes without waiting on a change window or an approval chain on your side.
Smoother upgrades and migrations. Moving to new infrastructure, regions, or platform versions doesn't require a coordinated cutover with your network team.
Better performance and availability. We can use health-checked records and geo- or latency-based routing to send your users to the best-performing endpoint.
Stronger security hygiene. Because we own both the DNS records and the resources they point to, we can retire records when infrastructure changes, which prevents stale entries and subdomain takeover risk.
Clear accountability. One party owns the stack from DNS to application, which makes troubleshooting faster and SLAs simpler.
What stays with you
Your root domain (companyname.com) and every other subdomain
The ability to revoke the delegation at any time
Visibility into changes, per our change-notification commitments
Thank you both for the info. I think I understand what you're saying, but our community is already a subdomain of our main website which is why I was trying to understand how this would work. I've asked my IT team if they have any issues with what you're suggesting and I'll update the thread when I've heard back.
More than likely you would have a single CNAME record(possibly an A record but not as common) that is creating and routing your subdomain to hosting. This record would be removed and replaced by an NS record with the name servers I mentioned that are provided.
