The supplied FOSSBilling connector represents up to four nameservers through its native domain object. If the upstream domain has more than four, synchronisation reports an error instead of silently discarding the extra nameservers. Preserve the working delegation while resolving the mismatch.
IN THIS ARTICLE
01 Inspect the actual nameserver set
- Read the domain in the reseller portal or current API and record every assigned nameserver in order.
- Compare the provider's required set with the public parent delegation and the nameservers saved in FOSSBilling.
- Confirm whether the extra nameservers are intentional, such as a provider-assigned set that requires more than four hosts.
- Keep management of that complete set in the reseller portal when it cannot be represented safely in this adapter.
- If you deliberately move to a different supported DNS service, prepare and verify its full zone before changing delegation.
02 Do not trim a working delegation for display
The connector's getter checks the upstream count before filling the four native nameserver fields. Its setter also reads the four available fields. A local screen showing four values is therefore not evidence that an upstream set with more hosts can be managed completely through that screen.
Use a reviewed connector or platform enhancement if native management of larger sets is a business requirement. Do not edit the database simply to hide the sync error, and do not remove provider-assigned nameservers without checking that provider's supported delegation.
Common questions
Why does synchronization fail instead of showing the first four?
Truncation would misrepresent the registered domain and could lead to an unintended nameserver replacement. The error makes that representation limit visible.
Does the error mean the domain has stopped resolving?
Not necessarily. Query the current authoritative service and inspect public delegation. This can be a local management limitation while DNS continues to work.
Can I use only four of a provider's assigned nameservers?
Use the provider's documented required set. Do not assume an arbitrary subset is supported or provides equivalent availability.
How should support investigate?
Provide the connector and FOSSBilling versions, the full intended nameserver list and the redacted sync error. Clarify whether you need to retain that DNS provider or plan a separate migration.