Varnish VS dnsmasq

Varnish Cache is a tool that provides a caching HTTP reverse proxy in order to accelerate your web applications. Once Varnish Cache is installed in front of any server that understands HTTP and configured to cache the contents, delivery speeds are typically enhanced by a factor of 300-1000x, depending on architecture. Kilobyte22 finds this tool along with HAProxy to be a winning combo. Source: 11 months ago

In this case, caching mechanism is situated in the proxy server or reverse proxy server like Nginx, Apache, or Varnish, and most probably it is a part of ISP (Internet Service Provider). - Source: dev.to / 12 months ago

To handle this level of traffic, you can use tools such as Varnish HTTP Cache, which caches the information of a news article starting from the first user who accesses and makes the request. Once Varnish caches the page, subsequent users will receive a response that is saved in memory. This process allows you to avoid unnecessary synchronous requests and send a quick response to users. - Source: dev.to / about 1 year ago

A couple of dedicated server-side resource caching solutions have emerged over the years: Memcached, Varnish, Squid, etc. Other solutions are less focused on web resource caching and more generic, e.g., Redis or Hazelcast. - Source: dev.to / over 1 year ago

Edge Side Includes (ESI): a more modern alternative to SSI. ESI can handle variables, have conditionals, and supports better error handling. ESI is supported by caching HTTP servers such as Varnish. - Source: dev.to / over 1 year ago

This seems like an improvement over my current solution in that it can keep multiple projects open simultaneously and route to each of them, but does add more complexity to the setup. I'm using Dnsmasq (https://thekelleys.org.uk/dnsmasq/doc.html) to map anything at .lo to the currently running project, like so:

  brew install dnsmasq.

- Source: Hacker News / 7 months ago

I would use a simple dns proxy like Blocky if you want adblocking or dnsmasq if you don't. Source: about 1 year ago

The pervious setup was much the same except the lab was under the UDMP without another gateway. I used UnifiOS to create networks(vLANs) and trusted that segregation to work. It did not. As I progressed in my home lab, I went through a few hypervisors and settled on EXSi and vSphere. 100% overkill but that is what labbing is for right? Again progressing through and adding things like windows AD and many Home... Source: over 1 year ago

If you can handle all these, then the easiest way to setup a local dev DNS is dnsmasq. You can install it via HomeBrew. Source: over 1 year ago

If you are still interested, I heartily suggest using dnsmasq to do the dhcp/tftp/PXE service. I’ve used it on airgapped networks to boot systems and install a base Linux OS or run diagnostic tools. Source: over 2 years ago