I know of at least two issues with our ptr record generation:
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | dcaro | T417736 Request creation of azwikimedia VPS project | |||
| Resolved | dcaro | T419582 Add floating IP and vanity domain for azwikimedia project | |||
| Resolved | Andrew | T421025 Add PTR record for azwikimedia (mail.wikimedia.az) | |||
| Resolved | Andrew | T421739 Improvements to auto-generated floating ip ptr records |
For #2, taavi points out that there is a boilerplate description for auto-created records
so it should be easy to have the daemon distinguish between manual and auto records.
Item #2 is already handled by the code. I don't know how/why my last attempt was clobbered; trying again.
OK, on the first pass the exclusion worked:
"WARNING : Did not update PTR record for 85.0-25.56.15.185.in-addr.arpa. due to lack of managed_description!"
But then after a later pass, it's gone...
Change #1264738 had a related patch set uploaded (by Andrew Bogott; author: Andrew Bogott):
[operations/puppet@production] floating_ip_updater: use project name (not id) for ptr records
Change #1264738 merged by Andrew Bogott:
[operations/puppet@production] floating_ip_updater: use project name (not id) for ptr records
Change #1270595 had a related patch set uploaded (by Andrew Bogott; author: Andrew Bogott):
[operations/puppet@production] floating_ip_updater: use project name (not id) for ptr records
Change #1270595 merged by Andrew Bogott:
[operations/puppet@production] floating_ip_updater: use project name (not id) for ptr records
#1 is fixed with attached patches
#2 was already handled; the reason I thought it wasn't was because of interactions with tofu-infra which are now also resolved.