Bartek PaciaFeb 1
Stefan Eissing

Few people know that you can continue to use curl when your DNS is broken. Just add

—resolve host:port:ip-address

to your command line*.

*) Yes, that about all DNS does for you. Prettty lame, right?💁🏻‍♂️

Feb 1 at 9:21amWeb
Show thread*sigh*Ber nardFeb 1
@icing also great for circumventing DNS based security solutions (Cisco Umbrella).
Build your own "resolver" with ~/.curlrc to make it persistent.
Show threadFelix 🇨🇦 🇩🇪 🇺🇦Feb 1
@icing and you also can use this neat trick to force your request to a specific host. Very useful for testing.
Show threadNikoFeb 1
@icing this is also great for overriding what DNS gives you
Show threadOlivier MehaniFeb 1

@icing You need to make sure to keep your rollodex with site addresses up-to-date, though q:

That said, it's also great to test VHOSTS.

Show threadm_eimanFeb 1
@icing @bagder why is the port part of the parameters though? Seems like it could lead to confusion if mixing this and normal DNS…
Show threadfaxmodemFeb 1
@icing that definitely defeats my lame playing around with /etc/hosts
Show threadComrade elronxenuFeb 1
@icing Stupid dumb name resolution ...
Show threadBitHive Feb 1
@icing also good to check if your virtual host settings work if you are on your local dev machine
Show threadAmᵃᵖanda | map data witchFeb 1
@icing I use `--connect-to HOSTNAME::REALHOST:` all the time to get directly to a host in a load balancer etc.
Makes everything work with HTTPS too!
Show threadDam H.Feb 1
@icing I use it a lot with dev team to show them where they are wrong on dev platform 😅
Show threadsnowyfoxFeb 1
.
Show threadDavid SloaneFeb 1
@icing curl is amazing - I love this feature for testing and troubleshooting DNS, certificates, WAF/CDN, etc.