Re: [dnsdist] Logging

2019-03-19 Thread Casey Deccio
> On Mar 19, 2019, at 2:19 PM, Jonathan Reed wrote: > > Winfried provided some help to me a few months back by pointing out that the > Protobuf example code is located in the pdns repo. > https://github.com/PowerDNS/pdns/blob/master/contrib/ProtobufLogger.py >

Re: [dnsdist] Logging

2019-03-19 Thread Casey Deccio
logger)) > addCacheHitResponseAction(logged_domains, > RemoteLogResponseAction(remote_logger)) > > On Tue, Mar 19, 2019 at 5:04 PM Casey Deccio <mailto:ca...@deccio.net>> wrote: > >> On Mar 19, 2019, at 2:19 PM, Jonathan Reed > <mailto:jreed...@gmail.com>> wro

Re: [dnsdist] Logging

2019-03-21 Thread Casey Deccio
Hello again, > On Mar 19, 2019, at 2:19 PM, Jonathan Reed wrote: > > Winfried provided some help to me a few months back by pointing out that the > Protobuf example code is located in the pdns repo. > https://github.com/PowerDNS/pdns/blob/master/contrib/ProtobufLogger.py >

Re: [dnsdist] TCP FastOpen

2019-05-03 Thread Casey Deccio
> On May 2, 2019, at 3:32 PM, Casey Deccio wrote: > > > >> On May 2, 2019, at 11:35 AM, Casey Deccio wrote: >> >> Hi, >> >> I'm using dnsdist 1.1.0-2+deb9u1 on Debian. I get the following error when >> I try to enable TCP Fast Open: >

Re: [dnsdist] TCP FastOpen

2019-05-02 Thread Casey Deccio
> On May 2, 2019, at 11:35 AM, Casey Deccio wrote: > > Hi, > > I'm using dnsdist 1.1.0-2+deb9u1 on Debian. I get the following error when I > try to enable TCP Fast Open: > >> setLocal("0.0.0.0:53", { tcpFastOpenSize=100 }) > U

[dnsdist] TCP FastOpen

2019-05-02 Thread Casey Deccio
Hi, I'm using dnsdist 1.1.0-2+deb9u1 on Debian. I get the following error when I try to enable TCP Fast Open: > setLocal("0.0.0.0:53", { tcpFastOpenSize=100 }) Unable to convert parameter from no value to N5boost8optionalIbEE Any suggestions? The answer might be to upgrade, but I've got a

Re: [dnsdist] Add ECS to response

2019-07-05 Thread Casey Deccio
> On Jul 4, 2019, at 6:19 AM, Arsen STASIC wrote: > > Hi Casey, > > * Casey Deccio [2019-07-04 01:55 (-0600)]: >> >> Oh, I suppose it all depends on what you're trying to accomplish :). I think >> I've found another way to accomplish what I needed. Than

[dnsdist] Add ECS to response

2019-07-03 Thread Casey Deccio
Hello! I'm wondering if it is possible to add an arbitrary ECS value to a response. I've poked around through the docs, but it wasn't immediately clear how that might be done. I did try: addResponseAction(AllRule(), SetECSAction('0.0.0.0/0', '::/0')) But SetECSAction() is only for queries,

Re: [dnsdist] Add ECS to response

2019-07-04 Thread Casey Deccio
Hi Remi, > On Jul 4, 2019, at 1:49 AM, Remi Gacogne wrote: > > On 7/3/19 6:47 PM, Casey Deccio wrote: >> I'm wondering if it is possible to add an arbitrary ECS value to a >> response. I've poked around through the docs, but it wasn't >> immediately clear how tha

Re: [dnsdist] High-fidelity timestamp in FrameStream logging

2019-10-11 Thread Casey Deccio
> On Oct 11, 2019, at 9:59 AM, Remi Gacogne wrote: > > This seems to be a limitation of dnstap-read, we do export the > nanoseconds as defined in the dnstap format, and it looks like > dnstap-ldns [1] read them just fine: Oh, that is great news. Thank you! I knew the issue was somewhere in

Re: [dnsdist] High-fidelity timestamp in FrameStream logging

2019-10-11 Thread Casey Deccio
> On Oct 11, 2019, at 11:10 AM, Casey Deccio wrote: > >> On Oct 11, 2019, at 9:59 AM, Remi Gacogne wrote: >> >> This seems to be a limitation of dnstap-read, we do export the >> nanoseconds as defined in the dnstap format, and it looks like >> dnstap-l

[dnsdist] High-fidelity timestamp in FrameStream logging

2019-10-11 Thread Casey Deccio
Hi all, I am using the following to log queries: logger = newFrameStreamTcpLogger("127.0.0.1:4343") addAction(AllRule(), DnstapLogAction("foo", logger)) Then I use this command line to read and produce yaml output: fstrm_capture -t protobuf:dnstap.Dnstap -a 127.0.0.1 -p 4343 -w - | dnstap-read

[dnsdist] Log timestamps

2019-10-15 Thread Casey Deccio
Hello there, I have another question about logging. When I send three DNS queries in a row, all within one second, often the log messages (i.e., with DnstapLogAction("foo", logger)) show that they arrived within the same microsecond. I realize that there is some buffering going on, such that