10-31-2017 08:21 PM
When creating a Host record, why would you add a MAC address without DHCP ticked? Is there a reason for adding a Host record and adding a Mac address if you don't want to add a fixed IP address?
Solved! Go to Solution.
10-31-2017 08:43 PM
Adding a Host record tied to any MAC address with/without DHCP enabled, prevents the record from being modified by dynamic DNS updates (DDNS).
However, in newer NIOS versions such as 8.x you have the ability to mark a record as 'Protected' and achieve the same result.
11-01-2017 04:06 PM
That's clear Bibin, but why would you want a record to be protected without turning it into a fixed IP? I mean without ticking the option for DHCP. Is there a real-life scenario there?
11-02-2017 02:58 AM
However later versions we have a feature to protect simple host records bas well.
11-02-2017 11:37 AM - edited 11-02-2017 11:40 AM
Let's look at a couple of examples.
1. You have a Domain Controller serving kerberos protocol for large number of clients. The DC name is dc01.example.com with IP 184.108.40.206. The DC has a statically configured IP address and is never expected to contact DHCP.
Disaster - A misconfigured client named 'dc01' got an IP 220.127.116.11 from DHCP and updated the same info into the DNS zone example.com
2. You want the name 'localhost', in your environment, to always resolve to 127.0.0.1 or something else. Any Linux clients for which an admin failed to change the name must not modify this record in DNS.
3. DHCP may not always recide on the Infoblox grid, in every environment.