Assets in Lansweeper having the DNS entry changed from the asset name to an IP followed by .ec2.inte

[dlafleur]

Hello.  Back in August of 2023, I moved my Scanning server up to AWS leaving the SQL DB on-prem.
Since migrating the server to AWS I have noticed that when scans are done on assets, some are having their DNS name in Lansweeper changed to an IP address followed by:  .ec2.internal.  Here is an example. (ip-192-168-19-20)

I'm not sure where this is coming from but it is a pain.  

Thanks
Dave LaFleur

[Katgroup]

It sounds like those IPs have reverse DNS (PTR records) with that information in your AWS environments, whereas those records did not exist in your previous environment.

[Tim_N]

Hello @dlafleur 

This is a challenging question. To start with, the first thing I think of is: which DNS server is your AWS scan server configured to use? 

I'm wondering if the AWS scan server is configured to use a DNS in AWS? You may want to try putting in a DNS server found in your on-prem environment instead. But this may also require configuring DNS traffic to come through your corporate and AWS firewalls (port 53). 

Let's confirm and try this first, run a scan, and see what results are returned. You might also want to test that the AWS scan server is able to reach and get results from the DNS server on-prem by using nslookup. (for example: nslookup (ip of target) (ip of dns server). 

Hope this gives us a little more clue(s) into what's happening.