Your next big idea starts with a name. Find yours
The blogDNS
THE NAMESILO BLOG

How to Connect a Custom Domain to a Cargo Portfolio

Modern SaaS illustration showing a custom domain connected to a Cargo portfolio using nameserver delegation, with registrar nameserver settings and Cargo Publish Settings for professional portfolio branding.

To connect a custom domain to a Cargo portfolio, add the domain inside your Cargo Publish Settings under "Add a Domain." Cargo's current platform uses full nameserver delegation rather than individual DNS records: update your registrar's nameservers to ns1.cargo.site and ns2.cargo.site, removing any other nameservers listed.

How Cargo's Infrastructure Handles Domain Integration

Cargo's modern platform (cargo.site) doesn't use the A-record-to-IP method many site builders rely on. Instead, it takes over DNS resolution entirely through its own nameservers.

Method

How It Works

Used By

A record

Points root domain to a static IP

Older/legacy platforms

Nameserver delegation

Hands full DNS control to the platform

Current Cargo platform

Once nameservers point to Cargo, Cargo's DNS editor becomes the single place where all your domain's records live, including MX and TXT records for existing email. Cargo maintains these automatically during the switch.

Why It Matters: Matching Agency Submission Standards

Portfolio sites on a .cargo.site subdomain read as unfinished to art directors and commercial clients reviewing submissions. A dedicated .com or .studio domain signals a working professional, not a student project. For artists competing for commissions, the domain is part of the first impression, often before a single image loads.

Important: Once nameservers point to Cargo, NameSilo's DNS Manager no longer controls your domain. Any future DNS record (a subdomain, an email service, a verification TXT record) must be added inside Cargo's own Edit DNS tool, not at NameSilo. Records added at NameSilo after the switch have no effect.

To reach it: Workspace → Account Settings → Domain Names → "···" icon next to your domain → Edit DNS. Supported record types include A, CNAME, MX, TXT, SRV, ANAME, SPF, and HTTPRED.

Sourcing the Correct Nameservers

Before touching your registrar, confirm two things inside Cargo:

Step 1: Confirm your site has an active Site Upgrade. A personal domain connection requires a paid Cargo plan; free tier sites cannot use a custom domain.

Step 2: In your Cargo admin, go to Publish Settings → Add a Domain → Use an Existing Domain, and enter your domain exactly as you'll type it later (e.g., yourname.com).

Cargo will display the required nameservers: ns1.cargo.site and ns2.cargo.site. These are fixed values and do not vary by account.

Implementation Phase: Updating Nameservers at NameSilo

Step 1: Log into your NameSilo account and go to Domain Manager.

Step 2: Select your domain and click "Change Nameservers"..

Step 3: Remove NameSilo's default nameservers and enter:

  • ns1.cargo.site
  • ns2.cargo.site

Step 4: Save changes. Propagation typically takes a few hours, though it can take up to 24-48 hours globally.

Step 5: Return to Cargo and confirm the domain shows as connected. If you use email at this domain, verify MX records appear correctly in Cargo's Edit DNS tool after the switch.

Common Mistakes

Adding DNS records at NameSilo after the switch: The most common point of confusion. Once Cargo's nameservers are active, records added in NameSilo's DNS Manager are invisible to visitors. All future changes belong in Cargo's Edit DNS tool.

Leaving old nameservers or A records active alongside Cargo's: Partial configurations cause the domain to resolve inconsistently, sometimes showing your old host, sometimes Cargo.

Skipping the Site Upgrade check: Entering a domain without an active paid plan fails silently or prompts an upgrade requirement.

What This Means for You

NameSilo makes nameserver changes straightforward from Domain Manager, letting Cargo take over DNS cleanly. If you need a domain for your portfolio, search available names and compare pricing across extensions like .com, .studio, and .art.

Frequently Asked Questions

Does Cargo Collective charge extra to use a custom domain? 

Yes. Custom domains require an active Cargo Site Upgrade.

What are the IP targets for Cargo site setup?

Cargo's current platform uses nameservers, not IP-based A records.

Why is my Cargo portfolio showing an invalid domain error? 

Nameservers may not have fully propagated, or one is misconfigured.

Can I use a custom subdomain with a Cargo site? 

Yes, via a CNAME record added in Cargo's Edit DNS tool.

How long does a Cargo domain connection take to propagate? 

Typically a few hours, up to 48 hours in some cases.

Do I need separate web hosting for Cargo? 

No. Cargo hosts your site; you only need a registered domain.

How do I fix SSL errors on my Cargo layout? Confirm nameservers are fully propagated; SSL issues automatically after.

Does NameSilo work with Cargo Collective? 

Yes. Update nameservers to Cargo's values from NameSilo's Domain Manager.

WRITTEN BY

NameSilo Staff

The NameSilo staff of writers worked together on this post. It was a combination of efforts from our passionate writers that produce content to educate and provide insights for all our readers.