Cloudflare DNS for GlobalR Domains | Nameservers, Records & Proxy | GlobalR
Switch to the old version
GLOBALR × CLOUDFLARE

Manage Your Domain With Cloudflare Through GlobalR

Your Domain in GlobalR. Cloudflare-Powered Management. One Interface.

Connect supported GlobalR domains to Cloudflare and manage DNS from your GlobalR account through a unified domain management experience.

Enable Cloudflare See How It Works Manage My Domains

Available for supported domains and integrations.

GlobalR + Cloudflare

What Does Cloudflare Add to Your Domain?

Cloudflare provides DNS and network infrastructure used to connect domains to websites, applications and other internet services.

Through the GlobalR integration, supported Cloudflare functionality can be managed directly from your GlobalR account.

DNS Management

Create and manage supported DNS records for the connected Cloudflare zone.

Network Connection

Connect your domain to Cloudflare infrastructure using the nameservers assigned to its zone.

Centralized Control

Manage your GlobalR domain and supported Cloudflare functions from one interface.

Status Monitoring

See whether Cloudflare is creating, pending nameservers, activating, active or needs attention.

Additional Cloudflare capabilities appear in GlobalR only where the current integration enables them for the account.

One workflow

Two Platforms. One Domain Workflow.

GlobalR remains the domain management interface. Cloudflare powers the connected DNS layer.

GlobalR

Domain control stays here

  • Domain registration
  • Ownership
  • Renewal
  • Contacts
  • Nameservers
  • Domain settings
example.com

One domain

Unified customer interface

Cloudflare

Connected DNS infrastructure

  • DNS zone
  • DNS records
  • Network connection
  • Proxy status where supported
  • Additional supported functionality*

Managed through GlobalR

*Only where supported by the current GlobalR integration.

Domain layer

GlobalR

Registration, renewal, ownership and domain settings stay in your GlobalR account.

DNS layer

Cloudflare

The connected zone, records and resolution run on Cloudflare infrastructure.

Service layer

Your infrastructure

Website, email, application and API destinations follow the records you manage.

Connect your domain

Connect Your Domain to Cloudflare in a Few Steps

Activation is asynchronous. GlobalR creates the zone, shows assigned nameservers, then verifies the connection through the backend.

STEP 01

Select domain

Choose a supported domain from your GlobalR account.

STEP 02

Enable Cloudflare

GlobalR creates or connects the Cloudflare zone through the backend integration.

STEP 03

Get nameservers

GlobalR displays the nameservers assigned to that Cloudflare zone.

Example only:
xxxx.ns.cloudflare.com
yyyy.ns.cloudflare.com
STEP 04

Update nameservers

The domain must use the assigned Cloudflare nameservers. Update them from GlobalR domain nameserver settings, or copy the values returned by the backend.

STEP 05

Verify connection

GlobalR checks whether Cloudflare sees the required nameservers. Status can stay pending while DNS propagates.

STEP 06

Active

When verification confirms the zone, Cloudflare is Active and supported DNS management becomes available.

Activation can require DNS/nameserver propagation and Cloudflare verification. GlobalR continues checking the connection automatically.

Why nameservers change

Why Do Nameservers Need to Change?

Nameservers tell the internet which DNS provider is authoritative for your domain. When Cloudflare DNS is enabled, the domain must use the nameservers assigned to its Cloudflare zone.

Before

Current nameservers

The domain still points at its previous DNS provider.

ns1.old-provider.com
ns2.old-provider.com

Cloudflare: not connected

After activation

Assigned Cloudflare nameservers

Values come from the GlobalR backend after the zone is created. These examples are illustrative only.

xxxx.ns.cloudflare.com
yyyy.ns.cloudflare.com

Then update the domain nameservers and wait for verification.

Manage DNS through GlobalR

Manage Cloudflare From GlobalR

When the zone is active, supported DNS records can be listed, created, updated and deleted from GlobalR. The browser talks only to the GlobalR API.

example.com Cloudflare
Active Zone connected Nameservers verified
Overview DNS Records Settings

Domain status

Domainexample.com
Registrar status Active
Cloudflare Active
DNS records12
ProxySupported for A, AAAA, CNAME
Last checkedRecently

Status values you may see

Not enabledNo zone yet
CreatingZone setup
Pending nameserversWaiting for NS
ActivatingVerification
ActiveDNS ready
Error / movedAttention required

Manage DNS records

Type Name Content Proxy TTL Action
A @ 203.0.113.10 Proxied Auto Edit
CNAME www example.com Proxied Auto Edit
MX @ mail.example.com DNS only Auto Edit
TXT @ v=spf1 … — Auto Edit
A @203.0.113.10 · Proxied · Auto
CNAME wwwexample.com · Proxied · Auto
MX @mail.example.com · DNS only · Auto
TXT @v=spf1 … · Auto

Add DNS record

Fields change with the selected type. Proxy appears only for A, AAAA and CNAME.

Preview only. Live create, edit and delete actions run in the signed-in GlobalR account against GlobalR validation rules.

DNS records you can manage

  • A — connect a hostname to IPv4. Proxy supported.
  • AAAA — connect a hostname to IPv6. Proxy supported.
  • CNAME — alias to another hostname. Proxy supported.
  • MX — mail routing, with priority. DNS only.
  • TXT — verification, SPF and other text data.
  • SRV — service discovery, with priority. DNS only.
  • CAA — certificate authority authorization.
  • NS — delegate a hostname to other nameservers.

Deleting a record asks for confirmation first. Ordinary edits do not use exaggerated warnings.

Proxy status

Choose How Traffic Reaches Your Origin

