Hi All.
We are having trouble with connecting using VPN and client Cube to the DMA agents network.
Resolve-DnsName shows two different A responses (IP addresses) for dma-srv-59.XXXX.local: 10.95.2.129 10.95.2.149
This causes exactly these errors in CubeLauncher: Launcher tries to connect to the server by name, but it doesn't know which IP to use.
Sometimes it chooses an address that doesn't respond to HTTP/HTTPS requests → timeouts and SSL errors. In short: DNS splits traffic between two IPs, and CubeLauncher doesn't support multiple records for the same hostname.
PS C:\Windows\system32> Resolve-DnsName dma-srv-59.XXX.local
Name Type TTL Section IPAddress
---- ---- --- ------- ---------
dma-srv-59.XXXX.local A 1200 Answer 10.95.2.129
dma-srv-59.XXXX.local A 1200 Answer 10.95.2.149
PS C:\Windows\system32>
Why are there two address IP entries in the DNS file on a Windows domain for one name dma-srv-59.XXXX.local
My question remains: Does any DataMiner process update these entries, and do they have to be for two IP addresses?
Why are there two different IP addresses for one DAM agent name in file DNS?
Big thanks for answer.
Br.
Jarek
I'm not sure how the Launcher behaves when more than one record is returned, it could very well be just a like a browser; it choses one and tries to connect...
Having more than one DNS record is not entirely abnormal, as windows will register in the DNS active network adapters on your system under the same hostname when it can.
Just did a quick check on my local system (DMA installed) and I have two A records also. The second A record is caused by the VM on my system. I went ahead and connected to a VPN and this introduced a third A record under the same hostname.
In windows you can disable an unwanted adapter from performing DNS registration.
So in your case I wonder if you have another adapter on your system that has the secondary IP address, in which case you should be able to disable it if not needed.
Also try and run the command ipconfig /flushdns should it be you are seeing old cached records.
Its not clear if you only experience this issue when you connect through a VPN and its ok without VPN. VPNs usually introduce their own routes to the routing table
and it might be worth checking if the IPs returned by the DNS match those routes.