Issue regarding logging of EDNS client subnet sent from Powerdns recursor

[Deepanjalkumar]

Issue regarding capturing of DNS request sent from Powerdns recursor via protobufServer .
I can confirm that EDNS data sent from Powerdns recursor via protobufserver is working as the data has been observed via wireshark.

[dmachard]

My bad, indeed the EDNS ClientSubnet exists in the protobuf definition.

OriginalRequestorSubnet []byte protobuf:"bytes,14,opt,name=originalRequestorSubnet" json:"originalRequestorSubnet,omitempty" // EDNS Client Subnet value (4 or 16 raw bytes in network byte order)

It will be ok for you if the original-requestor-subnet is added in the pdns section ?
By the way, can you share your recursor configuration ?

[Deepanjalkumar]

Sure here is the configuration file for Powerdns Recursor:
recursor.txt
For go-dns-collector configuration file:
config.txt

[dmachard]

Implemented in the beta release v0.22.0-beta6

I successfully tested with the following configuration

/etc/pdns-recursor/recursor.conf

ecs-add-for=0.0.0.0/0, ::/0
ecs-ipv4-bits=32
ecs-ipv4-cache-bits=32
ecs-ipv6-bits=128
ecs-ipv6-cache-bits=128v

edns-subnet-allow-list=.
use-incoming-edns-subnet=yes

local-address=0.0.0.0 ::
local-port=53

lua-config-file=/etc/pdns-recursor/recursor.lua

/etc/pdns-recursor/recursor.lua

protobufServer("192.168.1.15:6001", {exportTypes={pdns.A, pdns.AAAA, pdns.TXT}})
outgoingProtobufServer("192.168.1.15:6001", {exportTypes={pdns.A, pdns.AAAA, pdns.CNAME, pdns.NS, pdns.TXT}})

Test with dig command

dig @::1 www.google.fr +short +subnet=10.0.0.1/32

Finally in the json output, a new key is added in the pdns section

  },
  "pdns": {
    "tags": [],
    "original-request-subnet": "10.0.0.1"
  }
}

[Deepanjalkumar]

Thanks Denis. It worked and thank you once again for the quick response and feedback on the issue.