jdk_net tests failing on containers hosted on some dockerhost-equinix-ubuntu2004-x64-1

ref https://github.com/adoptium/infrastructure/issues/2894#issuecomment-1467953191

https://ci.adoptium.net/job/Grinder/6831/ , on [test-docker-ubuntu2204-x64-2](https://ci.adoptium.net/computer/test-docker-ubuntu2204-x64-2) the following jdk_net tests fail

```
com/sun/net/httpserver/simpleserver/CommandLinePositiveTest.java.CommandLinePositiveTest
com/sun/net/httpserver/simpleserver/jwebserver/CommandLinePositiveTest.java.CommandLinePositiveTest
java/net/InetAddress/HostsFileOrderingTest.java.HostsFileOrderingTest
java/net/InetAddress/InternalNameServiceTest.java.InternalNameServiceTest
java/net/InetAddress/InternalNameServiceWithHostsFileTest.java.InternalNameServiceWithHostsFileTest
jdk/net/ExtendedSocketOption/DontFragmentTest.java.DontFragmentTest
```

On the following containers hosted on dockerhost-equinix-ubuntu2004-x64-1 only java/net/httpclient/ManyRequestsLegacy.java.ManyRequestsLegacy fails (for jdk19)

[test-docker-ubi8-x64-1](https://ci.adoptium.net/computer/test-docker-ubi8-x64-1) https://ci.adoptium.net/job/Grinder/6840/
[test-docker-fedora35-x64-1](https://ci.adoptium.net/computer/test-docker-fedora35-x64-1) https://ci.adoptium.net/job/Grinder/6843/

Start with the linked Grinder jobs 6831, 6840, and 6843 and compare the listed jdk_net failures across the named containers. Check the referenced infrastructure issue comment for context. Done should identify the container or host-specific cause and document or implement the required infrastructure or test fix.

Written by the indexing model from the issue text.