swinog

swinog@lists.swinog.ch

1 participants
2916 discussions

DNSSEC issue with swizzonic DNS servers?
by Benoit Panizzon 06 Jan '23

06 Jan '23

Hi List Fancy another DNS issue hunt? We have DNSSEC validation enabled on our BIND DNS Servers. We started seeing: no valid RRSIG resolving 'www.numberportability.ch/DS/IN': 2a01:8100:2901::1:183:202#53 no valid RRSIG resolving 'www.numberportability.ch/DS/IN': 2a01:8100:2901::1:183:201#53 no valid RRSIG resolving 'www.numberportability.ch/DS/IN': 81.88.58.219#53 no valid RRSIG resolving 'www.numberportability.ch/DS/IN': 195.110.124.196#53 broken trust chain resolving 'www.numberportability.ch/HTTPS/IN': 2a01:8100:2901::1:183:202#53 broken trust chain resolving 'www.numberportability.ch/AAAA/IN': 2a01:8100:2901::1:183:202#53 client @0x803541d60 X.X.X.X#27325 (www.numberportability.ch): query failed (broken trust chain) for www.numberportability.ch/IN/AAAA at query.c:7724 And of course the query fails, disrupting access some some quite important API. numberportability.ch. 900 IN SOA dns1.swizzonic.ch. hostmaster.swizzonic.ch. 2022121601 10800 3600 604800 86400 $ dig +dnssec RRSIG www.numberportability.ch @dns1.swizzonic.ch ; <<>> DiG 9.16.33-Debian <<>> +dnssec RRSIG www.numberportability.ch @dns1.swizzonic.ch ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 39132 ;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; WARNING: recursion requested but not available So, from my point of view, the authoritative DNS server thinks, this is a recursive query and refuses to answer with the RRSIG, breaking validation of that record. Do you get to the same conclusion? Can you resolve this host via any other DNSSEC validating nameserver? I had no success contacting any technical inclined staff willing to look at the issue since the issue started on 16. December via hostmaster(a)swizzonic.ch by phone or via support(a)register.it. So if anyone from Swizzonic is reading here, it would be nice to get a direct contact to further investigate that issue. Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

8 9

Reach Swizzonic Support outside of working hours
by lizzy＠hennig.ch 05 Jan '23

05 Jan '23

Does someone know a way to reach Swizzonic outside their working hours? A Domain of us got deactivated in the evening outside their working hours, event though the bill is paid and wouldn't be due yet. Said domain is used for our dns servers we use for customer...

4 3

urgent swizzonic problem
by Peter Blaser 29 Dec '22

29 Dec '22

Somebody from Swizzonic here ? Please contact me offline Does somebody knows how to contact swizzonic off business hours ?

2 1

DNS contact at Sunrise needed
by Filip Hruška 15 Dec '22

15 Dec '22

Hi there, We are seeing some DNS resolution issues for a specific domain through Sunrise's recursors specifically. Does anyone perhaps have a contact at Sunrise that could be helpful with debugging this please? Already tried normal contact methods listed in PeeringDB etc and have been ignored or told that they don't help non-customers. Regards, Filip

1 0

How to destroy data effectively?
by Martin Ebnoether 07 Dec '22

07 Dec '22

Hi all. As some of you know, I work at a money laund... financial company. Some time ago, the question arose, how to effectively destroy data safely and securely in an easy way? How does your company deal with hard disks (or any media) that needs to be decommissioned? Do you just dd a few times over it? Or rather let a professional company shred your media to little bits? CU, Venty -- 10 PRINT "BASIC programmers don't die." 20 PRINT "They just GOSUB without RETURN." 30 END READY.

11 11

Anyone else having email issues with Metanet?
by Benoît Panizzon 02 Dec '22

02 Dec '22

Hi List Yes, I am already in contact with Metanet techs. We have a very strange issue with two of their email servers. Connecting to Port 25 starts fine. SYN, SYN-ACK but then we start seeing re-transmits until the connections times out. This first happened to one of their server, then to another one, the the first server became reachable again at the beginning of this week, the second one still causes the same problem. The Problem also occurs the other way round. Metanet is unable to establish tcp connection to port 25 on rrmx.imp.ch Is anyone else seeing such an issue, either to metanet or towards our rrmx.imp.ch? Has anyone any clue what could cause such an issue? I compared traces of tcp connections to both of the affected metanet servers, to the working one and to the one causing re-transmits. The two initial SYN and SYN-ACK look identical and then to one destination the re-transmits start and to the other destination I get the SMTP HELO banner. PS: Yes, I did disable the firewall on our mail-plattform and re-test. This does not seem to be the cause. -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

1 0

Sudden RTT drops after changing fiber OTO plug
by Mat Kowalski 29 Nov '22

29 Nov '22

