DNS Resolver doesn't work with my university domain.
-
-
@fandangos Yeah!!! great all sorted and didn't have to sit on hold with your isp, talking to someone that had no idea what your talking about.. And them telling you we do not block any outbound ports ;)
-
Can't thank you enough, guys.
Specially John that helped for days until this got figured out, one problem after another.Thanks a lot! :)))
-
Wow, that's fun*. So the ISP is blocking the udp traffic with source port 123 because that's easier than actually using a stateful firewall?!
-
Guess so, it's weird but I always had this problem. To be honest, I'm not sure why it started working for my unraid box.
It didn't a few months ago when I looked into this. -
@fandangos glad could be of help.. Always fun getting to the actual root of a problem..
-
@stephenw10 nothing saying the security guy at isps have to be the sharpest crayon in the box ;) heheh
Our users don't need 123 inbound, only out. Never coming to think that 123 is the default/common source port as well for ntp. And they prob don't get many complaints, because most of their users are prob using the isp router and all their devices are behind a nat so would never see the problem to complain about it.
@Fandangos if you ever just sitting around hmmm, what could I do that would be painful - you could try calling your isp and point out to them the problem they have ;)
-
@johnpoz said in DNS Resolver doesn't work with my university domain.:
Reason you seeing the problem is pfsense using its public wan IP never goes through a nat and uses the common normal source port for ntp of 123
You mean :
When I use a modem device, and one PC hooked up to it, using for example PPPOE, this PC won't be able to 'ntp' neither ?
I know, this set up doesn't exist any more these days, but was quiet common in the old days.I would like to understand what the reason for the ISP is to block this port 123.
ntp is a very low bandwidth service.
Router firewalls like pfSense can handle often TLS related functions, DNSSEC is just one of them, and using the correct time is not some kind of option.
So it should go back into it's LAN, to ask a NTP service (server), and that one goes back out to the net to sync ?
Strange ....No "help me" PM's please. Use the forum, the community will thank you.
Edit : and where are the logs ?? -
@gertjan said in DNS Resolver doesn't work with my university domain.:
When I use a modem device, and one PC hooked up to it, using for example PPPOE, this PC won't be able to 'ntp' neither ?
Exactly, it would fail because the service almost certainly uses 123 as the source port.
It would also fail through any NAT that did not change the source port.They are blocking it because they do not want their users running NTP servers or more likely accidentally exposing NTP servers and being used in an amplification attack.
But they are blocking it incorrectly IMO. They seem to have blocked to/from port 123 at the user side. As though they are not using stateful filtering.Steve
-
@gertjan said in DNS Resolver doesn't work with my university domain.:
I would like to understand what the reason for the ISP is to block this port 123.
While I agree it low bandwidth, but it is also a common amplification tool via for one that old monlist command, but pretty sure that was disabled many versions ago to prevent that attack vector.
But maybe they are just playing it safe because not like users keep their stuff updated all the time.. Look at here where they are still running like 2.3 versions of pfsense..
They could do it a different way to allow for source 123 to be answered, with yeah a stateful firewall. so if one of there users asks some ntp server with source port 123 that is allowed, but nonstateful traffic inbound to 123 would be denied. While sure udp is not really a stateful protocol, most firewalls do keep track of the state.
But that would be more work for them so they most likely just go the easy route. And don't monitor state of the users traffic and just block all inbound to their network on 123..
