Open
Conversation
…don't have /dev/fort's ACLs.
…t you don't *have* to intercept twitter for your entire local network. Remove the twitter bind configuration that assumes you'll have a second machine serving DNS. If you do have, then you want some slave configuration at the other end, and it doesn't seem worth documenting; if you need resilience in your DNS serving, you probably know what you're doing (or should learn ;-).
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hey — I think this helps. (It should actually work now, which previously it wouldn't unless you were running all of the standard /dev/fort setup.)