Differences

This shows you the differences between two versions of the page.

--- infoblox:migration [2020/05/24 08:36] – created bstafford
+++ infoblox:migration [2022/11/23 12:49] (current) – external edit 127.0.0.1
@@ Line 11: / Line 11: @@
   * When importing DNS, ensure that the advanced setting of "Delete A records associated with NS records is disabled". If you do not do this, all the Microsoft DNS server A records will be removed. Thes servers will quite possibly be domain controllers which is a very bad thing.
   * If something breaks, document it and fix it until the import is clean.
-  * Search the console logs of the DHCP import for <code>"Failed: A host with IP address x.x.x.x is already configured to use MAC address xx:xx:xx:xx:xx:xx.</code> or <code>is already configured to use MAC address</code>. This indicates that there is bad data in the configuraiton (a clash of MAC addresses).
+  * Search the console logs of the DHCP import for ''"Failed: A host with IP address x.x.x.x is already configured to use MAC address xx:xx:xx:xx:xx:xx.'' or ''is already configured to use MAC address''. This indicates that there is bad data in the configuration (a clash of MAC addresses).
   * When importing DNS, make sure the Name Server Groups already exist. Set the zones to be imported to use the Name Server Groups and also the correct view (if Views are being used).
-  * Ensure Grid DHCP lease time is set to 2 hours or less to allow for rollback. Ensure that we do NOT import the TTL to ensure we inherit Grid Settings. By default, this setting is not imported.
+  * Ensure Grid DHCP lease time is set to 2 hours or less to allow for rollback. Ensure that we do NOT import the TTL to ensure we inherit Grid Settings. By default, this setting is not imported. Do not allow dotted hostnames to be left alone. You must create a proper sub-domin if you want dynamic DNS updates to work. We found that Infoblox did not apply DDNS updates when it was both DNS sever and DHCP server until we make changed the dotted hostnames into a proper subdomain. This didn't affect either Windows domain domain1.example.local or domain2.domain1.example.local.
-Do not allow dotted hostnames to be left alone. You must create a proper subdomin if you want dynamic DNS updates to work. We found that Infoblox did not apply DDNS updates when it was both DNS sever and DHCP server until we make changed the dotted hostnames into a proper subdomain. This didn't affect either Windows domain domain1.example.local or domain2.domain1.example.local.
   * After the DNS is imported, you will need to go to each zone you imported that needs Dynamic Updates from Active Directory to allow unsigned updates from all Active Directory servers.
   * When importing DHCP, if Infoblox is DNS, make sure you set DNS Name Servers in top right section to "do not import". This will cause all imported scopes to use Infoblox.
@@ Line 24: / Line 23: @@
   * When importing, make sure no one else is logged onto the Grid master.
   * If you import DNS export from Microsoft DNS servers, if you see the text string ''\302\240'', this will cause an error. It is the representation of a space in the DNS record in Microsoft.
+=====Clean Up Microsoft DNS Data=====
+When you export DNS from Microsoft, this script will add the zone file names.
+<code>awk '{n=split($3,a,"\\"); print $0, "\r\n\"DatabaseFile\"=\"" , a[3], ".expdb\"" }' dns_export.reg | sed 's/]$//g' | sed 's/"DatabaseFile"="\ /"DatabaseFile"="/g' | sed 's/] .expdb"/.expdb"/g' | sed 's/"DatabaseFile"="\ .expdb"//g' | sed '/^\s*$/d' | dos2unix > new_dns_export.reg</code>