Neoload keep detecting and using the incorrect DNS when performing a "server detection".
Have attempt to try what is describe in the Q&A below but it doesn't work. Please advice.
When you start a tunnel mode recording, the IP address of your NeoLoad controller will be used as DNS server.
Normally the IP address that NeoLoad is showing up in the tunnel recording panel is the NeoLoad controller IP? Is it the case here?
If no, do you have multiple IP addresses configured in your machine?
Normally, if you go to the menu “Edit-->Preferences-->HTTP recorder, you should be able to select the right IP address. What do you have on your side?
Could you describe a bit what you've done so far so i can understand better?
We have the following server / mobile handset with the corresponding IP address (the numbers are masked out for privacy) all connected in the same network segment
<nnn>.<nnn>.<nnn>.1 --> Server 1
<nnn>.<nnn>.<nnn>.2 --> Server 2 with Neoload Controller running
<nnn>.<nnn>.<nnn>.3 --> mobile handset
We followed the Neoload tutorial for mobile recording before load testing ( http://www.neotys.com/documents/doc/modules/mobile-app/en... )
It keep showing an mysterious IP <nnn>.<nnn>.<nnn>.4 as the DNS. In our network, this mysterious IP does not belongs to any devices/servers and etc.
Even ping-ing this mysterious IP, returning "Reply from <nnn>.<nnn>.<nnn>.4: Destination host unreachable."