Hi folks, This is mostly to satisfy my curiosity, but if someone has technical insights I would be more than happy to hear. Background - yesterday my residential Sunrise fiber has changed the OTO plug from #1 to #2 (in Zurich). It's still XGS-PON, it's just that I'm using a different line now. I have a setup that runs a continuous ICMP test towards various targets. I have observed that after changing the fiber plug, all the RTTs suddenly dropped. My guess (may be wrong though) is that with OTO#1 I was connected to a more complex PoP setup than with OTO#2 and this is what reduced the RTT. For interested, here are 3 graphs presenting the drop. For every graph the left side is OTO#1 and the right is OTO#2. Monday morning was the time of changing the line: 1) https://i.ibb.co/qRL1Hyb/1.png 2) https://i.ibb.co/9ZL60KB/2.png 3) https://i.ibb.co/k2YJzJL/3.png Cheers, Mat

3 3

Buried alive in switzerland (long and painfull swiss intel hiccup)
by Catseye Chandra 25 Nov '22

25 Nov '22

Hello swinogers, Here's an update with my swiss intel affair in the field of telecoms. The feds are using IME/TrustZone for "étouffe, écrase d'affaire". I've had a supposed economical warfare act using the latest wifi hole in the linux kernel of mid october, an infiltration using IME on macOS deleting some files and modifying my OCaml compiler, all to prevent information leak about it. BE FRIGHTENED THE ROTTEN COPS ARE REALLY REALLY STRONG IN THIS COUNTRY BWAHAHAHHAAHHH! (do like me, go tell them to fuck off and you'll get a job change for FREE :) It's in french on my website - Google translate is your friend -- Version html disponible sur: http://www.strauss-engineering.ch/posts/sevices.html A noter que je n'ai, matériellement parlant, plus rien. Je vis désormais dans un établissement psycho-social médicalisé, à l'assurance invalidité, poussé par la force des choses, de loin pas par maladie mentale. Mon réseau de relation amicale ne compte plus qu'un à deux amis. 48 ans, pas de femme, pas de gosses, ce contre mon gré aussi. La plus grande partie de mon réseau de relation, essentiellement passé donc, est "réseauté" de manière sécuritaire. Le contact avec mes amis informaticiens m'est factuellement interdit. Le monde des avocats aussi, réseauté activement sur mes traces électroniques (emails, appels téléphoniques). 160 avocats contacté par email, 40 par lettres papier, 6 de visu ou par téléphone, réponses toujours négatives. Etouffe complète, à 100%, en tout cas tentative. Je n'ai jamais détenu le moindre secret, sauf les mots de passe de mon informatique. Aussi je coûte mensuellement plus de 7000.- par mois à la communauté, sans compter, sans connaître le budget de l'étouffe de cette affaire dans laquel je n'ai rien à voir. Probable jeux d'information fallacieux de la part d'enrôlés dans les télécoms il y a de cela plus de 20 ans en arrière. Je demande 3.5mio CHF net d'impôts comme réparation, probablement que l'enveloppe globale concernant l'étouffe de cette affaire est bien plus élevé. Constament des tentatives de petits roquets, petits rats de hiérarchie sécuritaire de me mettre dans une colère noir, afin que j'invective par email, aussi autour de moi voire que j'en arrive aux mains. 3 ans de lavage de cerveau, 3 ans de dépression abyssale, 14 ans de planche à savon, 20 ans à revenir à une forme normale. Pour rien, strictement rien, je n'ai jamais mis les pieds dans un central téléphonique (génération internet). Aussi google semble avoir été contacté afin de retourner très peu de résultat provenant de mon site web. Ne vous gênez pas de communiquer à ce sujet autour de vous. Salutations.

1 0

Fwd: [NLNOG] Voorkom AS-set namespace collisions. AS-A2B vs AS51088:AS-A2B // AS-SET Squatting
by Arnold Nipper 22 Nov '22

22 Nov '22

