Correcting incorrect zone value in A recs after subdomain creation.

[#1]

As part of a larger migration from another DNS system, we had tens of thousands of records living under a .local TLD internally. All of the records were dotted hostname records: foo.xyz.local and bar.aaa.local. We went about creating the subdomains to match all the dotted records with the expectation that we would be left with a .local containing only NS recs.

Lo and behold, we have about 100 A records left that have zone values set to .local and retain their original dotted hostnames. The vast majority of the A records correctly moved down to their new subdomains. The mis-domained records still work, thank goodness. I'm just wondering what would be the least-intrusive way to get these stragglers to do the right thing? They all seem to be dynamic records, but of course, plenty of dynamic ones happily-relocated to their new subdomains, so this may not be anything relevent.

Thanks

[#2]

The easiest way to correct this may be to use the CSV import feature to modify or delete and re-add these records.This allows you to export everything from the zone, modify the records in question en masse using any spreadsheet application and then using the CSV Job Manager in your Infoblox GUI, update these in one go.

To do this:

1. While in the zone in question, click on the little arrow for the export button (found in the horizontal toolbar above all the records) and select the Export data in Infoblox CSV Import Format option.
2. Click on the Export button. If prompted, save the download to the location of your choice.
3. Open the CSV file using any spreadsheet application (Excel, etc).
4. Modify the records as needed, removing all columns and rows that are not required (required columns are marked with an asterisk) and save this to a new file. Check further down for example syntax on how this will look.
5. In the toolbar on the right-hand side of the page (found on any screen under the Data Management tab), click on the CSV Job Manager button.
6. Under the CSV Import tab, click on the New CSV Import Job button.
7. Select Override and click Next.
8. Click on the Choose button and browse to the file you want to upload. In the On error section, toggle this to the Skip to the next row and continue option. Click Next.
9. Verify that the preview data looks correct and once ready, click on the Import button
10. Click Yes in the confirmation prompt.
11. Verify that the upload completes successfully. If any errors are encountered, you will be given the option to download a CSV file that will provide you with details on the errors encountered. If necessary, make any corrections required to the CSV file and attempt the import again as outlined above starting in step # 5.

Example syntax for the CSV file (when viewed using a standard text editor):

header-arecord,address*,fqdn*,_new_fqdn
arecord,1.1.1.1,record1.domain.test.local,record1.test.local

For more details regarding the CSV import process and CSV file syntax requirements, you may find the CSV Import Reference Guide useful.

Hope this helps.

-Tony

[#3 · Accepted solution]

As it turns out, the issue was that we had 2 records for each of these - one in the correct subdomain, and a zombie living outisde as a dotted hostname. Simply deleting the zombies was all I needed to do. There were about 80 of them out of 15k records that were moved from dotted hostname to subdomains.