This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] DNS over TCP problems?
- Previous message (by thread): [atlas] DNS over TCP problems?
- Next message (by thread): [atlas] DNS over TCP problems?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Tue Mar 21 17:57:15 CET 2017
Hi Stephane, On 2017/03/21 17:25 , Stephane Bortzmeyer wrote: > 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 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
- Previous message (by thread): [atlas] DNS over TCP problems?
- Next message (by thread): [atlas] DNS over TCP problems?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]