Can I use an electronic signature for this form?

Yes. Electronic signatures are valid under the ESIGN Act (15 U.S.C. §7001) and UETA when intent, consent, signer attribution, and reliable record retention are present. For consumer-facing notices, provide ESIGN consumer disclosure when required.

Do I need a notarized signature on the form?

Not usually. Notarization is only required if internal policy, contract, or specific state law demands it. Remote online notarization may be acceptable where authorized by state law; verify state notary rules before relying on electronic notarization for authenticity.

What supporting documents should I attach?

Attach DNS export, current SSL/TLS certificate details, hosting provider contacts, vendor change agreements, and proof of authority such as corporate resolution or delegated signing authorization. Missing documentation delays approval and complicates rollback planning during migration.

How long does processing usually take?

Processing varies by organization: simple internal updates can complete within one to three business days; complex migrations requiring certificates, vendor coordination, or legal review may take several weeks. Plan for DNS propagation and certificate issuance when estimating cutover dates.

What if DNS changes break services?

Have a documented rollback plan and pre-tested configuration. Monitor DNS propagation, MX and SPF records, and certificate status immediately after change. If services degrade, trigger rollback per plan and notify stakeholders; preserve logs for root cause analysis.

Can signNow handle electronic submission and storage?

Yes. signNow supports signed form capture, audit trails, and secure storage with AES-256 at rest and TLS 1.2/1.3 in transit. SignNow offers HIPAA compliance (BAA required) and integrations with CRM and storage platforms to streamline workflows.

Electronic Signature
Templates
Miscellaneous
Domain Change Request Form

Domain Change Request Form

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

Domain Change Request Form and Service Agreement

Parties

Client Name:

Client Contact Information Service Provider Provider Contact Information

Recitals

WHEREAS, Client currently operates the website and related services at Current Domain: and seeks to replace or reassign the domain name and associated DNS, hosting, and certificate configurations; and

WHEREAS, Service Provider is engaged in the business of domain management, DNS configuration, hosting migrations, SSL certificate provisioning, and related technical services and agrees to perform the domain change services under the terms and conditions set forth in this Request and Agreement; and

WHEREAS, the parties intend that the execution of this form will authorize Service Provider to take specified actions to effect the domain change and memorialize payment, timing, confidentiality, and governing law provisions for those services.

Domain Change Request Details

Requested New Domain Planned Cutover Window

Preferred Date: Preferred Time (TZ):

Services Requested (select all that apply)

DNS update and propagation monitoring
Hosting migration and URL redirect configuration
SSL certificate procurement and installation
CDN/WAF and cache invalidation coordination
Domain registrar transfer assistance

Scope of Work

Detailed Scope

Payment Terms

Total Fee:

Payment Schedule

Late Fee: If payment is not received within days of invoice due date, a late charge of per month will accrue on the outstanding balance.

Term and Termination

Commencement Date: . Expected Completion Date:

Either party may terminate this Agreement for material breach if the breaching party fails to cure such breach within days after written notice. Additionally, either party may terminate for convenience upon days' prior written notice to the other party; termination for convenience will not relieve Client of payment for services performed through the effective date of termination and any non-cancellable third-party costs incurred by Provider.

Confidentiality

Each party agrees that information designated as confidential or reasonably understood to be confidential given the nature of the information and circumstances of disclosure (including but not limited to credentials, DNS records, registrar account details, and migration plans) shall be held in strict confidence and used solely to perform obligations under this Agreement. Recipient shall not disclose Confidential Information to any third party without prior written consent except to affiliates or contractors on a need-to-know basis who are subject to equivalent confidentiality obligations. The obligations of confidentiality survive termination of this Agreement for a period of three (3) years.

Representations and Warranties

Client represents that it has authority to request changes to the Current Domain and to grant Service Provider necessary access and credentials. Service Provider represents that it will perform services in a professional and workmanlike manner consistent with industry standards. Except as expressly set forth in this Agreement, the parties disclaim all other warranties, express or implied.

Limitation of Liability

Except for liability arising from gross negligence or willful misconduct, neither party shall be liable for consequential, incidental, special or punitive damages. Provider's aggregate liability for claims arising out of or related to this Agreement shall not exceed the total fees paid by Client under this Agreement for the services that gave rise to the claim.

