[metrics-team] Need record cleared or altered for t6kexit1

[Karsten Loesing]

Hi!

I start hunting down this issue and created the following ticket to
track progress:

https://trac.torproject.org/projects/tor/ticket/31941

All the best,
Karsten


On 2019-09-23 19:25, t6kexit1 wrote:
> Sure, let me lay out the IPs and RDNSs here:
> 
> So previously I was using the IP 73.95.69.17 which RDNs'd to c-73-95-69-17.hsd1.co.comcast.net. That host name is valid and resolves back to the same IP.
> 
> Recently i switched to 70.39.93.111 which RDNs to mta31.canond550.com, which does not resolve to anything.
> 
> So my theory here, is that since i switched IPs, the RDNs verifier is rejecting the new RDNs because it doesnt resolve. This is causing my old host_name RDNs to be "stuck" on my relay listing (on metrics.torproject.org) because it cant find any new valid RDNs.
> 
> Thats my theory anyways. I looked around at onionoo a bit and that was the best explanation I could come up with.
> 
> Thanks!
> 
> 
> Sent with ProtonMail Secure Email.
> 
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Monday, September 23, 2019 8:00 AM, Karsten Loesing <karsten at torproject.org> wrote:
> 
>> Hi!
>>
>> I'm not sure that I understand the issue here. In theory, Onionoo has a
>> field called unverified_host_names for "bad RDNS" cases.
>>
>> Can you be more specific? When did you change your IP address, what was
>> your old IP, what's your new IP, and what did Onionoo show as verified
>> and unverified host names before and after the change?
>>
>> Regarding possible fixes, we shouldn't start modifying records manually.
>> But if an existing Onionoo instance produces different results than,
>> say, a newly setup one, we should fix that.
>>
>> Want to create a Trac ticket for tracking this issue?
>>
>> All the best,
>> Karsten
>>
>> On 2019-09-23 15:08, t6kexit1 wrote:
>>
>>> Hello,
>>> So I recently changed my relay IP for my relay t6kexit1:
>>> https://metrics.torproject.org/rs.html#details/64186B8BCD83E31CEFCE3018334E8C7DBBD04963
>>> The host name seems to be stuck resolving to the rdns for my old (home)
>>> IP. I recently switched to a new external public IP, but the hostname
>>> record seems to be stuck. I dug around onionoo for a bit to try and
>>> figure out why that is, and I think it's stuck there because the rdns
>>> for my new IP does not actually resolve to an IP (basically a bad RDNS).
>>> My ISP for that IP does not let me change the rdns, so im assuming my
>>> home IP rDNS will be stuck there probably forever.
>>> I was wondering if I can get the record modified or just deleted (so it
>>> can regenerate again).
>>> Thanks!
>>> Sent with ProtonMail https://protonmail.com Secure Email.
>>>
>>> metrics-team mailing list
>>> metrics-team at lists.torproject.org
>>> https://lists.torproject.org/cgi-bin/mailman/listinfo/metrics-team
> 
> 
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 528 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/metrics-team/attachments/20191003/1c566716/attachment.sig>