BWC Cybersecurity Overlord ✭✭✭
Reactions
Comments
-
@Larry would love to have some form of User Feedback (Uservoice) too, but I fear it got lost in the suggestion box. --Michael@BWC
-
Hi @ThK ... I checked and did not see any new bounces, the SNWL DNS is just poorly configured but does not do any harm at the moment, IMHO. --Michael@BWC
-
Hi @sdp it's a bit tricky to give advice here and I feel your need to get it resolved quickly. But Security isn't something to rush, IMHO. If you don't have the expertise to configure it from scratch, hire someone with the knowledge to do it for you. Or just give it a try to migrate/import the old settings into the new…
-
Hi, today a on-prem ES customer reported about the same "Bad Request" problem, copy&paste of the original URL worked though. What causes this and can it be avoided? --Michael@BWC
-
@David W it's back to "normal" again, but it's still badly configured. Your authoritative DNS is returning this, having both NS pointing to the same IP address is bad design and asks for a single point of failure. You should check your glue records for that. At least the non-resolving entry is removed again.…
-
Sorry for the double post. I'am confused, did SNWL really revert back to the DNS misconfiguration and everything will start all over again? BTW, same goes again for snwlhosted.com @David W any take on that? % dig @8.8.8.8 NS snwlhostedeu.com ; <<>> DiG 9.10.6 <<>> @8.8.8.8 NS snwlhostedeu.com ; (1 server found) ;; global…
-
I'am confused, did SNWL really revert back to the DNS misconfiguration and everything will start all over again? BTW, same goes again for snwlhosted.com @David W any take on that? % dig @8.8.8.8 NS snwlhostedeu.com ; <<>> DiG 9.10.6 <<>> @8.8.8.8 NS snwlhostedeu.com ; (1 server found) ;; global options: +cmd ;; Got answer:…
-
Hi @sdp wow quite a step, but if your consultants (AKA 💰️💰️💰️) said so. The Migration Support Matrix does not cover the NSa 3700 at the moment, but NSa 2700 is on it, so my best guess it would probably work.…
-
Hi @Connex_Ananth just a side note, because I don't get why Mobile Connect is still mentioned here these days. Isn't it dead already? Besides that, I never deployed NetExtender through SCCM or Intune, so I will be no help on that. --Michael@BWC
-
Not sure if disabling 173.240.221.13 will be a lasting solution, if the root cause is not fixed all other outbound servers will be burnt real quick :) --Michael@BWC
-
Hi @ThK I checked the whole network but it seems "only" one outbound server is blacklisted: IP 173.240.221.13 NAME outbound13.snwlhostedeu.com. 13.221.240.173.ips.backscatterer.org. 127.0.0.2 This is probably because of the stupid resetting DHA settings bug, which causes trouble for all HES customers. Shared pain is still…
-
Situation seems to be defused, at the end it might be caused by a small DNS misconfiguration at SNWL. --Michael@BWC
-
Hi guys, I have to wait until my customers are waking up, but if it was indeed a DNS related issue like I suspected yesterday you should give the DNS admin a clap on the back of his/her head. snwlhosted.com got fixed too, bravo. But it's just another batch of unbillable hours, who counts. 🤯 UPDATE: A test mail to @web.de…
-
@David W I’am not sure if your SOA serial reflects the actual date of change, but it still says 2021030188 for snwlhostedeu.com, which can be ok or maybe is outdated. Pointing ns1 und ns2.snwlhostedeu.com to the same IP is bad design, IMHO. I guess you don't do any zone transfers then. UPDATE: About the PTR,…
-
The whole thing might be not just limited to United Domains, another delivery to a different provider got bounced with this message: 5.0.0 (undefined status) smtp;550 Sender verification problem It might be all related to the wrongful configuration of the NS records for snwlhostedeu.com (and snwlhosted.com). --Michael@BWC