https://www.twingate.com/docs/supporting-unqualified-domain-names#troubleshooting--notes
also, according to this doc

Log into the Connector (if running on a VM) and try to look up an unqualified domain, e.g., nslookup employeeportal. If it doesn’t resolve, it will not work through Twingate.

so my nslookup api.railway.internal doesn't work

Hello,

Yep, Twingate only works with IPv4, and the private network is IPv6 only, so it just won't work unfortunately.

Perhaps you are interested in our Tailscale guide instead? -

https://docs.railway.com/tutorials/set-up-a-tailscale-subnet-router

Best,

Brody

oh, that's really sad. is there any chance you have a link to docs where they tell that twingate ipv4 only?

Here you go -

https://www.twingate.com/docs/exit-networks#why-isnt-ipv6-working

You might not be trying to use it as an Exit Node, but the same applies for all of its usecases.

thanks!