Hi Diochengion11

Like the others, I would also check whether the domain is resolved correctly at your parents’ home.

The best way to do this is to use the board tools “nslookup” or “dig” instead of online tools 😉.

If a different IP is reported, visit the page via HTTP (without S), the Internetguard may then respond and you can report the IP as false positive.

If you like, you can also send me the domain by PM and I’ll see if I can reach it from my Swisscom connection. Do you have any IDS/IPS in use?

LG

r00t

I noticed something similar at my home (server on own domain with host from Cloudflare) and DNS on Swisscom’s IB. When I changed the DNS server to the same one as the name server, everything worked. In my case it is 1.1.1.1…

Diochengion11

This has nothing to do with fibre optics if the technician briefly reconnects the fibre optic cable for his measurement.

The technician always checks that the router is back online and that the customer’s telephone, TV and Internet services are running.

There must be something else with your parents.

Cloudfare has switched to HTTPS for DNS, the rest is now going nowhere.

Have you tried one from another Swisscom connection?

Private customer connection

And after you have reconnected, how does the LED light up, flashing red or steady white?

Did you also observe the bending radii of the cable?

Greetings Lorenz

Hi Diochengion11

Thanks for the hostname, I can easily reach it from my connection and also resolve it correctly.

Do you see e.g. with tcpdump the traffic arriving at your server? If not, I would get @ChristianEb on board to see if there is a problem somewhere in the network.

LG

r00t

Diochengion11

Have you ever completely reset the Internet box?

There are three possible causes: either the DNS or the routing or a protection mechanism of the target system. Your comment that it worked briefly after the technician’s visit could be explained by the fact that your router was given a new IP at the time, but this was then quickly blocked. At least the first two causes can be narrowed down with the simple on-board tools of the operating system, as r00t already wrote above.

@Diochengion11 If you compare the output of the command “nslookup mail.meindomain.xx” with that of “nslookup mail.meindomain.xx 8.8.8.8” in a command line window, do you notice a difference? What output does the command give if you run it from an Init7 or Thurcom connection? If the results were only different on the Swisscom connection or with the Swisscom DNS, you would have to look further for the error in the DNS. An online DNS resolver, which can also detect any subtle DNS misconfigurations, may help. For example this one: https://www.diggui.com/

If the DNS is good, check the routing next. Can you ping your mail server (command line “ping mail.mydomain.xx”)? If not, how far does a traceroute get (command line “tracert mail.mydomain.xx”, a few unreachable lines are normal)?

Basically, does mail.meindomain.xx only have an IPv4 address or also an IPv6 address? And how exactly do you access the mail server, i.e. with which protocols? IMAP/POP/SMTP? Encrypted? I don’t assume and hope you don’t, but TCP port 25 is blocked outgoing at Swisscom, and for good reason.

Diochengion11 basically this forum works, yes….

but it is advisable to know that you are not opening a ticket here, but that you can expect answers in a user community that looks at what it can do on a goodwill basis….

Diochengion11 It would work better if you also answered the questions questions. A decent tone of voice also increases the chances of getting useful answers.