Baike.dev
All toolsAI codingTrendingOpen sourceNewsSubmit
Log in
Back to tool/Back to issues
#950·go

Cannot create hostnames (glue records) via GoDaddy API - UI works but API blocked

Author: saifkhan2kCreated Feb 12, 2026Updated Feb 12, 2026

I’m trying to automate domain provisioning using GoDaddy API.

I can successfully update nameservers via:

PATCH /v1/domains/{domain}

But hostname (glue) creation fails:

POST /v1/domains/{domain}/hosts - 404
PATCH /v1/domains/{domain}/records - 422

Even after:

  • Forcing default GoDaddy nameservers (ns01/ns02.domaincontrol.com)
  • Waiting 30+ minutes
  • Retrying API

However, the SAME hostname creation works instantly in GoDaddy UI:

ns1.example.com → IP
ns2.example.com → IP

After manually creating hostnames in UI, API allows setting nameservers.

So effectively:

  • NS change via API works
  • Hostname creation via API blocked
  • UI hostname creation works

This blocks full automation.

Questions:

  1. Is glue/hostname creation restricted by account tier?
  2. Is there any way to enable it via API?
  3. Is there a supported automation workaround?

Environment:

  • GoDaddy REST API v1
  • .com domains
  • Portfolio / reseller style account
  • Auth via sso-key

Expected: If hostname creation is allowed in UI, it should also be allowed via API, or at least return clear permission errors instead of 404/422.

Source: godaddy-wordpress/go

View original on GitHubView discussion on GitHub