Differences

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

--- infoblox:migration [2020/08/05 10:02] – bstafford
+++ infoblox:migration [2022/11/23 12:49] (current) – external edit 127.0.0.1
@@ Line 49: / Line 49: @@
   - Update all Windows DNS servers. Disable (not set to manual) the DNS server. Shutdown BIND. Configure BIND to run on port 53 instead of 5353. Start BIND and ensure it is set to automatically start on boot. Verify the DNS fowarding is working.
   - Update all Windows Domain Controllers so that their network card interfaces have the DNS server set to the Infoblox DNS servers.
-===== Delegation =====
-Remember, if you are migrating a DNS server that has a delegation, the DNS export may not have the appropriate records and you will need to create the appropriate A records after delivery.
-For example. Supposing you have a Microsoft DNS server called ns1.mycompany.corp that is authorative for the mycompany.corp DNS zone. That DNS server may delegate the zone phones.mycompany.corp to a BIND DNS server that is not being migrated. The BIND server is, in this example, ns1.phones.mycompany.corp.
-To do this, you configure the zone mycompany.corp on the Infoblox replacement called ns2.mycompany.corp. You then create a subzone phones.mycompany.corp pointing to ns1.phones.mycompany.corp. This data may not be in the imported data from the MS server but, so long as ns2.mycompany.corp has the zone  for mycompany.corp and a delegation to ns1.phones.mycompany.corp for the zone phones.mycompany.corp, then you should see that Infoblox automatically creates the A records ns1.phones pointing at the IP you specified in the delegation setting.