[SERVER-35540] Attempt best effort reverse dns for ingress connections Created: 11/Jun/18  Updated: 06/Dec/22

Status: Open
Project: Core Server
Component/s: Networking
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Major - P3
Reporter: Mira Carey Assignee: Backlog - Service Architecture
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-35453 Print the IP address that the replica... Closed
Assigned Teams:
Service Arch
Participants:

 Description   

On connection accepted we print the ip address of the remote host in the logs. Any efforts we could make towards doing reverse dns would help correlate ingress and egress log lines (egress are always host and port, not resolved address).

A minimal effort might include a cache of ip address to host and port that was derived from egress connections. That would at least allow us to identify we ourselves are connecting to (like other replica set members).



 Comments   
Comment by Daniel Morilha (Inactive) [ 11/Apr/22 ]

This is a nice idea and would definitely help during issue diagnosis. With that said, it doesn't seem important at the moment. I've written a proposal to revisit Domain-name resolution where this idea could be well incorporated into. Assigning it back to the backlog user and removing from the sprint.

Comment by Lauren Lewis (Inactive) [ 02/Nov/21 ]

The Service Arch team is in the process of cleaning up tickets in the backlog. This ticket has not been updated in two years so we are closing it. Please reopen if you think this change is valuable.

Comment by Mira Carey [ 15/Jul/19 ]

Whatever we decide, we should ensure that we don't add dns resolution overload unnecessarily to operations.

Doing something asynchronously (where we load things into the cache when we see them, use it from that cache if it's there), might be a reasonable approach

Comment by Spencer Brody (Inactive) [ 13/Jun/18 ]

This would be helpful when reading log files for correlating incoming internal connections with which member of the replica set they belong to

Generated at Thu Feb 08 04:40:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.