Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    NETFLIX NOT WORKING CAUSE OF DNS

    Scheduled Pinned Locked Moved General pfSense Questions
    5 Posts 5 Posters 1.6k Views 3 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • O Offline
      OpenWifi
      last edited by

      Hello guys, it has been long since I logged in but I hope you are well. So about one month ago, my Netflix account ceased to function on my android tv. At first, I thought the problem was the TV, so I reset it, even reinstalled the Netflix app but to no avail. On my firewall, I have these two rules to redirect any DNS request from my LAN network to my firewall before it sets out to the outside world
      Screenshot (51).png
      Here the IP address 192.168.7.240 is my home router WAN Ip, so it's below the two DNS rules, meaning my home router gets its DNS requests resolved by my firewall.This is initially how it was..Now the changes i made are below
      Screenshot (52).png
      Now here you see the Ip address rule is up the Two DNS rules and after I made the change it worked, Netflix was able to open up without any issue.
      I know most of us will say, that rule was affecting it but remember I have used this firewall for about one year and there was no issue with the first rule, I was able to stream Netflix...Another issue is now it becomes a security risk for my end devices as they can now use a DNS that isn't my firewall. Kindly advice...

      bingo600B S 2 Replies Last reply Reply Quote 0
      • bingo600B Offline
        bingo600 @OpenWifi
        last edited by

        @openwifi said in NETFLIX NOT WORKING CAUSE OF DNS:

        .Another issue is now it becomes a security risk for my end devices as they can now use a DNS that isn't my firewall.

        Since you have just allowed the Netflix device , there is no risk that the other devices can use a "foreign" dns.

        If you find my answer useful - Please give the post a šŸ‘ - "thumbs up"

        pfSense+ 23.05.1 (ZFS)

        QOTOM-Q355G4 Quad Lan.
        CPUĀ  : Core i5 5250U, Ram : 8GB Kingston DDR3LV 1600
        LANĀ  : 4 x Intel 211, DiskĀ  : 240G SAMSUNG MZ7L3240HCHQ SSD

        1 Reply Last reply Reply Quote 0
        • S Offline
          SteveITS Rebel Alliance @OpenWifi
          last edited by

          @openwifi Do you happen to have any other rules blocking DNS over HTTPS? I had set rules for that up at home and found only one very specific problem...the Dish (satellite) video on demand channel/app connects only over DoH, despite the Dish hardware using regular DNS for everything else. I have not had any issues using Netflix, but don't have an Android TV.

          Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
          When upgrading, allow 10-15 minutes to reboot, or more depending on packages, and device or disk speed.
          Upvote šŸ‘ helpful posts!

          1 Reply Last reply Reply Quote 0
          • U Offline
            Uglybrian
            last edited by Uglybrian

            Hi, I’m thinking if you were to also allow TCP along with UDP on your firewall rules. DNS for Netflix would work as it normally did,before it stopped. I don’t know for sure,but I do know that DNS requires both TCP and UDP to work properly.

            1 Reply Last reply Reply Quote 0
            • stephenw10S Offline
              stephenw10 Netgate Administrator
              last edited by

              @openwifi said in NETFLIX NOT WORKING CAUSE OF DNS:

              I have these two rules to redirect any DNS request from my LAN network to my firewall

              Mmm, you have shown firewall rules but they do not redirect anything. Do you have port forwards for the DNS traffic too?

              Steve

              1 Reply Last reply Reply Quote 1
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.