-
-
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: add cname support #996
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #996 +/- ##
==========================================
- Coverage 93.55% 93.34% -0.21%
==========================================
Files 63 63
Lines 5323 5337 +14
==========================================
+ Hits 4980 4982 +2
- Misses 268 278 +10
- Partials 75 77 +2
☔ View full report in Codecov by Sentry. |
Is there an ETA on this by any chance? |
Thanks for your contribution and sorry for delay, I had a lot to do at work and little time for private projects. I tried your change and it works: for each rewrite entry a CNAME DNS response will be returned. I testet also with following config (from documentation): customDNS:
customTTL: 1h
filterUnmappedTypes: true
rewrite:
home: lan
replace-me.com: with-this.com
mapping:
printer.lan: 192.168.178.3
otherdevice.lan: 192.168.178.15,2001:0db8:85a3:08d3:1319:8a2e:0370:7344 DNS questions for "printer.lan" or "printer.home" return A 192.168.178.3, because the "home" part will be rewritten to "lan". But I'll also receive CNAME record for "home". It is desired? I think, using of "rewrite" section for query rewrite and CNAME records is a bit confusing, just IMHO. Maybe we should do it more explicitly, for example: customDNS:
...
mapping:
printer.lan: A(192.168.178.3)
some.domain: CNAME(example.com)
other.domain: TXT(blabla) With support for A/AAAA (default), CNAME, TXT, MX, ...? |
I am not planning to work more on this currently. |
This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days. |
This PR was closed because it has been stalled for 10 days with no activity. |
related #465