DNS issue - important apps don't load anymore

100455374

Hi,

Since 1-2 months ago, all the important apps on my phone and websites (on both phone and PC) stopped working: postfinance, medgate, aldi mobile, etc.

After further investigation, I noticed that the issue is the DNS. I tried changing it in my router to Google’s DNS 8.8.8.8, 1.1.1.1, and even the ones from here https://quickline.ch/media/coqdsn4c/210412_sicherheits-abc_v1-9.pdf 212.60.61.246 / 212.60.63.246 but with no luck.

Please let me know what can I do to make these apps work again since they are very important. Imagine that every time I need to use postfinance or medgate, I have to switch to the carrier’s 4G connection because on wi-fi they don’t work.

Thank you very much,

Mihai (8192, Glattfelden - if helps)

MTR

Hello @100455374

Hm, so I don’t know exactly what you mean….
Which Quickline products are you using? Private or business customer?

In the linked document it is about the telephony services and what needs to be configured on the firewall.
But now you mention that you have changed the DNS entries on the router…

What does your installation look like (modem [bridge mode yes/no?], firewall, router, etc.)?

And you can then use the mentioned apps and websites only in the mobile network and not in the WLAN?
What kind of error is displayed or what happens after starting the app or when entering a web page in the browser?

Are any filters / blockers installed and running?

100455374

Thank you MTR for your response. You gave me a very good hint: To check if the firewall is enabled in the router. I disabled the firewall and now everything seems to be back to normal. Thank you very much!

MTR

Hello @100455374

You’re welcome!

Have you deleted your first post?

100455374

Hi MTR,

Unfortunately, yes. But now I restored it since I realized that the post could help some other folks out there 😃

Thank you again!

Networker

MarkusQuick I strongly support this view.

And actually I know of no consumer router that by vendor settings blocks traffic originating from inside your home network to the WAN. Just the other way round…

100455374 If you really would like to help others you should let people know what happened before you noticed the problem (e.g. update of router firmware, …) and how you came to conclude that DNS was the problem.

MTR

Thank you @100455374

Yes exactly - this is important for traceability when someone has the same problem.

MarkusQuick

@100455374

You solved the problem by switching off the firewall?

That’s not really a good idea. You should setup firewall rules instead.

MTR

Ooops. Yes, of course, so somewhere a firewall should still be active.

In my first answer, it was not clear to me how the infrastructure is set up and what devices are in use.

I now assumed that @100455374 did not simply disable all or the only firewall in use to solve the problem.

But maybe he can tell us how everything is installed and what the firewall is like.