Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Wiki Replica
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
The Tor Project
TPA
Wiki Replica
Commits
3c60c970
Unverified
Commit
3c60c970
authored
4 years ago
by
anarcat
Browse files
Options
Downloads
Patches
Plain Diff
expand the reverse DNS documentation
parent
bef9b4fc
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
howto/new-machine.md
+39
-1
39 additions, 1 deletion
howto/new-machine.md
with
39 additions
and
1 deletion
howto/new-machine.md
+
39
−
1
View file @
3c60c970
...
...
@@ -83,8 +83,46 @@ taken by the installer:
... where `$SUBNET` is the (known) subnet from the upstream
provider and `$MAC` is the MAC address as found in `ip link show
up`.
4.
ensure reverse DNS is set for the machine. this can be done either
in the upstream configuration dashboard (e.g. Hetzner) or in our
zone files, in the
`dns/domains.git`
repository.
Pro tip: `dig -x` will show you an SOA record pointing at the
authoritative DNS server for the relevant zone, and will even show
you the right record to create. Since IPv6 records are
particularly painful to create, you should use this all the time.
For example, the IP addresses of `chi-node-01` are `38.229.82.104`
and `2604:8800:5000:82:baca:3aff:fe5d:8774`, so the records to
create are:
$ dig -x 2604:8800:5000:82:baca:3aff:fe5d:8774 38.229.82.104
[...]
;; QUESTION SECTION:
;4.7.7.8.d.5.e.f.f.f.a.3.a.c.a.b.2.8.0.0.0.0.0.5.0.0.8.8.4.0.6.2.ip6.arpa. IN PTR
;; AUTHORITY SECTION:
2.8.0.0.0.0.0.5.0.0.8.8.4.0.6.2.ip6.arpa. 3552 IN SOA nevii.torproject.org. hostmaster.torproject.org. 2021020201 10800 3600 1814400 3601
[...]
;; QUESTION SECTION:
;104.82.229.38.in-addr.arpa. IN PTR
;; AUTHORITY SECTION:
82.229.38.in-addr.arpa. 2991 IN SOA ns1.cymru.com. noc.cymru.com. 2020110201 21600 3600 604800 7200
[...]
In this case, you should add this record to
`82.229.38.in-addr.arpa.`:
104.82.229.38.in-addr.arpa. IN PTR chi-node-01.torproject.org.
And this to `2.8.0.0.0.0.0.5.0.0.8.8.4.0.6.2.ip6.arpa.`:
Make sure reverse DNS is correct as well
.
4.7.7.8.d.5.e.f.f.f.a.3.a.c.a.b.2.8.0.0.0.0.0.5.0.0.8.8.4.0.6.2.ip6.arpa. IN PTR chi-node-01.torproject.org
.
4.
the machine has a short hostname (e.g.
`test`
) which resolves to a
fully qualified domain name (e.g.
`test.torproject.org`
) in the
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment