nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community Discussions

The most recent content from our members.

Community Discussions

The most recent content from our members.

Host record vs A/PTR vs DNS scavenging (best practices)

gregbardski

Hello everyone,

we have an ongoing discussion regarding DNS db integration with IPAM. I was quite amazed when first found out about 'Host record' that unites A/AAAA/PTR/CNAME records and at the same time allow to simply enable DHCP reservation (fixed-address). Tbh it is brilliant to have one entity that transcends IPAM, DNS and DHCP

I wanted to hear your thoughts about day-to-day management of 'Host records' given the fact that they are not subject to DNS scavenging.

What kind of approach do you prefer, keeping all DNS records as Hosts, or only DHCP related as hosts, and for servers/apps keep the separation between A/PTR records, or else…?

I know it's more a phylosophical question but I'm curious about your experience in the long run.

We are in the middle of a migration to infoblox - an environment when there's plenty of DNS zones and records. There are quite a few of voices those records are stale and should have been deleted long time ago. I believe thanks to infoblox we will finally be able to say when was the last time each record was queried. 👍

P.S. Apologies if this has already been discussed for possible duplicate of the topic.

Cheers,

Greg

Find more posts tagged with

DNS

IPAM

DHCP

Tips & Tricks

Comments

Don Smith

Greg,

For Host objects, you can still use some of the criteria but you would likely want to leverage Smart Folders to help you identify which ones should be reclaimed. Because Host objects have so many other things, besides just the one DNS record, associated with them, they aren't "generally" safe for automatic reclamation.