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/[email protected]/
[dns-wg] 127.0.53.53 in logs?
- Previous message (by thread): [dns-wg] 127.0.53.53 in logs?
- Next message (by thread): [dns-wg] [ncc-services-wg] [dnsmon-user] The Beta Version of the New DNSMON is Now Available
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Stephane Bortzmeyer
bortzmeyer at nic.fr
Wed Sep 3 09:36:00 CEST 2014
On Tue, Sep 02, 2014 at 06:11:36PM -0700, David Conrad <drc at virtualized.org> wrote a message of 43 lines which said: > I was wondering if any resolver operators were seeing 127.0.53.53 in > log files. Most of it will probably be created by OARC members (or other researchers) testing the ICANN system with dig, drill or delv... > For anyone who isn’t aware, seeing that address would suggest a > “name collision” No (see above). > there was much ... ‘discussion’ about the risk associated with the > delegation of those TLDs, No, not really, it's just FUD created by people who wanted to delay the new gTLDs, plus ICANN always eager to add new rules.
- Previous message (by thread): [dns-wg] 127.0.53.53 in logs?
- Next message (by thread): [dns-wg] [ncc-services-wg] [dnsmon-user] The Beta Version of the New DNSMON is Now Available
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]