-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
Unqualified domain names #33
Unqualified domain names #33
Conversation
I also need to implement a response policy zone, can this be merged? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A sentence or two regarding this new behaviour should be addded to the README as documentation
Co-authored-by: Tom Hubrecht <Tom-Hubrecht@users.noreply.github.com>
Co-authored-by: Tom Hubrecht <Tom-Hubrecht@users.noreply.github.com>
Co-authored-by: Tom Hubrecht <Tom-Hubrecht@users.noreply.github.com>
I moved ========= Then use { dns }:
zoneAsString = dns.lib.toString "example.com" (import ./example.com.nix) { inherit dns; }; If If $ORIGIN example.com.
@ A 203.0.113.1 |
This adds a
useOrigin
option tozone
type. It is a boolean, equals tofalse
by default.By default, it changes nothing to the actual result of
toString
.If set to true, this change the
toString
behaviour to add$ORIGIN
directive, and use@
as domain name for the zone itself.writeRecord
has been patched accordingly if called with@
as zonename
.This should address #17
I had the need for a RPZ zone.