Confusing results and basic whitelist question
-
Hi all,
I was playing with a Python package, yfinance and my first attempt to invoke it resulted in an SSL failure (self-signed-cert). I eventually figured out that it was pfBlockerNG DNSBL stopping it. (When I try and ping fc.yahoo.com I get replies from 10.10.10.1, the default DNSBL redirect target).
What's really confusing though is that when I go to https://fc.yahoo.com/ in Firefox, I get redirected to www.yahoo.com (which kind of makes sense if fc.yahoo.com is just an api server). I don't understand why I'm not seeing the same DNSBL page I get if I try and curl -k https://fc.yahoo.com/.
At any rate, I figured that just adding fc.yahoo.com to the DNSBL whitelist would fix my problem, but of course it didn't. Do I have to do anything special to update the whitelist or is there another part of the DNSBL process that is blocking it anyway? I just added "fc.yahoo.com" at the bottom of the list on its own line.
Doing a dig on Google gets me a cname with multiple IP addresses with 1 minute TTLs, so I don't think it's going to be feasible to allow IP addresses.TIA,
Dave -
@homealone The browser may be caching the redirect. Try a private window or different browser.
After making changes you need to run an update in pfB.
-
@SteveITS Thanks. I meant to put in the original post that I forced an update after I made the change.
A couple of days later, the white list appears to be working.
Thanks,
Dave