swinog April 2020

swinog@lists.swinog.ch

5 participants
4 discussions

Init7 wins peering case against Swisscom and ComCom

by Fredy Künzler

Bundesverwaltungsgericht BVGER (Tribunal administrativ federal) decides as the court of last resort in the IP interconnection (peering) case pro Init7 and pro open and discrimination free internet. The cartel of Deutsche Telecom and Swisscom until January 2016 has been sanctioned. ComCom needs to decide about a price for cost oriented peering. Details in our press release (German only). https://drive.google.com/open?id=13nMQkj1abja-3cPBiQWiZaybsFIUkWa5 We are very happy that this case is now over. It took seven years, it all started 2012 when Swisscom tried to make us pay for peering. Besides, as ComCom is going to decide about IP peering, we believe the court order will have an impact the peering landscape beyond Switzerland. -- Fredy Künzler Init7 (Switzerland) Ltd. Technoparkstrasse 5 CH-8406 Winterthur https://www.init7.net/

2 years, 10 months

ins3.admin.ch fails with ipv6-resolution

by Tom

Hi Any dns-admin from "admin.ch" resp. "ins[123].admin.ch" here? The server "ins3.admin.ch" does not resolve over ipv6: # get the v6-address $ dig +short @127.0.0.1 aaaa ins3.admin.ch 2a00:c38:2:28:0:ffff:d467:4855 # query the v6-address for the soa record of "admin.ch" $ dig @2a00:c38:2:28:0:ffff:d467:4855 soa admin.ch ; <<>> DiG 9.16.2 <<>> @2a00:c38:2:28:0:ffff:d467:4855 soa admin.ch ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached The same result on dnsviz.net: https://dnsviz.net/d/admin.ch/XqLpPw/dnssec/ Kind regards, Tom

2 years, 11 months

Weird Bluewin Error: 'Unable to verify MX-Record for domain'

by Benoît Panizzon

Hi List Has anyone seen this error message and has a clue about the cause? ... while talking to mxbw.lb.bluewin.ch<http://mxbw.lb.bluewin.ch>.: <****(a)bluewin.ch> (reason: 550-5.1.0 MAIL FROM: <*****(a)list.scout.ch> Unable to verify MX-Record for domain list.scout.ch) list.scout.ch. 3600 IN MX 50 list.scout.ch. list.scout.ch. 3600 IN A 157.161.57.26 list.scout.ch. 3600 IN AAAA 2001:4060:dead:beef:200:e2ff:fe70:3b2f list.scout.ch. 3600 IN TXT "v=spf1 a:list.scout.ch a:akela.scout.ch a:list.scoutnet.org -all" Can't find anything wrong with the MX entry. Actually an MX is not even really necessary. -Benoît-

2 years, 11 months

IANA AS Numbers Registry Update

by Selina Harrington

Hi, The IANA AS Numbers registry has been updated to reflect the allocation of the following blocks to the RIPE NCC: 210332-211355 Assigned by RIPE NCC 2020-04-01 211356-212379 Assigned by RIPE NCC 2020-04-01 212380-213403 Assigned by RIPE NCC 2020-04-01 You can find the registry at: https://www.iana.org/assignments/as-numbers/ The allocation was made in accordance with the Policy for Allocation of ASN Blocks to Regional Internet Registries: https://www.icann.org/resources/pages/global-policy-asn-blocks-2010-09-21-en Best Regards, -- Selina Harrington Lead IANA Services Specialist

2 years, 11 months

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

swinog April 2020