Reverse lookup failed

[MadBoy]

Hello,

I know this problem has been responded over and over but i can't seem to fix one server only. IN error log for that server i can see: "Reverse lookup failed : 10.10.14.1 <> " while the address of the server is 10.10.16.229.

When i use connection tester on fqdn (servername.domain.corp), on wins (servername) name or on ip (10.10.16.229) every single test works fine. I tried using ping -a to verify there's no problems and there aren't. Always 10.10.16.229 is reported.

When i use tracert it says 1ms to 10.10.14.1 (my router) and 1ms to server fqdn.corp [10.10.16.229].

A bit about my infrastructure. The server with Lansweeper has address 10.10.14.250 and is in LAN, the server i want to scan is in DMZ with 10.10.16.229 (connected to WAN2 interface thru switch VLAN on my router). I have not setup firewall yet between 10.10.14.250 (Gateway 10.10.14.1) and 10.10.16.229 (Gateway 10.10.16.1) as i wanted to test lansweeper first and see if it works. So there's full connection between those two (as teh connection tester seems to get thru just fine).

Anyone can give me some ideas. Like i said the DNS seems to be working fine and resolve the ips and all preety quickly.

With regards,

MadBoy

[MadBoy]

I was waiting for 3.5 to be tested a bit more by users, but since you asked if it fixed the problem i've done the upgrade too. And.... It works!! 🙂 The server was scanned successfully. 3.5 Owns 😆

[Hemoco]

Do you have this issue also in 3.5?