For A, AAAA and CNAME records, GlobalR can set Cloudflare proxy status. Other supported record types stay DNS only.

Proxied

Cloudflare in the path

Visitor Cloudflare Origin server

Cloudflare network sits between visitors and your origin for that hostname.

DNS only

Direct destination

Visitor DNS Origin server

Cloudflare provides DNS resolution, but traffic connects directly to the configured destination.

Why GlobalR + Cloudflare

Domain and DNS Management in One Place

One interface

Manage the domain and supported Cloudflare settings from GlobalR.

Less context switching

Avoid switching between multiple control panels for common DNS tasks.

Clear activation status

See whether the domain is creating, pending, active or needs attention.

DNS control

Create and update supported DNS records directly from your GlobalR account.

Secure integration

Secure Integration Architecture

The browser never calls Cloudflare with GlobalR credentials. Privileged Cloudflare operations stay on the GlobalR backend.

Customer
GlobalR frontend · Domain management
GlobalR API
Cloudflare integration · credentials stay here
Cloudflare API
DNS / network
Website / email / apps

The domain stays in GlobalR

Cloudflare becomes part of the domain’s infrastructure management:

  • Registration, renewal, contacts and nameservers
  • Cloudflare zone status
  • DNS records
  • Proxy status where supported
  • Settings where the integration enables them

Know when your domain is ready

Cloudflare requestedZone creation starts in GlobalR
Nameservers assignedBackend returns the zone nameservers
Waiting for nameserver changePending until the domain uses the assigned NS
Cloudflare activeSupported DNS management becomes available

Frontend displays GlobalR backend status. It does not poll Cloudflare directly. We’ll continue checking the connection automatically while the zone is pending.

Pending activation

Cloudflare setup · example.com

To activate Cloudflare, the domain must use the nameservers assigned to its zone.

xxxx.ns.cloudflare.com
yyyy.ns.cloudflare.com

Current nameservers are compared with the required Cloudflare nameservers. You can also check status from the account; GlobalR keeps verifying in the background.

If something needs attention

Errors are shown as clear account messages, without raw Cloudflare API output, internal IDs or secrets.

  • Activation failed — try again or contact support.
  • Nameservers not updated — current vs required values are shown.
  • DNS record update failed — a safe backend message is displayed.
  • Zone needs attention — the configuration should be reviewed in GlobalR.
FAQ

Frequently Asked Questions

Answers follow the current GlobalR Cloudflare integration — not the full Cloudflare product catalog.

What is the GlobalR Cloudflare integration?

It connects a supported domain in your GlobalR account to a Cloudflare DNS zone. GlobalR stores the zone, assigned nameservers and activation status, then lets you manage supported DNS records from GlobalR.

Does my domain remain registered with GlobalR?

Yes. Registration, ownership, renewal, contacts and registrar management stay with GlobalR. Cloudflare becomes the connected DNS/network layer after activation.

Do I need a separate Cloudflare account?

No. The integration uses GlobalR’s Cloudflare connection on the backend. You enable and manage supported functions from your GlobalR account.

How do I enable Cloudflare for my domain?

Sign in to GlobalR, open a supported domain and choose Enable Cloudflare. GlobalR creates or connects the zone, then shows the assigned nameservers and activation status.

Why do my nameservers need to change?

Nameservers decide which DNS provider is authoritative. Cloudflare can manage the zone only after the domain uses the nameservers assigned to that zone.

How long does Cloudflare activation take?

Activation is not instant. It depends on nameserver updates, DNS propagation and Cloudflare verification. GlobalR checks status in the background and you can also refresh status from your account. No fixed activation time is promised.

Where can I see my assigned Cloudflare nameservers?

After you enable Cloudflare, GlobalR shows the nameservers returned for that zone. Do not use generic examples from this page for a live domain.

Can I manage DNS records from GlobalR?

Yes, after the zone is in a DNS-manageable state — typically Active. You can list, create, update and delete supported records from GlobalR.

Which DNS record types are supported?

The current integration supports A, AAAA, CNAME, MX, TXT, SRV, CAA and NS. Proxy status is available for A, AAAA and CNAME only.

Can I use Cloudflare proxy mode?

Yes, for A, AAAA and CNAME records. MX, SRV, TXT, CAA and NS stay DNS only.

Can I disable Cloudflare later?

Yes. GlobalR can disable the connection after the domain no longer uses the Cloudflare nameservers. Change nameservers first, then disable Cloudflare in your account.

What happens to my DNS records if I disable Cloudflare?

Disabling removes the GlobalR Cloudflare zone connection. Records that existed only in that Cloudflare zone are no longer authoritative once the domain uses other nameservers. Plan the destination DNS before you disable.

Does GlobalR manage Cloudflare DNSSEC?

GlobalR has separate registrar DNSSEC / DS management for supported domains. That workflow is not mixed with Cloudflare DNS on this page. Use the domain DNSSEC tools and the DNS & DNSSEC guide for DS records.

What happens if Cloudflare activation fails?

GlobalR shows an error or attention-required status. You can retry the check from your account or contact support. Raw Cloudflare API errors are not exposed in the interface.

Which domain extensions support Cloudflare integration?

Availability depends on the domain in your GlobalR account and whether the integration is enabled. Not every domain is guaranteed. Open the domain in GlobalR to see if Cloudflare can be enabled.

GLOBALR × CLOUDFLARE

Connect Your Domain to Cloudflare

Manage your GlobalR domain and supported Cloudflare DNS functionality from one integrated experience.

Enable Cloudflare Manage My Domains Learn About DNS

Your domain stays in GlobalR. Cloudflare becomes part of its infrastructure management.