(dnscache role) rm site specific override of dns::forwarders #611
Conversation
This file contains 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
It is unknown why the tu site was not using 1.1.1.1 as a forwarder as
cp,dev,ls do. Perhaps there was an access restriction on 1.1.1.1 in the
past? There is no current issue with accessing 1.1.1.1 from
dns1.tu.lsst.org. E.g.:
[jhoblitt@dns1 ~]$ dig +short google.com @1.0.0.1
142.250.68.46
[jhoblitt@dns1 ~]$ dig +short google.com @1.1.1.1
142.250.72.142
[jhoblitt@dns1 ~]$ dig +short google.com @8.8.8.8
142.251.46.142
cbarria
approved these changes
Jul 29, 2022
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.
It is unknown why the tu site was not using 1.1.1.1 as a forwarder as
cp,dev,ls do. Perhaps there was an access restriction on 1.1.1.1 in the
past? There is no current issue with accessing 1.1.1.1 from
dns1.tu.lsst.org. E.g.: