You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are handful of A, PTR, and TXT records that exist in the Route 53 zone that do not have corresponding EC2 instances.
Also, I did few spot check and noticed several A/PTR records that are orphaned (meaning, there's no EC2 instance associated). Again, I assume that these were due to the code's inability to delete the record for whatever reason. I don't have a good feel as to why that's the case.
ite.das.rm.census.gov. Zone
ip-10-191-29-64.ite.das.rm.census.gov TXT
ip-10-191-29-172.ite.das.rm.census.gov A
ip-10-191-28-97.ite.das.rm.census.gov TXT
ip-10-191-28-27.ite.das.rm.census.gov A
ip-10-191-18-62.ite.das.rm.census.gov A
ip-10-191-18-33.ite.das.rm.census.gov TXT
ip-10-191-18-112.ite.das.rm.census.gov A
Few PTR zones that I checked by hand but not comprehensive.
The text was updated successfully, but these errors were encountered:
I did some cleanup already, but yeah, we need a script to handle it. I pulled DDB entries and extracted stuff with JQ, but it may be easier to build some python for that.
Possible orphan records
ip-10-191-18-112.ite.das.rm.census.gov A Simple - 10.191.18.112
ip-10-191-18-62.ite.das.rm.census.gov A Simple - 10.191.18.62
ip-10-191-28-27.ite.das.rm.census.gov A Simple - 10.191.28.27
ip-10-191-29-79.ite.das.rm.census.gov A Simple - 10.191.29.79
There are handful of A, PTR, and TXT records that exist in the Route 53 zone that do not have corresponding EC2 instances.
Also, I did few spot check and noticed several A/PTR records that are orphaned (meaning, there's no EC2 instance associated). Again, I assume that these were due to the code's inability to delete the record for whatever reason. I don't have a good feel as to why that's the case.
ite.das.rm.census.gov. Zone
Few PTR zones that I checked by hand but not comprehensive.
The text was updated successfully, but these errors were encountered: