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

    Pfblocker (DNSBL) and android amazon app (android web viewer) issue "SOLVED"

    pfBlockerNG
    16
    20
    18.5k
    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.
    • S
      scorpious
      last edited by

      local-data: "amazon-adsystem.com 60 IN A 10.10.10.1"
      local-data: "amazon-cornerstone.com 60 IN A 10.10.10.1"
      local-data: "amazonily.com 60 IN A 10.10.10.1"
      local-data: "assoc-amazon.ca 60 IN A 10.10.10.1"
      local-data: "assoc-amazon.co.uk 60 IN A 10.10.10.1"
      local-data: "assoc-amazon.com 60 IN A 10.10.10.1"
      local-data: "assoc-amazon.de 60 IN A 10.10.10.1"
      local-data: "assoc-amazon.es 60 IN A 10.10.10.1"
      local-data: "assoc-amazon.fr 60 IN A 10.10.10.1"
      local-data: "assoc-amazon.it 60 IN A 10.10.10.1"
      local-data: "aan.amazon.com 60 IN A 10.10.10.1"
      local-data: "aax-eu.amazon-adsystem.com 60 IN A 10.10.10.1"
      local-data: "aax-us-east.amazon-adsystem.com 60 IN A 10.10.10.1"
      local-data: "aax-us-pdx.amazon-adsystem.com 60 IN A 10.10.10.1"
      local-data: "adagiobanner.s3.amazonaws.com 60 IN A 10.10.10.1"
      local-data: "dra.amazon-adsystem.com 60 IN A 10.10.10.1"
      local-data: "fls-na.amazon.com 60 IN A 10.10.10.1"
      local-data: "ir-na.amazon-adsystem.com 60 IN A 10.10.10.1"
      local-data: "mobileanalytics.us-east-1.amazonaws.com 60 IN A 10.10.10.1"
      local-data: "mobileanalytics.us-east-2.amazonaws.com 60 IN A 10.10.10.1"
      local-data: "mobileanalytics.us-west-1.amazonaws.com 60 IN A 10.10.10.1"
      local-data: "mobileanalytics.us-west-2.amazonaws.com 60 IN A 10.10.10.1"
      local-data: "rcm-images.amazon.com 60 IN A 10.10.10.1"
      local-data: "rcm-it.amazon.it 60 IN A 10.10.10.1"
      local-data: "sdogiu.bestamazontips.com 60 IN A 10.10.10.1"
      local-data: "uedata.amazon.com 60 IN A 10.10.10.1"
      local-data: "aax-us-west.amazon-adsystem.com 60 IN A 10.10.10.1"
      local-data: "admarvel.s3.amazonaws.com 60 IN A 10.10.10.1"
      local-data: "campaign-tapad.s3.amazonaws.com 60 IN A 10.10.10.1"
      local-data: "html5adkit.plusmo.s3.amazonaws.com 60 IN A 10.10.10.1"
      local-data: "iacpromotion.s3.amazonaws.com 60 IN A 10.10.10.1"
      local-data: "inneractive-assets.s3.amazonaws.com 60 IN A 10.10.10.1"
      local-data: "strikeadcdn.s3.amazonaws.com 60 IN A 10.10.10.1"

      1 Reply Last reply Reply Quote 0
      • D
        doktornotor Banned
        last edited by

        Eh, stick something like

        
.s3.amazonaws.com

        to the whitelist?

        1 Reply Last reply Reply Quote 0
        • RonpfSR
          RonpfS
          last edited by

          Did you use the "+" icon to whitelist s.amazon-adsystem.com? This will also whitelist any CNAME.

          Or remove the leading "." and just put

          s.amazon-adsystem.com

          2.4.5-RELEASE-p1 (amd64)
          Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
          Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

          1 Reply Last reply Reply Quote 0
          • S
            scorpious
            last edited by

            I tried to enter that in the custom list, but it did not seem to have any affect.

            digging into it further I turned off the DNSLB feed "someonewhocares" ad blocking. and Amazon android web service worked.

            further down the list the check mark for Alexa white list was turned off. so when I checked that and restarted DNSLB. Amazon AWS was working, expect for pages that did not have ads "like order page" and few others, but not the home page.

            so I made the following change to the custom white list in DNSLB

            .amazonaws.com
            .amazon-adsystem.com

            and reran the UPDATE. Amazon AWS works like a charm. no issues.

            I suppose I can consider this Thread SOLVED.

            Thanks a lot for your help.

            Ashish

            ![DNSBL Feeds - pfSense.jpg](/public/imported_attachments/1/DNSBL Feeds - pfSense.jpg)
            ![DNSBL Feeds - pfSense.jpg_thumb](/public/imported_attachments/1/DNSBL Feeds - pfSense.jpg_thumb)

            1 Reply Last reply Reply Quote 0
            • B
              bchow
              last edited by

              This is an old thread, but I have this working as of 9/15/17 for the Amazon app.  There was one one domain not showing up in the DNSBL logs/alerts that I found in the main firewall, and that was googleapis.com.  Here is my current whitelist that allows plex, and the amazon android app to work.

              .amazonaws.com
              .amazon-adsystem.com
              .amazon.com
              .ssl.google-analytics.com
              .ssl-google-analytics.l.google.com # CNAME for (ssl.google-analytics.com)
              .www.google-analytics.com
              .www-google-analytics.l.google.com # CNAME for (www.google-analytics.com)
              .www.googleadservices.com
              .plex.tv
              .gravatar.com
              .thetvdb.com
              .themoviedb.com
              .googleapis.com # 172.217.3.202 is important for amazon app to work
              .1e100.net # cname? altname? for googleapis.com

              1 Reply Last reply Reply Quote 0
              • T
                thezfunk
                last edited by

                Running into this exact problem and I tried everything I see  in this thread to no avail.  Do I have to refresh something when I add something to the whitelist?

                1 Reply Last reply Reply Quote 0
                • S
                  silverhair
                  last edited by

                  I used the posted whitelist above, and the Amazon app works.

                  @thezfunk, where did you add your whitelist? 
                  Under Firewall -> pfBlockerNG -> DNSBL there are two options, the "Custom Domain Whitelist" and the "TLD Whitelist". 
                  Which did you use?

                  After you've updated the list, you'll need to wait ten minutes for the cronjob to update the lists, or force the list to update manually.  Did you wait long enough?

                  1 Reply Last reply Reply Quote 0
                  • L
                    lordbob75
                    last edited by

                    I'm having this issue as well.  Added the entire list posted a couple comments up by silverhair, but still closes the login screen constantly.

                    Silverhair asked about which whitelist, I thought it was the Custom Domain Whitelist.  Should it be the TLD one instead?

                    Edit:  Did not realize that the update didn't push changes and needed to reload it instead.  Able to log into the app now.  Thanks to Silverhair for the list.  May have to try removing lines one at a time until it stops working though.

                    1 Reply Last reply Reply Quote 1
                    • B
                      BSA66
                      last edited by

                      I was just running into a similar issue (Amazon Android App not working)

                      My shortly added Domain Whitelists are the following:

                      .c.amazon-adsystem.com # Amazon Advertisements
                      .d1ykf07e75w7ss.cloudfront.net # CNAME for (c.amazon-adsystem.com)
                      .fls-eu.amazon.de
                      .fls-eu.amazon.com # CNAME for (fls-eu.amazon.de)
                      .gateway.prod.eu-west-1.forester.a2z.com # CNAME for (fls-eu.amazon.de)
                      .endpoint.prod.eu-west-1.forester.a2z.com # CNAME for (fls-eu.amazon.de)
                      .mads.amazon-adsystem.com # Amazon Adsystem Mads
                      .amazon-adsystem.com # Amazon Adsystem MADS

                      As you see it is a little bit unsorted what I track back to my whitelisting flow... You should not just copy & paste it as in your region and on your phone / setup / yet added Domains on the Whitelist it may work or even not work.

                      The process is easy.

                      • run your apps and keep about 5-10 secs after reload the DNSBL Alert Tab
                      • check for potentially corresponding Domains
                      • whitelist them**

                      ** First I added them manually to the Domain Whitelist which did not work (I guess the CNAMEs might have been missing...)
                      It is uncomfortable to whitelist them automatically by the + Sign as every Alert Tab Reload takes Ages to reload...
                      But anyway, at least it was necessary for me to get the CNAMEs, too, as it did not seem to work without them.
                      BTW this is also the reason why the List seems to be so unsorted, I added several before the automatic initiated Alert Tab Reload (and maybe the hidden but initiated Reload-DNSBL for adding the new Entries) accomplished.

                      1 Reply Last reply Reply Quote 0
                      • A
                        aaronhong13
                        last edited by

                        Not sure if this is still an ongoing issue, but posting incase someone else finds this thread with the same question.

                        Adding this fixed the app for me. No more "Something has gone wrong messages". If any other issues come up, I will update this post.

                        DNSBL Whitelist
                        .aan.amazon.com

                        1 Reply Last reply Reply Quote 1
                        • V
                          viskalpiskal
                          last edited by

                          Old thread, created an account to help others
                          from uk here, managed to fix it as per BSA66 suggestion, loading the app and looking at the DNSBL Alert tab for my phone

                          saw, z.moatads.com
                          and then whitelisted it
                          now have several whitelist domains
                          z.moatads.com # z.motads
                          www.z.moatads.com # z.motads
                          wildcard.moatads.com.edgekey.net # CNAME for (z.moatads.com)
                          e13136.g.akamaiedge.net # CNAME for (z.moatads.com)

                          Hopefully this will fix the problem for you.

                          1 Reply Last reply Reply Quote 0
                          • J
                            jjneff
                            last edited by

                            Hey all,
                            I read this somewhere else for a non-pfsense oriented fix. If your phone allows it, change the app settings to only allow it to use cell data. Obviously this doesn't help if you HAVE to use wifi, but it also doesn't help your network's security to whitelist all these url's for the sake of one device/app imo. I figured it would be a helpful consideration for those it may apply to.

                            1 Reply Last reply Reply Quote 0
                            • B
                              bandit8623
                              last edited by

                              aan.amazon.com

                              is the 1 that needs to be added only to stop the uh oh in the amazon app

                              noplanN 1 Reply Last reply Reply Quote 1
                              • noplanN
                                noplan @bandit8623
                                last edited by

                                @bandit8623

                                true statement the only one needed to fix uh oh

                                aan.amazon.com

                                1 Reply Last reply Reply Quote 0
                                • G
                                  GorillaMitts
                                  last edited by

                                  This post is deleted!
                                  1 Reply Last reply Reply Quote 0
                                  • P
                                    pulsartiger
                                    last edited by

                                    I have this issue also with pfblocker and the Amazon app (Android). I whitelist the domains that I saw in the report log but I still have the dog screen come up stating "UH-OH Something went wrong on our end." What's odd is that this only happens when searching and it only happens when searching certain terms. Has anyone found the exact domains to whitelist? (aan.amazon.com did not do it for me)

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