Scheduler.connect(IP_address) fails to connect to headnode

[LMuk]

Problem Description

Using the scheduler::Connect("1.2.3.4") with an IP address for a 2019 Headnode results in the following error message:

"No DNS entries exist for host machinename.2.3.4. No such host is known"

Steps to Reproduce

IScheduler scheduler = new Scheduler(); scheduler.Connect(headNodeName);

Expected Results

The scheduler connects.

Actual Results

"No DNS entries exist for host machinename.2.3.4. No such host is known"

Additonal Comments

Using machine name in the Connect() call works without issue.
Using IP results in the error containing the machine name in place of the first part of the IP address.
Connecting to 2012R2 Headnode works with IP or machine name

Changing the code to
scheduler.Connect(headNodeName, ConnectMethod.Remoting);
means we can connect to a 2019 headnode using IP.

Reporting as it feels like an issue, and an odd error message. Also do not 100% understand the implications of using of the different ConnectMethod enums and can't find enough documentation on them.

[arsdragonfly]

Could you check if the issue persists in 2019 RTM version (i.e. 6.0, available here) and 6.0.7205 SDK? This might have been caused by a change that we introduced in Update 1.