Changes in DNS?
-
I would love to see what you were seeing, why should I have to image it?
For such a tech guy, what you couldn't post a screenshot of your sniff of what pfsense was doing or not doing for dns?
And no I can not image what you described because that is NOT how it works.. So all those snaps you switched too all had the bad code? Come on dude really? Simple sniff would of shown everyone what was happening..
I don't have to try anything - anyone that jumps to multiple snaps without basic troubleshooting already painted a very clear picture ;)
-
I do disregard them now. But don't you think your setup is somewhat an overkill for a private household?
And 4 WAN links isn't? Never occurred to me we were talking about a private home network. Good luck.
-
I do disregard them now. But don't you think your setup is somewhat an overkill for a private household?
And 4 WAN links isn't? Never occurred to me we were talking about a private home network. Good luck.
Guess it is ;)
It were even 5 but I suspended one (and will probably cancel it). It's difficult to explain. First I had ADSL which is slow and flaky, then I added a WIFI link, then Sat, then a better WIFI link and then another WIFI Link that (because it's very cheap) should replace ADSL as a backup. I'll probably cancel the Sat link when the contract period is over…@Johnpoz: I just wanted to jump to the last known working version but I wasn't sure which one that was… so simple…
When I did this I wasn't even aware that it's a DNS problem. First idea was that it's an ISP problem. As you might know most websites load pics/ads/whatever from different servers and when one of the lookup fails that may cause problems that don't directly point to dns problems. -
When I did this I wasn't even aware that it's a DNS problem. First idea was that it's an ISP problem.
Broken DNS being served via DHCP by ISP sure like hell is ISP problem.
-
It were even 5 but I suspended one (and will probably cancel it). It's difficult to explain. First I had ADSL which is slow and flaky, then I added a WIFI link, then Sat, then a better WIFI link and then another WIFI Link that (because it's very cheap) should replace ADSL as a backup.
Makes me wonder…who operates the WiFi APs? You neighbor, or your landlord, or some idiot who forgot to enable security on his AP...? :-)
It might just be aomeone trying to perform an attack utlizing a fake DNS server (but obviously too incompetent to succeed).
Well, I might just be paranoid. But that doesn't mean that conspiracy theories must be all wrong, right? Seen anything suspicious lately? UFOs? Elvis? Any droids which weren't the droids you were looking for? ;-)
-
As an X-Conspirator, I believe in some conspiracy theories… No reptiles though... Thats just crazy talk :P
-
"one of the lookup fails that may cause problems that don't directly point to dns problems."
How is that? That would be the first thing it would point too, if something doesn't load you would verify name resolution. Once you verify name resolution, then you check connectivity. Your name resolution problem may well be a connectivity issue.
Some websites don't load, images not working - so try a different snap?? Come on dude seriously??
-
When I did this I wasn't even aware that it's a DNS problem. First idea was that it's an ISP problem.
Broken DNS being served via DHCP by ISP sure like hell is ISP problem.
I agree. On the other hand, 2 bad ones out of 8 shouldn't be a problem (even 7 out of 8 shouldn't). But we're running circles. Maybe I'll try to reproduce the problem some day. What's the best way to capture dns requests on pfsense? Seams to be possible within the gui as I saw in the other posting? For whatever reason the list of available packets doesn't load right now…
-
Nonsense! Don't stop now. I've just gotten my popcorn and soda :-[
-
Makes me wonder…who operates the WiFi APs? You neighbor, or your landlord, or some idiot who forgot to enable security on his AP...? :-)
In this area there are a lot of ISPs that provide their services with directed pt2pt WIFI links. The other side of my main link is more than 8 km away on a hill. There's no neighbor signal I could pick up ;)
-
"one of the lookup fails that may cause problems that don't directly point to dns problems."
How is that? That would be the first thing it would point too, if something doesn't load you would verify name resolution. Once you verify name resolution, then you check connectivity. Your name resolution problem may well be a connectivity issue.
Some websites don't load, images not working - so try a different snap?? Come on dude seriously??
It was not the first thing I did… Listen, I already know you're a genious, OK? As I didn't have any DNS problems the last years when some pages don't load correctly it wasn't the first thing to come to my mind. And unfortunately dig and nslookup behave quite differently form safari. It wouldn't have been the first time my multi WAN setup was causing problems and it wouldn't have been the first time 'trying another snap' would resolve it. Heck, the last few builds even crashed safari beta builds.