I think it's better to check context.getRemoteAddress() first as it has been running smoothly for previous versions. Fallback tocontext.getUrl().toInetSocketAddress() when context.getRemoteAddress() is empty.

toInetSocketAddress calls InetAddress.getByName while the descriptions of https://opentelemetry.io/docs/specs/semconv/attributes-registry/network/#network-peer-address does not say anything about avoiding dns lookups https://opentelemetry.io/docs/specs/semconv/http/http-spans/ mentions that for client.address and server.address reverse DNS lookup should be avoided. Secondly when a name to ip resolution is used and there are multiple ip addresses for the same name you could end up with the wrong ip.
In my opinion you could alternative options. Perhaps it would make sense to fill client address/port and server address/port besides network.peer.address? If remote address isn't available on the server side then if it is guaranteed that the url contains an ip you could implement an overload from NetworkAttributesGetter that does not require an InetSocketAddress.