Add Blocker to the external plugins list #326
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Siddharth Kannan <[email protected]>
icyflame
force-pushed
the
add-blocker-explugin
branch
from
a301cc9 to
39653da
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I am the author of the
blockerCoreDNS plugin. It is a very simple plugin that can be used to block domains from being responded to by CoreDNS. I have used it mainly for blocking domains on a small home network until now.I received a request to add this to the external plugins list on the coredns.io website. I think this is a good idea, so I have made this PR to the appropriate file.
Take a look! Thank you!
Fix icyflame/blocker#3