#2787 closed defect (duplicate)
DNS Connection for Non-exits
| Reported by: | atagar | Owned by: | |
|---|---|---|---|
| Priority: | Low | Milestone: | |
| Component: | Core Tor/Tor | Version: | |
| Severity: | Keywords: | tor-relay | |
| Cc: | Actual Points: | ||
| Parent ID: | Points: | ||
| Reviewer: | Sponsor: |
Description
Hi. When the ORPort is set Tor makes connections to the system's resolvers:
atagar@fenrir:~$ netstat -np | grep "ESTABLISHED 3776/tor"
...
tcp 0 0 10.243.55.20:49947 206.217.215.183:53 ESTABLISHED 3776/tor
udp 0 0 10.243.55.20:60630 10.128.128.128:53 ESTABLISHED 3776/tor
My understanding is that this is to provide dns resolution for exit traffic we're handling. However, these connections are made for both exiting and non-exiting relays alike. Functionally this isn't an issue, but is probably a little confusing for operators.
Am I misunderstanding the purpose for these connections? Do they serve a purpose for non-exits? I thought it was appropriate to label them as belonging to exit traffic in arm but I'll need to rethink this, lest we get some very confused non-exit operators. ;)
Cheers! -Damian
Child Tickets
Change History (3)
comment:1 Changed 8 years ago by
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
comment:2 Changed 7 years ago by
| Keywords: | tor-relay added |
|---|
comment:3 Changed 7 years ago by
| Component: | Tor Relay → Tor |
|---|
Baka, forgot that I had already encountered this issue a month back and it already has a ticket:
https://trac.torproject.org/projects/tor/ticket/965
Closing as a duplicate.