Unable to resolve certain sites DNS Resolver

Gertjan

@bigraz1968 said in Unable to resolve certain sites DNS Resolver:

The other machines on the LAN work fine

Compare IP config on working and not working machines and you'll find the answer.

bigraz1968

I did all that. All of the clients on the LAN are getting their IP configuration from the same DHCP server.

Thanks

Randy

Gertjan

IP ok, but DNS ? Gateway ?

bigraz1968

I checked and all the same.

johnpoz

So your saying something resolve for this client and other things do not - or dns is not not working at all?

What error do you get when you do a dig or nslookup?

bigraz1968

It seems like the firewall is holding some stale information somewhere and rebooting isn't fixing the issue.

bigraz1968

Hi John

The two clients are my TV's have the issue My Netflix smart app. doesn't work I get the message 'Unable to connect' I use the builtin browser to load Netflix and Netflix still doesn't load. Other sites will load. Sharp TV support worked on the issue and finally said the problem is my router.

I hookup my Chromebook and Netflix.com doesn't load. It just says 'Waiting on cache' an then it stops loading

I hookup another laptop and that laptop loads Netflix without issue.

The common denominator is machines that had a static DHCP reservation don't work, but machines not assigned statically have no issues

johnpoz

doesn't answer the question.. What happens when you query - and does it happen for all things or just some sites?

Lets see an example dig or nslookup query (dig is BETTER) from client that works, and from client that doesn't work.

edit: Well what are you doing different in your static reservation? You know you can point to different dns.. Or you could have different rules, etc.

Simple solution would be to sniff on pfsense to see exactly what the client is trying to do, etc. Netflix apps can be hard coded to try and query say google dns.

bigraz1968

DNS is working. Just a couple frequent sites I use will not resolve. I picked Netflix because in my house it is used frequently. I can do a working client but unable to perform dig on a broken client. I am at work.

bigraz1968

Nslookup query from working machine

C:\Users\rdevone-desktop>nslookup netflix.com
Server: pfSense.localdomain
Address: 192.168.1.1

Non-authoritative answer:
Name: netflix.com
Address: 45.76.252.24

johnpoz

ok well that is a cached response from 192.168.1.1 (assume pfsense IP since it resolve to pfsense.localdomain)... so lets see something broken when you get home..

I take it you did not mess with the the unbound views and acls..

bigraz1968

I take it you did not mess with the the unbound views and acls.. No I don't know what that is. I haven't made any changes at all.

You always have been so helpful. I really appreciate your help. My family is going to kill me if I don't get this fixed soon.

Thanks

Randy

bigraz1968

Johnpoz;

I did a dig on one of the clients that is having a issue and the dig command completes successfully as it did on a client that has no issue.

Thanks

Randy

bigraz1968

Johnpoz;

I made a mistake. I did the dig with the wrong DNS server. I switched the DNS to my resolver and I get 'connection timed out, no servers can be reached'.

Thanks

Randy

johnpoz

so you can not get any sort of answer from pfsense? From this client? Or you saying that certain looks fail?

bigraz1968

Correct. for Netflix.com Most sites do resolve. If I switch to a client in my DMZ. Netflix resolves successfully. DMZ uses the resolver as well.

johnpoz

Here is the thing the resolve doesn't care what network your on local - if you can talk to it, then it the same no matter what local network your on.. UNLESS you have messed with the acls or created views.

What are your firewall rules on this interface?