{"action":"opened","issue":{"url":"https://api.github.com/repos/ElementalAlchemist/txircd/issues/159","repository_url":"https://api.github.com/repos/ElementalAlchemist/txircd","labels_url":"https://api.github.com/repos/ElementalAlchemist/txircd/issues/159/labels{/name}","comments_url":"https://api.github.com/repos/ElementalAlchemist/txircd/issues/159/comments","events_url":"https://api.github.com/repos/ElementalAlchemist/txircd/issues/159/events","html_url":"https://github.com/ElementalAlchemist/txircd/issues/159","id":327672513,"number":159,"title":"User hostname lookup fails if both AAAA and A DNS records exist for a hostname","user":{"login":"HubbeKing","id":1328601,"avatar_url":"https://avatars1.githubusercontent.com/u/1328601?v=4","gravatar_id":"","url":"https://api.github.com/users/HubbeKing","html_url":"https://github.com/HubbeKing","followers_url":"https://api.github.com/users/HubbeKing/followers","following_url":"https://api.github.com/users/HubbeKing/following{/other_user}","gists_url":"https://api.github.com/users/HubbeKing/gists{/gist_id}","starred_url":"https://api.github.com/users/HubbeKing/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/HubbeKing/subscriptions","organizations_url":"https://api.github.com/users/HubbeKing/orgs","repos_url":"https://api.github.com/users/HubbeKing/repos","events_url":"https://api.github.com/users/HubbeKing/events{/privacy}","received_events_url":"https://api.github.com/users/HubbeKing/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-05-30T10:37:07Z","updated_at":"2018-05-30T10:37:07Z","closed_at":null,"author_association":"NONE","body":"When I migrated my server from Vultr to DigitalOcean I also started managing my domain's DNS records through DigitalOcean, and added both AAAA and A records for the same hostname.\r\n\r\nThis meant that a DNS lookup on hubbe.club returned both an IPv6 and an IPv4 address.\r\nHowever, txircd apparently got confused by this, and where I used to be properly detected as hubbe@hubbe.club, I was now hubbe@<IPv4 IP> instead.\r\n\r\nRemoving the AAAA record for hubbe.club resolved the issue, and I was now properly signed on as hubbe@hubbe.club again.\r\n\r\nThus, it seems that txircd somehow gets confused during hostname resolution if it finds both an IPv6 and an IPv4 address for the same hostname.\r\n\r\nHad StarlitGhost test the same thing, and she is now also properly detected as SG@starlitghost.xyz, after having removed her AAAA record for starlitghost.xyz\r\n\r\nUnsure if this is only an issue with DigitalOcean's DNS nameservers, or if it's also a problem with other providers. Should be easy to test if that's the case, since having both A and AAAA records for the same domain/hostname is fairly common."}}
{"actor":{"display_login":"HubbeKing"}}