Governing Law; Dispute Resolution

This Agreement shall be governed by and construed in accordance with the laws of the State of , without regard to conflict of law principles. The parties shall attempt in good faith to resolve disputes by negotiation. If unresolved, disputes shall be resolved in the state or federal courts located in the governing state.

Entire Agreement

This document, together with any attachments and accepted change orders, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, proposals, and communications, whether oral or written. Any amendment to this Agreement must be in writing signed by both parties.

Authorizations and Acknowledgements

By signing below, Client authorizes Service Provider to (a) access registrar and hosting accounts as necessary to implement the domain change, (b) update DNS records and coordinate TTL/propagation, and (c) obtain, install, or reissue SSL certificates as required. Client acknowledges that propagation delays, caching, and third-party approvals may affect go-live timing.

Account Credentials or Notes for Change (if required)

Acceptance

Upon completion of the tasks described in the Scope of Work, Service Provider will notify Client and Client shall have business days to identify any material issues. If Client does not object in writing within that period, the services will be deemed accepted.

Client:

By:

Date:

Service Provider:

By:

Date:

What the Domain Change Request Form Is

Domain Change Request Form is a standardized written request used to update an organization’s registered internet domain, associated DNS records, and account identifiers across internal systems and third-party services. It documents the current and requested domain names, authorization from an accountable representative, required cutover dates, and technical details such as DNS records, SSL/TLS certificate needs, and forwarding rules. The form creates an auditable record for IT, security, legal, and vendor teams to coordinate migration tasks while preserving service continuity, reducing configuration errors, and meeting compliance or contractual notification obligations.

Why a Formal Request Matters

Use this form to document authorization, technical scope, and timing for changing domain names. It centralizes approvals, reduces configuration errors, preserves audit trails for compliance, and clarifies responsibilities across IT, security, legal, and vendor teams during domain migrations or rebranding.

Who Typically Completes This Form

Typical teams and roles that complete this form include IT operations, security, and legal representatives.

IT administrators — plan DNS changes, coordinate cutover windows, update internal systems.
Security officers — review SSL/TLS, authentication, and access control impacts; approve exceptions.
Legal or compliance — verify contract notices, branding permissions, and retention rules.

Signatories should have delegated authority to authorize domain changes and confirm alignment with business and regulatory obligations.

Step-by-Step: Submitting a Domain Change Request

Follow these steps to submit and process a Domain Change Request Form through internal workflows.

01

Prepare: Collect current DNS and certificate details.
02

Complete Form: Fill all required fields and attach supporting docs.
03

Authorize: Obtain signature from delegated approver.
04

Implement: Schedule cutover and monitor post-change status.

Workflow Overview from Request to Review

This workflow describes routing a domain change request from submission through technical validation, DNS change execution, and post-implementation review.

Submit: Send form to IT and record ticket.
Validate: Verify authorization and DNS records.
Change: Apply DNS updates and update certificates.
Review: Confirm propagation and service stability.

Configuring Automated Routing and Approvals

Configure automated routing and approval rules in your ticketing system for domain change requests and notifications.

Field	Configuration
Approval Workflow	Require manager and security officer approval before changes
Notification	Email and ticket updates to stakeholders
Scheduling	Use maintenance windows and calendar invites
Rollback Plan	Define rollback steps and communication list

Platform and Integration Considerations

Verify platforms, integrations, and formats before submitting to prevent processing errors and ensure record compatibility.

Integrations: Confirm Salesforce, Google Workspace, and NetSuite links.
File formats: Accept PDF and DOCX with fillable fields.
Auth: Support SSO and MFA for admin users.

Essential Sections to Include on the Form

A professional Domain Change Request Form captures authorization, technical specifics, scheduling, and rollback plans so teams can execute migrations with clear accountability.

Authorization

Document approver name, title, and scope of authority. Include delegation evidence when approvals come from proxies to prevent disputes during implementation and specify contact information for verification.

Technical Details

List current DNS records, required A/AAAA/CNAME/TXT records, desired TTL values, MX records, and any required certificate renewals or SAN entries, and hosting provider contact details for coordination.

