Two different IP addresses for the DMA agent name in the DNS file

73 views
0
0 Comments

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

Jaroslaw Burtny [DevOps Member] Asked question