-
-
Notifications
You must be signed in to change notification settings - Fork 214
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
Comments
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. |
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. |
I added cname support in #996 |
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. |
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. |
Implemented with #1352 and included in release v0.24. |
No description provided.
The text was updated successfully, but these errors were encountered: