Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CustomDNS should support other query types (CNAME, TXT, ...) #465

Closed
0xERR0R opened this issue Mar 21, 2022 · 7 comments
Closed

CustomDNS should support other query types (CNAME, TXT, ...) #465

0xERR0R opened this issue Mar 21, 2022 · 7 comments
Labels
🔨 enhancement New feature or request
Milestone

Comments

@0xERR0R
Copy link
Owner

0xERR0R commented Mar 21, 2022

No description provided.

@0xERR0R 0xERR0R added the 🔨 enhancement New feature or request label May 25, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Aug 4, 2022

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions
Copy link
Contributor

github-actions bot commented Nov 3, 2022

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@SuperSandro2000
Copy link

I added cname support in #996

@BenMcH
Copy link
Contributor

BenMcH commented Jan 25, 2024

While the CNAME PR appears to be DOA, you can emulate CNAMEs for internal IPs using yaml anchor tags like this:

customDNS:
  customTTL: 1h
  mapping:
    home-server.lan: &server 192.168.0.1
    app-1.lan: *server
    app-2.lan: *server

This of course has its downsides and doesn't solve for external domain names, but for my use-cases this works well enough.

If I have time in the coming weeks/months, I may look at picking up where @SuperSandro2000 left off and add @0xERR0R's suggestion for psuedo-funcitons in the config file to see if we can get that merged. I know I'd prefer my apps to be CNAMEs even if this is technically functional.

@joryirving
Copy link

I saw that @BenMcH merged #1352 and I'm very thankful, but I wanted to know if there was a way to handle multiple zones in 0.24? I got one zone working wonderfully.

@kwitsch
Copy link
Collaborator

kwitsch commented May 26, 2024

Shouldn't be a problem since according to RFC1035 the master file format supports it. The commonly used name 'zone file' is a bit misleading since it supports more than just one zone.

@kwitsch kwitsch modified the milestones: future, v0.24 May 27, 2024
@kwitsch
Copy link
Collaborator

kwitsch commented May 27, 2024

Implemented with #1352 and included in release v0.24.

@kwitsch kwitsch closed this as completed May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🔨 enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants