Re: [dns-operations] cmdns.dev.dns-oarc.net down?

--- Begin Message --- > On 4 Sep 2023, at 14:27, Christoph via dns-operations > wrote: > > > From: Christoph > Subject: cmdns.dev.dns-oarc.net down? > Date: 4 September 2023 at 14:27:47 CEST > To: DNS Operations > > > Hello! > > https://dnsviz.net/d/cmdns.dev.dns-oarc.net/dnssec/ > > si

Re: [dns-operations] RPZ list additions

--- Begin Message --- On 2021-08-18 22:04, Sue Steffen wrote: Can I request a domain be added to RPZ lists for distribution?  How do I go about doing that? I know of a domain which presents a website that has trademark infringement of my company.  We've sent Cease & Desist letters but the web

Re: [dns-operations] [Ext] A? ftp://netgear.routerlogin.net/shares/.

--- Begin Message --- Maybe one thing we as recursive operators could in theory do is to detect https:// & http:// & ftp:// or just :// and NXDOMAIN those queries directly instead of asking the root for something that cannot work. Is there any good reason not to? (Except maybe that in the future

[dns-operations] A? ftp://netgear.routerlogin.net/shares/.

--- Begin Message --- Just noticed while debugging why our recursive DNS platform is seeing an increase of queries for Shared with the jokers at jnj.com whose employee laptops are hammering for wks.jnj.com SOA, yeah, and of course the many thousands of companies with internal AD where they empl

Re: [dns-operations] .ag outage

--- Begin Message --- > On 20201127, at 13:40, Matthew Richardson wrote: > > DNSvis has recorded two entries for hoevelmann.ag. Whilst the latest one > looks OK, the previous one:- > > https://dnsviz.net/d/hoevelmann.ag/X8DXeQ/dnssec/ > > is showing an amount of bogusness. Apparently Afili

Re: [dns-operations] .ag outage

--- Begin Message --- > On 20201127, at 12:09, Thomas Mieslinger wrote: > > Hi, > > I received customer complaints that quad8 and some german broadband > resolvers were unable to resolve .ag secondlevel domains. Any outputs from 'dig' that show the problem? Note that all DNS for hoevalmann.a

Re: [dns-operations] [Ext] Netgear time-g.netgear.com + time-f.netgear.com - flooding....

--- Begin Message --- Yeah, they have a "funny" interface. I have two perfectly solid Netgear GS108T's for private use (read: desk switches :) and these have a "Upload" and "Download" web interface. Upload is that the device *UPLOADS* to TFTP or HTTP. Download is when the device downloads from T

Re: [dns-operations] Netgear time-g.netgear.com + time-f.netgear.com - flooding....

--- Begin Message --- TLDR: - bug from before 2013 it seems, not a malicious takeover fortunately - there is/was a software update - best to tell customers to update gear (but not everybody has proper wifi toys in house or cash... :( ) Off-list I got a few response from Jack who did some g

[dns-operations] Netgear time-g.netgear.com + time-f.netgear.com - flooding....

--- Begin Message --- So as can be seen in a short snippet of a tcpdump with the customer IP replaced with 'customer', we have had multiple customers over the last several years who run into this issue: 14:23:58.147601 IP customer.32769 > 212.60.63.246.53: 17710+ A? time-g.netgear.com. (36) 14

Re: [dns-operations] which breakage is this? FreeBSD.org / systemd-resolved

--- Begin Message --- > On 20201030, at 02:21, Phil Pennock wrote: > > On 2020-10-29 at 21:17 +0100, Jeroen Massar wrote: >> I can only first suggest starting to use 'dig', as then it also shows you >> which is the server that is answering you and it is using TCP or not, just >> in case a rando

Re: [dns-operations] which breakage is this? FreeBSD.org / systemd-resolved

--- Begin Message --- > On 20201030, at 05:29, Paul Vixie wrote: > > On Thu, Oct 29, 2020 at 09:43:28PM -0400, Viktor Dukhovni wrote: >> On Thu, Oct 29, 2020 at 09:21:56PM -0400, Phil Pennock wrote: >>> ... >>> systemd-resolved is on 127.0.0.53 as a host-local resolver, so the >>> details of tr

Re: [dns-operations] which breakage is this? FreeBSD.org / systemd-resolved

--- Begin Message --- On 2020-10-29 20:31, Phil Pennock wrote: I am so tired of dealing with systemd-resolved; I replace it on servers, but the alternatives for a roaming laptop are even buggier (in the resolver management, rather than in the actual resolver). Which breakage is this, does anyone

Re: [dns-operations] Possible issue with Office365 DNS?

--- Begin Message --- Hi Paul, One issue there is the CNAME chain. Not all recursors will actually follow that many, just in case there is a loop (e.g powerdns limits to 10) Also note https://link.springer.com/chapter/10.1007/978-3-030-00470-5_7 Seems somebody at Microsoft has the CNAME bug, de

Re: [dns-operations] QTYPEs 65 and 65479

--- Begin Message --- > On 20201001, at 16:59, Stephane Bortzmeyer wrote: > > On Wed, Sep 16, 2020 at 10:44:00AM +0100, > Roy Arends wrote > a message of 128 lines which said: > >> More info: >> >> https://mailarchive.ietf.org/arch/msg/add/MbOOWPVHRHM_wvbKhfHuzUTwimI/ >>

Re: [dns-operations] CLI Tool for DoH

--- Begin Message --- > On 20200929, at 10:47, Petr Špaček wrote: > > On 29. 09. 20 3:30, cjc+dns-o...@pumpky.net wrote: >> Looking for a command line tool to do testing of DoH. Something like >> dig or drill with DoH support. I suspect there's a Python tool or >> the like out there somewhere, b

Re: [dns-operations] peak DNS traffic increases

--- Begin Message --- On 2020-03-27 11:55, bert hubert wrote: [..] > Several of our ISP customers have informed us they are seeing >25% increases > in peak resolver DNS traffic, plus remarkable shifts in DNS access patterns. > The usual 'waves' are all gone. This increase is far bigger than the >