Schedule

Record proposed cutover date, maintenance windows, expected DNS propagation periods, rollback window, and contact availability for immediate troubleshooting including time zones and blackout dates.

Rollback

Define precise rollback steps, data reconciliation procedures, and point persons. Include estimated recovery time objective and criteria that trigger rollback activation and outline notification templates for stakeholders.

Dependencies

List third-party services, certificate authorities, CDN or load-balancer configurations, email providers, and integrations that must be updated or coordinated prior to change and include SLAs for vendor response times.

Audit Trail

Capture timestamps, signer identity, IP addresses, and a versioned record of changes. Retain logs and signed copies to support compliance reviews and post-mortem analysis for legal and operational requirements.

Security and Compliance Considerations

Encryption In Transit: TLS 1.2 and TLS 1.3

Encryption At Rest: AES-256 encryption of stored data

Certifications: SOC 2 Type II and ISO 27001

HIPAA: BAA available for covered entities

Audit Trail: Comprehensive tamper-evident audit logs

Standards: Compliant with ESIGN, UETA, 21 CFR Part 11

Risks of Incorrect or Incomplete Requests

Service Outage: User downtime and loss of access

Email Disruption: Delayed or undelivered emails

Security Exposure: Misconfigured DNS can enable spoofing

Contract Breach: Violates vendor or customer contracts

Certificate Failure: HTTPS errors and trust warnings

Regulatory Risk: HIPAA or financial compliance penalties

Common Mistakes to Avoid When Preparing the Form

Incomplete DNS records or missing MX entries cause email interruption and lengthen recovery time if not identified during validation checks.
Failing to obtain proper authority signatures leads to rejected changes and potential contractual disputes with vendors or customers.
Scheduling cutovers without accounting for DNS TTL results in unpredictable propagation and extended split-brain behavior across services and users.
Not verifying SSL/TLS certificate coverage for new hostnames causes HTTPS errors, broken integrations, and user trust issues during migration.

eSignature Vendor Pricing and Feature Snapshot

Pricing and feature snapshot comparing signNow with major eSignature vendors for domain change request eSignature needs.

	signNow	DocuSign	Adobe Sign	PandaDoc	HelloSign
Starting Price	$8/user/mo	$15/user/mo	$14/user/mo	$19/user/mo	$15/user/mo
Free Trial	7-day free trial	Varies by vendor	Varies by vendor	Varies	Varies
Bulk Send	Yes (Business Premium)	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Frequently Asked Questions and Troubleshooting

Answers to common questions about completing, submitting, and validating Domain Change Request Forms are below.

Need help? Contact support

Can I use an electronic signature for this form?
Yes. Electronic signatures are valid under the ESIGN Act (15 U.S.C. §7001) and UETA when intent, consent, signer attribution, and reliable record retention are present. For consumer-facing notices, provide ESIGN consumer disclosure when required.
Do I need a notarized signature on the form?
Not usually. Notarization is only required if internal policy, contract, or specific state law demands it. Remote online notarization may be acceptable where authorized by state law; verify state notary rules before relying on electronic notarization for authenticity.
What supporting documents should I attach?
Attach DNS export, current SSL/TLS certificate details, hosting provider contacts, vendor change agreements, and proof of authority such as corporate resolution or delegated signing authorization. Missing documentation delays approval and complicates rollback planning during migration.
How long does processing usually take?
Processing varies by organization: simple internal updates can complete within one to three business days; complex migrations requiring certificates, vendor coordination, or legal review may take several weeks. Plan for DNS propagation and certificate issuance when estimating cutover dates.
What if DNS changes break services?
Have a documented rollback plan and pre-tested configuration. Monitor DNS propagation, MX and SPF records, and certificate status immediately after change. If services degrade, trigger rollback per plan and notify stakeholders; preserve logs for root cause analysis.
Can signNow handle electronic submission and storage?
Yes. signNow supports signed form capture, audit trails, and secure storage with AES-256 at rest and TLS 1.2/1.3 in transit. SignNow offers HIPAA compliance (BAA required) and integrations with CRM and storage platforms to streamline workflows.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now