Jump to content
Not connected, Your IP: 3.236.19.251

Search the Community

Showing results for tags 'pi-hole'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • AirVPN
    • News and Announcement
    • How-To
    • Databases
  • Community
    • General & Suggestions
    • Troubleshooting and Problems
    • Blocked websites warning
    • Eddie - AirVPN Client
    • DNS Lists
    • Reviews
    • Other VPN competitors or features
    • Nonprofit
    • Off-Topic
  • Other Projects
    • IP Leak
    • XMPP

Product Groups

  • AirVPN Access
  • Coupons
  • Misc

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Twitter


Mastodon


AIM


MSN


ICQ


Yahoo


XMPP / Jabber


Skype


Location


Interests

Found 3 results

  1. Lately, I've come across the Pi-Hole, a program for the Raspberry Pi which basically turns the device into an advanced adblocker which you can connect your computer to via DNS. It sounded very fascinating as it could do the work of your typical browser adblocker but potentially freeing the use of one, thus reducing any browser entropy that could uniquely identify you - whether you're using a VPN or not. Pi-Hole website link here. Check it out! What I want to know is whether or not AirVPN would work well with the Pi-Hole if I had to replace the VPN's DNS with the devices. Are there any noteworthy features of AirVPN's DNS I would be giving up in exchange? Thanks.
  2. Hey, I got this since a while now. Sometimes I try to resolve airvpn.org it fails. After some trys or minutes it works fine. I use a Pi-Hole as DNS Server running a local unbound (127.0.0.1) and as said I only got issues with this domain here.. real strange. Luckily today I was able to grab some logs, maybe someone can read them and tell me if the dnssec-query request tell something useful ? Jan 4 19:19:07 dnsmasq[31678]: query[PTR] 44.1.168.192.in-addr.arpa from 192.168.1.15 Jan 4 19:19:07 dnsmasq[31678]: /etc/pihole/local.list 192.168.1.44 is pi-hole Jan 4 19:19:07 dnsmasq[31678]: query[A] airvpn.org.localdomain from 192.168.1.15 Jan 4 19:19:07 dnsmasq[31678]: cached airvpn.org.localdomain is NXDOMAIN Jan 4 19:19:07 dnsmasq[31678]: query[AAAA] airvpn.org.localdomain from 192.168.1.15 Jan 4 19:19:07 dnsmasq[31678]: cached airvpn.org.localdomain is NXDOMAIN Jan 4 19:19:07 dnsmasq[31678]: query[A] airvpn.org from 192.168.1.15 Jan 4 19:19:07 dnsmasq[31678]: forwarded airvpn.org to 127.0.0.1 Jan 4 19:19:09 dnsmasq[31678]: query[AAAA] airvpn.org from 192.168.1.15 Jan 4 19:19:09 dnsmasq[31678]: forwarded airvpn.org to 127.0.0.1 Jan 4 19:19:16 dnsmasq[31678]: dnssec-query[DS] airvpn.org to 127.0.0.1 Jan 4 19:19:16 dnsmasq[31678]: dnssec-query[DS] airvpn.org to 127.0.0.1 Jan 4 19:19:16 dnsmasq[31678]: reply airvpn.org is DS keytag 55882, algo 8, digest 1 Jan 4 19:19:16 dnsmasq[31678]: reply airvpn.org is DS keytag 57919, algo 8, digest 1 Jan 4 19:19:16 dnsmasq[31678]: dnssec-query[DNSKEY] airvpn.org to 127.0.0.1 Jan 4 19:19:16 dnsmasq[31678]: reply airvpn.org is DS keytag 55882, algo 8, digest 1 Jan 4 19:19:16 dnsmasq[31678]: reply airvpn.org is DS keytag 57919, algo 8, digest 1 Jan 4 19:19:16 dnsmasq[31678]: dnssec-query[DNSKEY] airvpn.org to 127.0.0.1 Jan 4 19:19:16 dnsmasq[31678]: reply airvpn.org is DNSKEY keytag 57919, algo 8 Jan 4 19:19:16 dnsmasq[31678]: reply airvpn.org is DNSKEY keytag 55882, algo 8 Jan 4 19:19:16 dnsmasq[31678]: reply airvpn.org is DNSKEY keytag 59298, algo 8 Jan 4 19:19:16 dnsmasq[31678]: reply airvpn.org is DNSKEY keytag 38193, algo 8 Jan 4 19:19:16 dnsmasq[31678]: validation result is SECURE Jan 4 19:19:16 dnsmasq[31678]: reply airvpn.org is 5.196.64.52 Jan 4 19:19:16 dnsmasq[31678]: reply airvpn.org is DNSKEY keytag 57919, algo 8 Jan 4 19:19:16 dnsmasq[31678]: reply airvpn.org is DNSKEY keytag 55882, algo 8 Jan 4 19:19:16 dnsmasq[31678]: reply airvpn.org is DNSKEY keytag 59298, algo 8 Jan 4 19:19:16 dnsmasq[31678]: reply airvpn.org is DNSKEY keytag 38193, algo 8 Jan 4 19:19:16 dnsmasq[31678]: validation result is SECURE Jan 4 19:19:16 dnsmasq[31678]: reply airvpn.org is 2001:41d0:a:6034:: Please note that I was running a nslookup airvpn.org here and at the end it was working. Same command 2 minutes earlier failed. So till 19:19:07 I had a DNS timeout when querying airvpn.org and on 19:19:16 it started to work just fine Any help is much appreciated.
  3. Hi, I'm not an expert on networks, and VPNs add a layer of complexity to the subject, so I had an idea but I don't even know whether that idea is possible or not: I have a Pi-Hole DNS server in my home network. At the LAN level, everything communicates with the Pi-Hole for DNS purposes (router uses the Pi-Hole as nameserver and DHCP clients are instructed to submit DNS requests to router). If I get the Pi-Hole to operate through AirVPN, nothing will change on the LAN side, but would it be possible for me to, for example, go outside with my smartphone (which also connects to AirVPN) and have the phone use my home network Pi-Hole for DNS purposes? I mean, both the Pi-Hole and smartphone would be connected to the AirVPN network of servers, is there a way for my Pi-Hole to provide DNS service to my VPNed devices when I take them outside my home? I understand this could get complicated, but I like learning through challenge. That being said, please be clear in your explanations.
×
×
  • Create New...