Set Up a .com.np Domain with Cloud Hosting

By Khimananda Oli | Last reviewed: August 2026

To successfully set up a .com.np domain with cloud hosting, you must bridge the manual verification process of the Mercantile registry with modern automated infrastructure. Unlike standard gTLDs, .np domains require document validation before DNS delegation becomes active, creating a unique dependency between administrative approval and technical provisioning. This guide walks through the exact workflow I use to connect verified Nepali domains to cloud VPS environments without downtime or propagation delays.

How do you register and verify a .com.np domain before cloud hosting?

The .np namespace is managed exclusively by Mercantile Communications. You cannot purchase these domains instantly; they are free but require manual vetting. Before you can set up a .com.np domain with cloud hosting, the domain must exist in their registry with approved nameservers.

Required documentation and submission

• For individuals: Scanned copy of Nepali citizenship certificate (front and back). The domain name must match or closely relate to the applicant’s legal name.
• For organizations: Company registration certificate issued by the Office of the Company Registrar, plus a cover letter on company letterhead requesting the specific domain.
• Nameserver requirement: You must provide at least two working nameservers during application. If your cloud host isn’t ready, use temporary placeholders like ns1.example.com and update later after approval.

Submit via register.com.np. Approval typically takes 1–3 business days. There is no expedited process. Plan your migration from shared hosting to the cloud timeline around this administrative window. A common mistake is provisioning servers before domain approval, leading to idle resources and wasted spend.

How do you configure DNS for a .com.np domain on cloud infrastructure?

Once Mercantile approves your domain, the registry delegates authority to your specified nameservers. At this point, all DNS resolution depends entirely on your cloud provider’s zone configuration. Most teams use either the cloud vendor’s managed DNS (Route 53, Azure DNS, GCP Cloud DNS) or self-hosted BIND/Unbound on VPS.

Managed DNS zone setup (recommended)

1. Create a hosted zone for yourdomain.com.np in your cloud console.
2. Note the four NS records assigned by the provider (e.g., ns-123.awsdns-45.com).
3. Log back into register.com.np and update your domain’s nameservers to match exactly.
4. Add essential records:

   A     @       203.0.113.25      ; Your VPS public IP
   CNAME www     @                 ; Canonical redirect target
   TXT   @       "v=spf1 include:_spf.google.com ~all"
   MX    @       10 mail.yourdomain.com.np

5. Set TTL to 300 seconds during initial testing, then increase to 3600+ once stable.

DNS propagation for .np domains can take up to 48 hours after nameserver changes, though it often resolves within 4–6 hours globally. Use dig +trace yourdomain.com.np to verify delegation chain integrity from root → .np TLD → your authoritative NS. Never assume propagation is complete based solely on local resolver cache.

What server configuration is needed when you set up a .com.np domain with cloud hosting?

DNS only directs traffic; your server must correctly accept and serve requests for the domain. For most Nepali business applications running Laravel, Node.js, or static sites, Nginx as a reverse proxy with Let’s Encrypt SSL is the production standard. Refer to my guide on deploying Laravel on Ubuntu VPS with Nginx for framework-specific tuning.

Nginx virtual host and SSL automation

server {
    listen 80;
    server_name yourdomain.com.np www.yourdomain.com.np;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl http2;
    server_name yourdomain.com.np;
    
    ssl_certificate /etc/letsencrypt/live/yourdomain.com.np/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/yourdomain.com.np/privkey.pem;
    
    root /var/www/yourdomain.com.np/public;
    index index.php index.html;
    
    location / {
        try_files $uri $uri/ /index.php?$query_string;
    }
    
    location ~ \.php$ {
        fastcgi_pass unix:/run/php/php8.3-fpm.sock;
        fastcgi_param SCRIPT_FILENAME $realpath_root$fastcgi_script_name;
        include fastcgi_params;
    }
}

Obtain certificates after DNS fully resolves to your server IP. Run certbot --nginx -d yourdomain.com.np -d www.yourdomain.com.np. Certbot will fail if the A record hasn’t propagated or if port 80 is blocked. Always test HTTP→HTTPS redirection and HSTS headers post-installation. Automate renewal via systemd timer or cron; never rely on manual cert management in production.

Which cloud hosting option works best for .com.np domains in Nepal?

Latency, cost, compliance, and support responsiveness matter more than raw specs for Nepali audiences. While global hyperscalers work, regional considerations often favor hybrid or localized approaches. Below is a practical comparison based on deployments I’ve architected for Kathmandu-based startups and government-adjacent projects.

For public-facing consumer apps targeting Nepali users, local VPS providers offer unbeatable latency and simplify setting up a .com.np domain with cloud hosting due to pre-established Mercantile relationships. For SaaS platforms serving international clients or requiring SOC 2 / ISO 27001 alignment, AWS Mumbai provides audit-ready infrastructure with acceptable latency. Avoid hosting .np domains on US/EU regions unless legally mandated; the added latency degrades Core Web Vitals and user trust. See my analysis of best VPS and cloud hosting options for Nepali businesses for provider-specific benchmarks.

How do you troubleshoot common .com.np domain and cloud hosting issues?

Even with correct configuration, .np domains exhibit unique failure modes due to the manual registry layer. Diagnose systematically:

• No DNS resolution after approval: Verify nameservers in register.com.np dashboard match your cloud zone exactly (including trailing dots). Typos here are silent failures. Run dig NS yourdomain.com.np +short against multiple resolvers.
• SSL certificate errors: Certbot requires port 80 open and functional HTTP→HTTPS redirect. Temporarily disable firewall rules blocking 80/443 during issuance. Confirm A record points to correct IP with host yourdomain.com.np.
• Inconsistent global resolution: Some ISPs in Nepal cache .np TLD aggressively. Flush local DNS, test via external tools like DNSChecker.org, and consider lowering TTL temporarily during cutover.
• Email delivery failures: .np domains without valid SPF/DKIM are frequently rejected. Ensure TXT records propagate fully before sending transactional mail. Test with MXToolbox.

Always maintain infrastructure-as-code for DNS zones and server configs. Manual tweaks during troubleshooting create drift that breaks future audits. My Terraform practical guide covers managing .np-compatible DNS zones declaratively across providers.

Next Steps After You Set Up a .com.np Domain with Cloud Hosting

Successfully connecting your .com.np domain to cloud infrastructure is just the foundation. Production readiness demands hardened security, automated backups, observable metrics, and documented recovery procedures. Don’t stop at “it loads.” Implement UFW rate limiting, fail2ban for SSH/Nginx, daily encrypted snapshots, and Prometheus/Grafana monitoring from day one. Treat your .np domain with the same operational rigor as any global asset — its local relevance makes reliability even more critical. If you need hands-on assistance architecting or auditing your Nepali cloud deployment, reach out directly for a consultation tailored to your stack and compliance requirements.