namespace.basedomain.xyz cannot resolve any nameserver provided by a third-party DNS provider #404

Closed
opened 2025-12-29 01:28:19 +01:00 by adam · 2 comments
Owner

Originally created by @RealTirex on GitHub (Dec 27, 2022).

Feature request
I am using special domain for a all services of my company (basedomain.xyz). Sometimes I want to assign custom DNS, apart from the names that are provided by headscale.
For example I have a namespaces like api for all nodes, which provided a internal api of my company. I want to add these nodes, so that they can be solved with api.basedomain.xyz.

While I want to resolve namespace.basedomain.xyz for existing namespace, then headscale DNS, does not return any IP address. I checked answers for headscale vs cloudflare DNS:
dig @100.100.100.100 a namespace.basedomain.xyz return a empty A record, while dig @1.1.1.1 a namespace.basedomain.xyz return a expected A record.

For a nonnamespace.basedomain.xyz, everything worked as expected, that's why I think it's not a problem with my headscale configuration

Before I am using headscale 0.15.x, and everything worked as expected, but while I am migrated to 0.17.1, then I got above behavior.

Originally created by @RealTirex on GitHub (Dec 27, 2022). **Feature request** I am using special domain for a all services of my company (basedomain.xyz). Sometimes I want to assign custom DNS, apart from the names that are provided by headscale. For example I have a namespaces like `api` for all nodes, which provided a internal api of my company. I want to add these nodes, so that they can be solved with api.basedomain.xyz. While I want to resolve namespace.basedomain.xyz for existing namespace, then headscale DNS, does not return any IP address. I checked answers for headscale vs cloudflare DNS: `dig @100.100.100.100 a namespace.basedomain.xyz` return a empty A record, while `dig @1.1.1.1 a namespace.basedomain.xyz` return a expected A record. **For a nonnamespace.basedomain.xyz, everything worked as expected, that's why I think it's not a problem with my headscale configuration** Before I am using headscale 0.15.x, and everything worked as expected, but while I am migrated to 0.17.1, then I got above behavior.
adam added the enhancementstale labels 2025-12-29 01:28:19 +01:00
adam closed this issue 2025-12-29 01:28:19 +01:00
Author
Owner

@github-actions[bot] commented on GitHub (Sep 27, 2023):

This issue is stale because it has been open for 180 days with no activity.

@github-actions[bot] commented on GitHub (Sep 27, 2023): This issue is stale because it has been open for 180 days with no activity.
Author
Owner

@github-actions[bot] commented on GitHub (Oct 12, 2023):

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions[bot] commented on GitHub (Oct 12, 2023): This issue was closed because it has been inactive for 14 days since being marked as stale.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#404