We’re currently experiencing a high volume of support requests, which may result in longer response times — Thank you for your patience and understanding.
Community FAQ
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
ahahum
Engaged Sweeper II
I am getting the reverse lookup failed error for many of our laptops. I have scavenging setup on the DNS zones and I have verified that it is working and correctly removing old records.

At our main office we have a separate VLAN for wireless so I think the problem is coming from when the reverse lookup returns an address from the oposite VLAN it is currently active on.

All of our remote sites only have 1 VLAN so a particular computer will usually have 2 records in DNS from the same subnet...one for wired and one for wirelss. Is there any way to get around these errors on machines that have 2 different legit DNS records?

I would assume a possible solution would resolve both scenarios I am experiencing.

Thanks in advance!

Adam
1 REPLY 1
Hemoco
Lansweeper Alumni
Version 3.5 scans on FQDN by default to fix this issue, you can download the beta from the forum

Archive

This board contains archived posts from the retired Lansweeper Forum and Insiders Community.

New to Lansweeper?

Try Lansweeper For Free

Experience Lansweeper with your own data.
Sign up now for a 14-day free trial.

Try Now