Learn How We Can Help You Keep Teleworkers Protected During the COVID-19 Crisis

DNS DHCP IPAM

Reply
Highlighted
Accepted Solution

When creating a Host record, why would you add a MAC address without DHCP ticked?

Guru
Posts: 188
2722     0

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?

 

 

Kindly

Wasfi

Highlighted

Re: When creating a Host record, why would you add a MAC address without DHCP ticked?

Moderator
Moderator
Posts: 148
2722     0

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.

 

Best Regards,

Bibin Thomas

Highlighted

Re: When creating a Host record, why would you add a MAC address without DHCP ticked?

Guru
Posts: 188
2723     0

Thank you Sir.

 

Kindly

Wasfi

Highlighted

Re: When creating a Host record, why would you add a MAC address without DHCP ticked?

Guru
Posts: 188
2723     0

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?

 

Kindly

Wasfi

Highlighted

Re: When creating a Host record, why would you add a MAC address without DHCP ticked?

Moderator
Moderator
Posts: 66
2723     0
As Bibin pointed out there might be free recrd that you need to ensure that it's never deleted/overwritten through a dynamic update. Adding a mac address converts the host record to complex host record. By design normal host records can be deleted, but not complex host records.

However later versions we have a feature to protect simple host records bas well.
Highlighted

Re: When creating a Host record, why would you add a MAC address without DHCP ticked?

[ Edited ]
Moderator
Moderator
Posts: 148
2723     0

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 172.0.0.10. The DC has a statically configured IP address and is never expected to contact DHCP.

Disaster - A misconfigured client named 'dc01' got an IP 172.0.0.200 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.

 

Etcetera

 

Best Regards,
Bibin Thomas

Showing results for 
Search instead for 
Do you mean 

Recommended for You