Skip to main content

Men & Mice bulk DNS import builder

Build CSV / TSV files for the Micetro web UI bulk DNS import tool (Tools → Import DNS Records). Add, modify, and remove records of any type in one paste. Auto-detects which columns to include in the header, validates per record type, and shows the exact text ready to paste. Tested against Micetro 25.1 syntax — older versions (10.x / 11.x) use the same format.

⚠ Disclaimer This tool is provided as-is, for educational and planning purposes only. Imports should only be run on zones you are authorised to manage. Test against a non-production view or zone first — bulk DNS changes can break name resolution organisation-wide and are hard to undo at scale. Always have an export of the current zone as your rollback. The Tech Space makes no warranty and accepts no liability. Full disclaimer →

Quick start templates

Records

Hostname vs FQDN — depends on where you import Micetro treats the name field differently depending on the context you're importing from:
  • Importing inside a specific zone (DNS → zone-name → Tools → Import DNS Records): use hostname only, e.g. www or mail. Micetro appends the zone suffix automatically. Entering an FQDN like www.example.com. here creates www.example.com.example.com. — the classic double-suffix bug.
  • Importing from the whole DNS section (DNS → Tools → Import DNS Records at the top, no zone selected): use the full FQDN with trailing dot, e.g. www.example.com. Micetro routes each row to the matching zone by name.
Rule of thumb: if your URL bar shows a zone name, drop the FQDN suffix; if it shows the DNS overview, keep it.

Generated CSV Updated just now

CSV — paste into Micetro web UI 

          

        


        
        

          
How to import into Micetro

          
    
            
  1. In the Micetro web UI, navigate to DNS → either pick the target zone (use hostname-only in name) or stay at the top level to import across zones (use full FQDN with trailing dot in name).
    2. 
            
  2. Open Tools → Import DNS Records.
    3. 
            
  3. Either paste the generated CSV into the text area, or download it as .csv / .tsv and upload.
    4. 
            
  4. Choose the matching delimiter, click Import.
    5. 
            
  5. Micetro shows a preview / dry-run with errors per row. Fix any flagged rows, then commit the import.
    6. 
          

          

            Before you import
            Export the current zone as a backup. Micetro's import is transactional per row, not per file — partial imports are possible if a few rows error. Always test in a non-production view if you have one.
          

        


        
        

          
Micetro CSV reference


          

            

              
Header fields

              
    
                
  • action Add (default), Modify, Remove. Aliases: Insert/Create, Update/Change, Delete/Del. Case-insensitive.
    • 
                
  • name required. Format depends on import context — hostname only (e.g. www) when importing inside a specific zone, FQDN with trailing dot (e.g. www.example.com.) when importing from the DNS root.
    • 
                
  • type required. A, AAAA, CNAME, MX, TXT, PTR, NS, SRV, CAA, SOA, NAPTR, …
    • 
                
  • data required. IP, target, or rdata. Type-dependent.
    • 
                
  • newdata Modify only. Replacement value.
    • 
                
  • ttl Seconds (default), or with units: H, D, W, M, Y. E.g. 3600, 1H, 2D.
    • 
                
  • zone Zone name. Optional when importing within a single zone.
    • 
                
  • view DNS view name (multi-view / split-horizon setups).
    • 
                
  • authority Authority name (multi-primary setups).
    • 
                
  • forest AD forest name (multi-forest setups).
    • 
                
  • comment Optional save comment, shown in change history.
    • 
              

            


            

              
Data format by record type

              
    
                
  • A 192.0.2.1 — IPv4 address
    • 
                
  • AAAA 2001:db8::1 — IPv6 address
    • 
                
  • CNAME target.example.com. — FQDN with trailing dot
    • 
                
  • MX 10 mail.example.com. — priority + target
    • 
                
  • TXT "v=spf1 -all" — quoted string (use "" for embedded quotes)
    • 
                
  • PTR host.example.com. — FQDN with trailing dot
    • 
                
  • NS ns1.example.com. — nameserver FQDN
    • 
                
  • SRV 10 60 5060 sip.example.com. — priority weight port target
    • 
                
  • CAA 0 issue "letsencrypt.org" — flag tag value
    • 
                
  • NAPTR 100 50 "s" "SIP+D2T" "" _sip._tcp.example.com. — order pref flags service regexp replacement
    • 
              

            


            

              
Worked examples (verbatim from Micetro docs)

              
    
                
  • name,type,data
    viola.illyria.coast.,A,16.0.2.2 — simplest add
    • 
                
  • name,type,data,view
    viola.illyria.,A,16.0.2.2,first-folio — add in a specific view
    • 
                
  • action,name,type,data,newdata
    modify,viola.illyria.coast.,A,16.0.2.2,20.21.9.6 — change IP
    • 
                
  • action,name,type,data
    remove,malvolio.olivia.palace.,A,16.0.2.2 — delete
    • 
              

            


            

              
Gotchas

              
    
                
  • Trailing dots matter. www.example.com (no dot) becomes www.example.com.zone-suffix — usually wrong. Always use the absolute FQDN with trailing dot when in doubt.
    • 
                
  • Modify needs both data and newdata. The data field identifies the existing record; newdata replaces it. If only one matches, Micetro will error or no-op.
    • 
                
  • TXT values must be quoted. SPF strings like v=spf1 -all need double quotes "v=spf1 -all". Embedded quotes are doubled: "a ""b"" c".
    • 
                
  • MX / SRV data is space-separated multi-field, not multiple CSV cells. The whole thing goes in data: 10 mail.example.com.
    • 
                
  • The CSV delimiter cannot appear inside fields unquoted. If you have commas inside data (rare but possible in TXT), use TSV mode or quote the field.
    • 
                
  • The action column can be omitted if every row is an Add. Including it explicitly per row is safer for mixed batches.
    • 
              

            

          


          
Source: Micetro 25.1 — Importing DNS Records. Same format applies to 10.x / 11.x with minor field differences.

        


      

    

  


  
  
Updated