DNS over TCP problems?
[I did not test it myself.]
On Tue, Mar 21, 2017 at 05:10:02PM +0100, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote a message of 204 lines which said:
[I did not test it myself.]
According to DNSmon, there is indeed a problem since 14 March: https://atlas.ripe.net/dnsmon/group/fr.?dnsmon.session.color_range_pls=0-10-10-50-100&dnsmon.session.exclude-errors=true&dnsmon.type=zone-servers&dnsmon.zone=fr.&dnsmon.maxProbes=undefined&dnsmon.startTime=1488974400&dnsmon.endTime=1490112000&dnsmon.filterProbes=false&dnsmon.ipVersion=both&dnsmon.isTcp=true
Hi Stephane, On 2017/03/21 17:25 , Stephane Bortzmeyer wrote:
According to DNSmon, there is indeed a problem since 14 March:
Unfortunately, a debug statement was left behind in the DNS over TCP code path. This was not noticed until that code was deployed on the anchors and started affecting DNSMON. The patch is simply to delete the offending line and, if all goes well, will be rolled out on the anchors in the next few days. Philip
On Tue, Mar 21, 2017 at 05:57:15PM +0100, Philip Homburg <philip.homburg@ripe.net> wrote a message of 16 lines which said:
The patch is simply to delete the offending line and, if all goes well, will be rolled out on the anchors in the next few days.
What about the other probes?
On 2017/03/21 19:10 , Stephane Bortzmeyer wrote:
On Tue, Mar 21, 2017 at 05:57:15PM +0100, Philip Homburg <philip.homburg@ripe.net> wrote a message of 16 lines which said:
The patch is simply to delete the offending line and, if all goes well, will be rolled out on the anchors in the next few days.
What about the other probes?
The other probes as soon as possible. But releasing probe firmware is a long process. So both are in progress at the moment. But it is easier to rush a release on anchors than on probes.
participants (2)
-
Philip Homburg -
Stephane Bortzmeyer