OPNsense Forum

English Forums => General Discussion => Topic started by: oppland on July 01, 2023, 12:56:08 am

Title: weird dns problem (solved)
Post by: oppland on July 01, 2023, 12:56:08 am
I don't think this is opnsense related, but just hoping this might make sense to someone here.

My wife works at a VA Hospital and has been working from home at times for the last few years.  She could connect to the work vpn just fine over our home wifi (unifi access points).

Suddenly, it didn't work on her work laptop.  It said it couldn't resolve the va.gov address.  I couldn't ping the address either.  Everything worked on my computer, but I then realized nothing could reach va.gov over wifi.  Not even the webpage.  Other .gov sites were fine.

I checked the AP and the dns was set to 1.1.1.1   I tried changing it to 192.168.0.1 (my opnsense router with unbound) and that fixed it.

The first dns server for unbound is 1.1.1.1

I'm glad it works now, but does that make any sense?
Title: Re: weird dns problem (solved)
Post by: CJ on July 01, 2023, 03:33:23 pm
I don't think this is opnsense related, but just hoping this might make sense to someone here.

My wife works at a VA Hospital and has been working from home at times for the last few years.  She could connect to the work vpn just fine over our home wifi (unifi access points).

Suddenly, it didn't work on her work laptop.  It said it couldn't resolve the va.gov address.  I couldn't ping the address either.  Everything worked on my computer, but I then realized nothing could reach va.gov over wifi.  Not even the webpage.  Other .gov sites were fine.

I checked the AP and the dns was set to 1.1.1.1   I tried changing it to 192.168.0.1 (my opnsense router with unbound) and that fixed it.

The first dns server for unbound is 1.1.1.1

I'm glad it works now, but does that make any sense?

What do you mean by the AP dns was set to 1.1.1.1?  What ip config was the laptop and your computer showing?

What other dns servers are configured for unbound?

I have seen cases where one dns provider has issues resolving a particular domain for a short time period.  Switching to another dns provider or just waiting a bit will fix the issue.