Overview

DNS (Domain Name System) configuration is a foundational requirement for ensuring uninterrupted access to your Simpplr portal and related services. Proper DNS setup enables:

• Secure access to the Simpplr portal

• SSL/TLS certificate issuance and renewal

• Reliable backend/API communication

• Outbound email authentication and delivery

Any modification, removal, or misconfiguration of required DNS records can lead to service disruptions and security issues.

Potential Impact of Incorrect DNS Changes

Improper DNS changes may result in:

• Portal inaccessibility

• Application or API failures

• SSL/TLS certificate renewal failures

• Email delivery or verification issues

• Extended downtime requiring coordination between your IT team and Simpplr Support

To avoid service interruptions, it is important to understand the DNS onboarding model used for your environment and maintain the required DNS records accordingly.

Supported DNS Onboarding Models

Simpplr supports two DNS onboarding approaches:

1. Simpplr Managed DNS

2. Customer Managed DNS

Option 1: Simpplr Managed DNS

Overview

In this model, Simpplr manages DNS configuration for your portal.

Customers delegate DNS authority to Simpplr by adding NS (Name Server) records to their domain configuration.

Simpplr manages:

• DNS configuration

• Frontend and backend routing

• SSL/TLS certificate issuance and renewal

• SES identity verification and email-related DNS records

• Ongoing DNS maintenance

Customer Responsibilities

Customers are responsible for:

• Maintaining the NS records provided by Simpplr

• Ensuring NS records are not removed or modified after onboarding

DNS Architecture Flow

Customer Domain
      │
      ▼
NS Records Delegated to Simpplr
      │
      ▼
Simpplr Managed DNS
      │
      ├── Frontend Routing
      ├── Backend Routing
      ├── SSL/TLS Certificate Management
      └── SES Identity Verification & Email Configuration

Important Notice

Removing or modifying delegated NS records can immediately disrupt DNS resolution and may cause:

• Complete portal outage

• SSL/TLS certificate renewal failures

• Email verification or delivery failures

Option 2: Customer Managed DNS

Overview

In this model, customers manage DNS records using their own DNS provider.

Simpplr provides the required DNS entries, typically in the form of CNAME records, which customers must maintain permanently.

These records commonly include:

• Frontend CNAME

• Backend/API CNAME

• Certificate validation CNAME records

• SES identity verification CNAME records

Customer Responsibilities

Customers must:

• Maintain all DNS records provided by Simpplr

• Ensure records are not removed during:

  • DNS cleanup activities

  • Domain migrations

  • Security audits

  • Infrastructure changes

• Periodically review DNS configuration to ensure continued validity

DNS Architecture Flow

Customer Domain
      │
      ▼
Customer Managed DNS
      │
      ├── Frontend CNAME → Simpplr
      ├── Backend CNAME → Simpplr
      ├── Certificate Validation CNAME → Simpplr
      └── SES Verification CNAME → Simpplr

Important Notice

Removing Simpplr-provided CNAME records may result in:

• Portal inaccessibility

• Backend or API communication failures

• SSL/TLS certificate renewal failures

• Email verification or delivery issues

• Unexpected downtime requiring manual intervention

Importance of Certificate Validation CNAME Records

Certificate validation CNAME records are required for automated SSL/TLS certificate renewal.

If These Records Are Removed

The following issues may occur:

• Existing certificates may expire

• Browsers may display security warnings

• Secure access to the portal may fail

• Renewal failures may only become visible during automated renewal cycles

Because certificate renewal is automated and periodic, issues may not appear immediately after DNS changes.

Importance of SES Verification Records

SES (Simple Email Service) verification records are required to maintain authorized email sending capabilities for your Simpplr environment.

These DNS records support:

• Email domain verification

• DKIM validation

• Secure outbound email delivery

• Notification and system email functionality

If SES Records Are Removed or Modified

Potential issues include:

• Failure of outbound email delivery

• Missing notifications or system-generated emails

• DKIM or authentication validation failures

• Email reputation impacts

These problems may appear later during periodic verification or email validation checks.

Best Practices and Recommendations

Simpplr strongly recommends the following practices:

Do Not Remove or Modify Required DNS Records

Avoid changing or deleting:

• NS records delegated to Simpplr

• Simpplr-provided CNAME records

• Certificate validation records

• SES verification records

Inform Internal Teams

Ensure your:

• IT administrators

• DNS administrators

• Security teams

• Infrastructure teams

are aware of the dependency on Simpplr-related DNS records.

Validate DNS Before Infrastructure Changes

Review and validate DNS configurations before performing:

• DNS migrations

• Security audits

• Domain cleanup activities

• Registrar changes

• Infrastructure modernization projects

Coordinate with Simpplr Support

Contact Simpplr Support before making DNS-related changes to avoid unintended service disruption.

Impact of DNS Record Removal

Support and Recovery Process

If DNS records are accidentally removed or modified:

• Immediate restoration may require coordination between customer IT teams and Simpplr Support

• DNS propagation delays may extend recovery timelines

• Service restoration may not be instantaneous

To minimize risk and downtime, customers should proactively engage Simpplr Support before making planned DNS changes.

Need Assistance?

For guidance related to DNS configuration, migrations, or planned DNS changes, please contact Simpplr Support before making modifications to your DNS environment.