Cannot create quic http/3 connection using URL

[SchoolTARMaster]

@jasnell
@nodejs

NodeJS versions: I did this in v27.0.0-pre, but it happens on any version that supports quic.
I noticed here this block of code, which was used as part of an example for an http/3 client:

const session = await connect('example.com:443', {
  // ALPN defaults to 'h3'.
  servername: 'example.com',
});
await session.opened;

If I try to call quic.connect(), whether I have the intention to use http/3 or raw quic, if I set the address parameter of the function to a URL instead of an IP address, it throws an error. But in the block of code I showed, it just uses 'example.com:443'. This can be a problem because some websites change the IP every few minutes, so then it would be mandatory to perform a DNS lookup.
Thank you

[jasnell]

The implementation currently does not perform DNS resolution of the address. It's a known limitation that is intentional for now... I wanted to focus on minimizing what additional work is happening at this layer while we figure out all the details.