[ h/t Erik Bais ... helemaal bedankt, Erik! ] Erik hat eine einfache Anleitung, um AS-SET Squatting zu umgehen bzw. auf hierarchische AS-SET zu wechseln * Erstelle einen neuen AS-Set-Namen .. der mit der eigenen AS-Nummer beginnt .... ASNUMBER:<alter AS-Set-Name> * Kopiere alle Informationen darin, die auch im aktuellen (Short) AS-Set enthalten sind * Speichern und überprüfe es in der RIPE DB * Im alten AS-Set .. trägst du eine Referenz ein .. und lässt den Rest leer .. Du bekommst also nur eine Zeile mit Mitgliedern: ASNUMBER:<alter AS-Set-Name> * benachrichtige alle Peers und ändere auch den Eintrag in PeerinDB etc. Viele Grüße Arnold P.S.: Siehe auch https://www.ripe.net/ripe/mail/archives/routing-wg/2022-November/004649.html ff -------- Weitergeleitete Nachricht -------- Betreff: [NLNOG] Voorkom AS-set namespace collisions. AS-A2B vs AS51088:AS-A2B Datum: Fri, 18 Nov 2022 13:02:28 +0000 Von: Erik Bais <erik(a)bais.name> An: nlnog(a)nlnog.net <nlnog(a)nlnog.net> Ollah, Er loopt momenteel bij de RIPE Database Working group ( DB-WG ) een discussie <https://www.ripe.net/ripe/mail/archives/db-wg/2022-November/007646.html> waarbij de AS-Set name misbruikt kan worden, omdat de normale short notatie zoals ( AS-A2B ) bij het aanmaken van een ‘nieuwe’ short as name, geen authorisatie vereist in referentie naar een origineel of naar een eigenaar van een netwerk. Nu is er een optie om je AS nummer als authorisatie te gebruiken .. en dan moet je dus je AS set naam aanpassen .. in <ASnummer>:<AS-set naam> Dit is al misbruikt in de afgelopen weken.. waarbij een of andere leukerd in de RIPE Database een AS-Set aangemaakt had met een naam AS-<grote cloud provider> .. Aangezien hun normaal hun AS-Set bij een andere database bijhielden, hadden ze hierdoor opeens een AS-Set name collission .. met als resultaat .. dat alle partijen die bijvoorbeeld bgpq4 gebruiken om de prefixfilters te maken, een lege prefixfilter als resultaat set kregen .. omdat ze tegen de lege AS set in de RIPE db aanliepen ..en daarna exit. Het is dus sterk aan te raden om de ‘long’ AS-Set notatie te gaan gebruiken voor je eigen (en je klanten) hun bereikbaarheid. Wat je nu binnen een paar minuten kan doen is: Creëer een nieuwe AS-Set naam .. die begint met je eigen AS nummer …. ASNUMMER:<oude AS set naam> Kopieer daar alle informatie in, die ook in je huidige (Short) AS-Set staat.. Bewaar en check die dan even in de RIPE DB. ( A2B voorbeeld : https://apps.db.ripe.net/db-web-ui/query?searchtext=as51088:as-a2b <https://apps.db.ripe.net/db-web-ui/query?searchtext=as51088:as-a2b> ) In de oude AS-Set .. zet je 1 verwijzing in .. en de rest laat je leeg .. Dus je krijgt dan alleen een regel met .. members: ASNUMMER:<oude AS set naam> ( Voorbeeld van AS-A2B - https://apps.db.ripe.net/db-web-ui/query?bflag=false&dflag=false&rflag=true… <https://apps.db.ripe.net/db-web-ui/query?bflag=false&dflag=false&rflag=true…> ) En bij peeringdb : zet je de nieuwe AS set naam (ASNUMMER:<oude AS set naam>) .. en wil je het helemaal fancy doen .. dan doe je RIPE:: ASNUMMER:<oude AS set naam> Als je RIPE:: ervoor zet, dan is dat een referentie naar in welke RIR DB je AS-Set te vinden is .. ( voorbeeld in PeeringDB : https://www.peeringdb.com/net/3237 <https://www.peeringdb.com/net/3237> ) Daarna is het handig om ook je AS object even een update te geven .. En loop even overal na, dat je je nieuwe AS-Set in je export regels hebt staan.. zoals : * remarks: Transits * remarks: ============================================================ * import: from AS2914 action pref=100; accept ANY AND NOT {0.0.0.0/0} * export: to AS2914 announce AS51088:AS-A2B * import: from AS3257 action pref=100; accept ANY AND NOT {0.0.0.0/0} * export: to AS3257 announce AS51088:AS-A2B Mocht je dat bij peers / klanten of internet exchanges ook hebben staan.. rinse & repeat .. you know the drill. ( Voorbeeld AS51088 - https://apps.db.ripe.net/db-web-ui/query?bflag=false&dflag=false&rflag=true… <https://apps.db.ripe.net/db-web-ui/query?bflag=false&dflag=false&rflag=true…> ). Het is een pleister tegen een mogelijk issue .. maar wel handig om dit correct te fixen .. waar je later veel plezier van kan hebben .. dus doe er je voordeel mee. Die fix die er besproken wordt in de RIPE DB WG, zorgt er voor dat er geen nieuwe AS-Sets met een short notatie aangemaakt kunnen worden. Maar verhelpen is beter dan genezen. Alvast prettig weekend, Groetjes, Erik Bais -- Keep calm, keep distance, keep connected! Arnold Nipper email: arnold(a)nipper.de mobile: +49 172 2650958

1 0

Netbox or similar DCIM consulting/services
by Olaf 22 Nov '22

22 Nov '22

Hi, I am looking for someone that offers/provides consulting/services around Netbox or similar DCIM software for Staging/PoC for engineering before we would handover towards operations at my current employer. Gladly off-list via olaf.baumert(a)wz.axpo.com Sorry for the noise everyone not interested. Kind regards, Olaf

1 1

← Newer
1
...
6
7
8
9
10
11
12
...
292
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

swinog