{"action":"opened","issue":{"url":"https://api.github.com/repos/PowerDNS/pdns/issues/8182","repository_url":"https://api.github.com/repos/PowerDNS/pdns","labels_url":"https://api.github.com/repos/PowerDNS/pdns/issues/8182/labels{/name}","comments_url":"https://api.github.com/repos/PowerDNS/pdns/issues/8182/comments","events_url":"https://api.github.com/repos/PowerDNS/pdns/issues/8182/events","html_url":"https://github.com/PowerDNS/pdns/issues/8182","id":479082723,"node_id":"MDU6SXNzdWU0NzkwODI3MjM=","number":8182,"title":"Not all valid address formats for AAAA accepted","user":{"login":"csch42","id":17472915,"node_id":"MDQ6VXNlcjE3NDcyOTE1","avatar_url":"https://avatars0.githubusercontent.com/u/17472915?v=4","gravatar_id":"","url":"https://api.github.com/users/csch42","html_url":"https://github.com/csch42","followers_url":"https://api.github.com/users/csch42/followers","following_url":"https://api.github.com/users/csch42/following{/other_user}","gists_url":"https://api.github.com/users/csch42/gists{/gist_id}","starred_url":"https://api.github.com/users/csch42/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/csch42/subscriptions","organizations_url":"https://api.github.com/users/csch42/orgs","repos_url":"https://api.github.com/users/csch42/repos","events_url":"https://api.github.com/users/csch42/events{/privacy}","received_events_url":"https://api.github.com/users/csch42/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2019-08-09T17:04:05Z","updated_at":"2019-08-09T17:04:05Z","closed_at":null,"author_association":"NONE","body":"<!-- Tell us what is issue is about -->\r\n - Program: Authoritative\r\n - Issue type: Bug report\r\n\r\n### Short description\r\n<!-- Explain in a few sentences what the issue/request is -->\r\n\r\nPDNS does not accept AAAA records in the format\r\n\r\n`2001:db8::1.2.3.4`\r\n\r\ni.e., with an embedded IPv4 address at the end, as per RFC 4291 (Section 2.2, Paragraph 3)\r\n\r\nAttempts to add such records to a zone (i.e., through the API) yield the following error:\r\n\r\n`{\"error\": \"Record foobar.example.net./AAAA '2001:db8::1.2.3.4': Invalid IPv6 address\"}`\r\n\r\nAlso: When using  `pdnsutil load-zone ...` it complains about this format, but _converts_ them anyway into \"full hex format\" addresses, i.e. 2001:db8::1.2.3.4 → 2001:db8::0102:0304\r\n\r\n### Environment\r\n<!-- Tell us about the environment -->\r\n - Operating system: Linux; Ubuntu 18.04\r\n - Software version: PowerDNS Authoritative Server 4.2.0-rc3\r\n - Software source: PowerDNS repository\r\n\r\n### Steps to reproduce\r\nAdd a record in the above format to a zone. The method doesn't matter.\r\n(I tried Opera's DNS-U and pdnsutil)\r\n\r\n### Expected behaviour\r\nIt would be nice, if PDNS would both \"eat\" this format and also _retain_ it (i.e., _not_ convert it to all-hex)\r\n\r\n### Actual behaviour\r\nAs described above. Attempts to add such a record via the API (using DNS-UI) yields the error shown above. Zone imports through pdnsutil create warnings, but import the data anyway, yet converting it to all-hex format.\r\n\r\n### Other information\r\nMy use-case: I am using NAT64 **a lot** to hide IPv4-only-speaking devices with private IPv4 addresses behind public IPv6 prefixes.\r\n\r\nThanks for all your efforts and the great _product_ PowerDNS! I very much appreciate it!\r\n(this is my first bug-report here, please excuse potential mistakes)"}}
{"actor":{"display_login":"csch42"}}