Several test elements use JMeter properties to control their behaviour.

dhcp clients not updating dns-26

The sample results have various attributes (success/fail, elapsed time, data size etc.) and can be viewed in the various listeners.

This controller lets you send an FTP "retrieve file" or "upload file" request to an FTP server.

If you are going to send multiple requests to the same FTP server, consider using a FTP Request Defaults Configuration Element so you do not have to enter the same information for each FTP Request Generative Controller.

But since the no-refresh interval is set where it is, the lack of updates should be expected - see my answer.

Having a "No-refresh" interval configured to 7 days is intentionally blocking the periodic (24 hour) refresh by the client systems, until their record is at least 7 days old.

That configuration should be just fine - it just means that you shouldn't be worrying about a system failing to update until the timestamp on its record is over 8 days old.

In other words, don't stress about those timestamps; only stress about the refresh failing if scavenging actually kills a record for a system that's running.

I have 2 Server 2008 R2 domain controllers with a AD integrated DNS zone for the domain. I enabled scavenging a week ago and now that I am seeing old stale records go away, I am also noticing that about 80% of my DNS record timestamps arent updating properly.

From what I understand, the servers should update their own DNS records every 24 hours, but like I said, I have many that are over 24 hours old.