Thanks a lot Todd.
Tested and works great.
Thanks Vikrant and Todd for your suggestions. Iâll give them a try and see how it goes.
Motivation is for a temporary kludge while our Networks Team (and Active Directory DNS Team) sort out
a DNS issue within âsomeâ of our wireless VLANs.
Now that we are including laptop machines as execute nodes, many of these hook into the local on-site
wifi systems. Some are also connected directly via wired ethernet at the same time.
These laptops and wireless networks are spread over multiple sites around the country, and there seems
to be some possible firewall issues.
nslookup fails for some wireless VLANs, weirdly enough when talking to a DNS server via IPv6, but not IPv4.
A laptop in a different wireless VLAN can talk to the same DNS server via IPv6 OK.
This userâs jobs talk to a specific hostname, so jobs fail if this name is not resolved. The executable is sort
of 3rd party, so using an IP address instead will require a recompile, which could take weeks and is out of
our immediate control. His failed jobs requeue but it is affecting his overall job throughput.
So, just trying to keep a user happy while the things I have no control over get sorted out.
On 5/11/2021 10:39 PM, Hitchen, Greg (IM&T, Kensington WA) wrote: