I'm not sure whether I'm holding ChatGPT wrong. Whenever someone convinces me to give it another try, I ask something along the line "Generate a config file for X so that is does Y and Z". ChatGPT spits out a configuration with undocumented options. I ask back for a source for the used options. ChatGPT tells me that I'm right and those options do not exist and spits out an alternative config which is correct but completely misses the point of the original question... Then I don't use it again for a few month until another colleague tells me it got a lot better now. #ai #dnsdist config....
Recent searches
Search options
#dnsdist
1 post1 participant0 posts today
/me playing with #Grafana and #VictoriaMetrics to keep an eye at what happens to my #PowerDNS #dnsdist VPS hosted at #OpenBSD_Amsterdam. All those running on a mix of #OpenBSD and #OmniOS resources.
Continued thread
The goal was to shrink #dnsdist to fit in a CPE router, using OpenWRT on small hardware.
Continued thread
Replied in thread
@SIDNlabs Thanks for contributing to the #DNS resolution diversity.
The original part is that you use many proxies (@PowerDNS #dnsdist ) and only a few backends (@nlnetlabs #unbound ). I know by experience that both work well together (esp. with PROXYv2).
What were the advantages (practical, technical, financial) that lead to this setup?
Also, do you share cache between nodes either at the proxy or backend (cachedb)?
The DNS-collector v0.44.0 is available! The focus of this update is on maintenance to prepare future stable release
- Fixed support for IP fragments with AFPACKET sniffer.
- Major code refactoring of the base code.
- Completely redesigned the configuration checker.
https://github.com/dmachard/go-dnscollector/releases/tag/v0.44.0
GitHubRelease v0.44.0 · dmachard/go-dnscollectorWhat's Changed
If you find the project helpful, please consider supporting the project via monthly donation via GitHub Sponsors or simply add a star to this project.
Highlights
The focus of this up...
Ah bah finalement pas de #DoH3 et #DoQ pour @DNS_Shaftinc 
Je pensais que quiche, la bibliothèque de Cloudflare pour faire du Quic, était dans le tarball de #dnsdist, mais après vérif, il y a plutôt un script qui télécharge quiche et compile le truc.
Meh :/
Replied in thread
That what I did understood by reading the doc.
#PowerDNS's #DNSDist seems a superb project, just maybe a bit overhelm for what it should do in this specific case. Yet seems likely the only option, actually.
It's a bit of a shame no other #DoH #CGI have been written in compiled languages so far... which is likely why few resolver support such forwarding.
When I first read about DNS-over-HTTP, I saw it as a further centralization attempt by #Google & friends (which sadly includes @mozilla these days), since to get a working DoH service you need good sysadmin skills and a stable public IP: not something a kid with a cheap shared hosting can set up.
And ə PHP implementation would be too slow.
#FossilSCM made me realize that a simple CGI in C could have good performances and be widely distributed, so I wrote one (still early alpha).
Now I can use it in most (non enterprise managed¹) browser, but I'd like to try it system wide.
Anyway... thanks for your help guys!
Θ you know, it is always great when you report an issue and it actually gets fixed.
Like what happened today! https://github.com/PowerDNS/pdns/pull/14081
GitHubdnsdist-1.9.x: Backport 14070 - Fix DNS over plain HTTP broken by `reloadAllCertificates()` by rgacogne · Pull Request #14081 · PowerDNS/pdns
Replied in thread
The DNS-collector v0.43.0 is available! This release introduces some great features
- Compression support on DNSTap collector and logger
- Custom Flat-JSON relabeling
- New ClickHouse logger
https://github.com/dmachard/go-dnscollector/releases/tag/v0.43.0
GitHubRelease v0.43.0 · dmachard/go-dnscollectorWhat's Changed
If you find the project helpful, please consider supporting the project via monthly donation via GitHub Sponsors or simply add a star to this project.
Highlights
This release introdu...
ok #dnsdist heads! This damn console is stupid! is there a way to tie(view) a client to a domain and how much it has been served/requested/whatever?
PSA: don't update to #dnsdist 1.9.2 as it contains a crasher regression. 1.9.3 will be released soon.
The DNS-collector v0.42.0 is now available! This release introduces some important bug fixes (memory leak) and minor features.
- Fix memory leak with ElasticSearch logger, thank to @misaki-kawakami to report that.
- Optimizations to reduce CPU usage, more particularly for flat-json
- Add support for query-zone field on DNStap collector
https://github.com/dmachard/go-dnscollector/releases/tag/v0.42.0
GitHubRelease v0.42.0 · dmachard/go-dnscollectorIf you find the project helpful, please consider supporting the project via monthly donation via GitHub Sponsors or simply add a star to this project.
Highlights
This release introduces some import...