You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Seems DNS resolution on a macOS M2 Pro 2023 works differently than other apps (e.g. curl). This happens where there's a local dnsmasq and the macOS is configured to defer to it for a specific domain.
Other apps such as curl work with this setup implicitly - not sure why venom fails to pick up this configuration.
Reproduce
Setup
Setup the local dnsmasq and macOS-to-dnsmasq configuration (assuming greenstar.local is the bogus domain that only works locally):
Overview
Seems DNS resolution on a macOS M2 Pro 2023 works differently than other apps (e.g.
curl
). This happens where there's a localdnsmasq
and the macOS is configured to defer to it for a specific domain.Other apps such as
curl
work with this setup implicitly - not sure whyvenom
fails to pick up this configuration.Reproduce
Setup
Setup the local
dnsmasq
and macOS-to-dnsmasq
configuration (assuminggreenstar.local
is the bogus domain that only works locally):Reproducing it
Any idea why Venom fails on its DNS resolution, but curl does not?
The text was updated successfully, but these errors were encountered: