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

    DNS Resolver not resolving a specific hostname

    Scheduled Pinned Locked Moved
    General pfSense Questions
    4
    11
    147
    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.
    • M
      michmoor LAYER 8 Rebel Alliance
      last edited by

      pfSense DNS server configuration is as follows

      ad8d0714-7743-4691-a829-151f7a3631be-image.png

      Everything is working fine until i signed up for a service and it required me to validate my email address. Once i received the link in my inbox, i click on it, and it times out.

      The address in question is hq4ypryg.r.us-west-2.awstrack.me

      When i resolve the name using pfSense there is no response so that makes sense

      39f74c84-4b7d-4118-b788-98316a5c97bc-image.png

      When i do a dig lookup using the same external DNS servers as configured on pfsense i get response

      b880f9b9-8e31-44b7-9830-ade81f14f167-image.png

      Whats going on ??

      Firewall: NetGate,Palo Alto-VM,Juniper SRX
      Routing: Juniper, Arista, Cisco
      Switching: Juniper, Arista, Cisco
      Wireless: Unifi, Aruba IAP
      JNCIP,CCNP Enterprise

      GertjanG johnpozJ 2 Replies Last reply Reply Quote 0
      • GertjanG
        Gertjan @michmoor
        last edited by Gertjan

        @michmoor said in DNS Resolver not resolving a specific hostname:

        hq4ypryg.r.us-west-2.awstrack.me

        Same thing here :

        2bad1c66-2354-4e2e-9b33-d0c673edd748-image.png

        So pfBlockerng does what what it is paid for :

        e37fe0ff-0001-4ac3-af61-653e3d274e7a-image.png

        Btw : I can somewhat imagine that awstrack.me is listed in some DNSBL ^^

        If your device was asking 1.1.1.1 directly, then you would have had an answer :

        [24.03-RELEASE][root@pfSense.bhf.tld]/root: dig @1.1.1.1 hq4ypryg.r.us-west-2.awstrack.me +short
r.us-west-2.awstrack.me.
r.delegate.us-west-2.awstrack.me.
baconredirects-elb-mev7rf5mv7m-1287676624.us-west-2.elb.amazonaws.com.
44.235.182.63
44.238.30.7
54.212.58.93

        A solution : whitelist "hq4ypryg.r.us-west-2.awstrack.me", probably the entire ".awstrack.me" domain.

        No "help me" PM's please. Use the forum, the community will thank you.
        Edit : and where are the logs ??

        1 Reply Last reply Reply Quote 0
        • johnpozJ
          johnpoz LAYER 8 Global Moderator @michmoor
          last edited by

          @michmoor not having any issues with resolving that

          ;; QUESTION SECTION:
;hq4ypryg.r.us-west-2.awstrack.me. IN   A

;; ANSWER SECTION:
hq4ypryg.r.us-west-2.awstrack.me. 3600 IN CNAME r.us-west-2.awstrack.me.
r.us-west-2.awstrack.me. 3600   IN      CNAME   r.delegate.us-west-2.awstrack.me.
r.delegate.us-west-2.awstrack.me. 3600 IN CNAME baconredirects-elb-mev7rf5mv7m-1287676624.us-west-2.elb.amazonaws.com.
baconredirects-elb-mev7rf5mv7m-1287676624.us-west-2.elb.amazonaws.com. 3600 IN A 54.212.58.93
baconredirects-elb-mev7rf5mv7m-1287676624.us-west-2.elb.amazonaws.com. 3600 IN A 44.235.182.63
baconredirects-elb-mev7rf5mv7m-1287676624.us-west-2.elb.amazonaws.com. 3600 IN A 44.238.30.7

          dns.jpg

          I would do a dig +trace on pfsense to see where you might be failing, keep in mind that you would have to manually follow a CNAME when you do a dig +trace.

          An intelligent man is sometimes forced to be drunk to spend time with his fools
          If you get confused: Listen to the Music Play
          Please don't Chat/PM me for help, unless mod related
          SG-4860 24.03 | Lab VMs 2.7.2, 24.03

          GertjanG 1 Reply Last reply Reply Quote 0
          • GertjanG
            Gertjan @johnpoz
            last edited by

            @johnpoz said in DNS Resolver not resolving a specific hostname:

            not having any issues

            I'm betting that @mich is using :

            f6bbe9d7-c1e2-4a00-bc9b-0dd8719269cd-image.png

            or one of the other DNSBL that contains "track.me".

            No "help me" PM's please. Use the forum, the community will thank you.
            Edit : and where are the logs ??

            M 1 Reply Last reply Reply Quote 0
            • M
              michmoor LAYER 8 Rebel Alliance @Gertjan
              last edited by

              @Gertjan

              I checked my dnsbl.log file and its not coming up at all.

              
[24.03-RELEASE][admin@GAFW]/root: cat /var/log/pfblockerng/dnsbl.log | grep awstrack.me
[24.03-RELEASE][admin@GAFW]/root:

              My host IP which is 192.168.50.241 does show up in the block logs - showing just to verify that pfblk is doing its thing.

              
DNSBL-python,Aug 20 21:35:45,www.google-analytics.com,192.168.50.241,HSTS_A,TLD_A,DNSBL_Firebog_Malicious,google-analytics.com,DandelionSprouts,-
DNSBL-python,Aug 26 22:21:34,ocsp.digicert.cn,192.168.50.241,Python,TLD_A,DNSBL_TLD,cn,DNSBL_TLD,+
DNSBL-python,Aug 26 22:21:34,crl.digicert.cn,192.168.50.241,Python,TLD_A,DNSBL_TLD,cn,DNSBL_TLD,+
DNSBL-python,Aug 28 09:04:27,ocsp.dcocsp.cn,192.168.50.241,Python,TLD_A,DNSBL_TLD,cn,DNSBL_TLD,+
DNSBL-python,Aug 29 09:52:59,matching.truffle.bid,192.168.50.241,Python,TLD_A,DNSBL_TLD,bid,DNSBL_TLD,+
DNSBL-python,Sep 6 14:17:38,ocsp.dcocsp.cn,192.168.50.241,Python,TLD_A,DNSBL_TLD,cn,DNSBL_TLD,+
DNSBL-python,Sep 10 08:57:52,cdn.adguard.info,192.168.50.241,Python,TLD_A,DNSBL_TLD,info,DNSBL_TLD,+
DNSBL-python,Sep 12 17:43:14,matching.truffle.bid,192.168.50.241,Python,TLD_A,DNSBL_TLD,bid,DNSBL_TLD,+
DNSBL-python,Sep 16 13:58:21,ocsp.digicert.cn,192.168.50.241,Python,TLD_A,DNSBL_TLD,cn,DNSBL_TLD,+
DNSBL-python,Sep 16 13:58:21,crl.digicert.cn,192.168.50.241,Python,TLD_A,DNSBL_TLD,cn,DNSBL_TLD,+
DNSBL-python,Sep 16 14:36:42,ocsp.trust-provider.cn,192.168.50.241,Python,TLD_A,DNSBL_TLD,cn,DNSBL_TLD,+
DNSBL-python,Sep 18 10:47:30,ocsp.dcocsp.cn,192.168.50.241,Python,TLD_A,DNSBL_TLD,cn,DNSBL_TLD,+

              Firewall: NetGate,Palo Alto-VM,Juniper SRX
              Routing: Juniper, Arista, Cisco
              Switching: Juniper, Arista, Cisco
              Wireless: Unifi, Aruba IAP
              JNCIP,CCNP Enterprise

              johnpozJ GertjanG 2 Replies Last reply Reply Quote 0
              • johnpozJ
                johnpoz LAYER 8 Global Moderator @michmoor
                last edited by

                @michmoor well now that @Gertjan mentioned it, yup 0.0.0.0 as a response screams block

                An intelligent man is sometimes forced to be drunk to spend time with his fools
                If you get confused: Listen to the Music Play
                Please don't Chat/PM me for help, unless mod related
                SG-4860 24.03 | Lab VMs 2.7.2, 24.03

                1 Reply Last reply Reply Quote 0
                • GertjanG
                  Gertjan @michmoor
                  last edited by Gertjan

                  @michmoor said in DNS Resolver not resolving a specific hostname:

                  cat /var/log/pfblockerng/dnsbl.log | grep awstrack.me

                  Try this :

                  tail /var/log/pfblockerng/dnsbl.log | grep awstrack.me

                  or better (probably) :

                  tail -f /var/unbound/var/log/pfblockerng/dns | grep awstrack.me

                  Anyway, now its resolving for me, as I've "Group Policy" the IP of the PC I'm using right now, so a nslookup on my PC did work out, and the answer, the IP made it in the unbound cache, and from then then pfBlockerng is bypassed :(

                  I'm good for another cache trick to destroy the entry for awtrack.me using unbound-control or .... yeah ... restarting unbound again.

                  No "help me" PM's please. Use the forum, the community will thank you.
                  Edit : and where are the logs ??

                  M 1 Reply Last reply Reply Quote 0
                  • M
                    michmoor LAYER 8 Rebel Alliance @Gertjan
                    last edited by

                    @Gertjan

                    Ok i found it in the unified log but...its not hitting any block list which is why i excluded pfblocker from the analysis. Any reason why its failing to resolve still?

                    ]/var/log/pfblockerng: grep -ir awstrack.me
./unified.log:DNS-reply,Sep 18 10:41:42,servfail,HTTPS,HTTPS,Unk,hq4ypryg.r.us-west-2.awstrack.me,192.168.50.241,ServFail,unk
./unified.log:DNS-reply,Sep 18 10:41:42,servfail,HTTPS,HTTPS,Unk,hq4ypryg.r.us-west-2.awstrack.me,192.168.50.241,ServFail,unk
./unified.log:DNS-reply,Sep 18 10:42:09,servfail,HTTPS,HTTPS,Unk,hq4ypryg.r.us-west-2.awstrack.me,192.168.50.241,ServFail,unk
./unified.log:DNS-reply,Sep 18 10:42:09,servfail,HTTPS,HTTPS,Unk,hq4ypryg.r.us-west-2.awstrack.me,192.168.50.241,ServFail,unk
./unified.log:DNS-reply,Sep 18 10:45:49,servfail,HTTPS,HTTPS,Unk,hq4ypryg.r.us-west-2.awstrack.me,192.168.50.241,ServFail,unk
./unified.log:DNS-reply,Sep 18 10:45:49,servfail,HTTPS,HTTPS,Unk,hq4ypryg.r.us-west-2.awstrack.me,192.168.50.241,ServFail,unk
./unified.log:DNS-reply,Sep 18 10:45:57,servfail,HTTPS,HTTPS,Unk,hq4ypryg.r.us-west-2.awstrack.me,192.168.50.241,ServFail,unk
./unified.log:DNS-reply,Sep 18 10:45:57,servfail,HTTPS,HTTPS,Unk,hq4ypryg.r.us-west-2.awstrack.me,192.168.50.241,ServFail,unk
./unified.log:DNS-reply,Sep 18 10:46:38,servfail,HTTPS,HTTPS,Unk,hq4ypryg.r.us-west-2.awstrack.me,192.168.50.241,ServFail,unk
./unified.log:DNS-reply,Sep 18 10:46:38,servfail,HTTPS,HTTPS,Unk,hq4ypryg.r.us-west-2.awstrack.me,192.168.50.241,ServFail,unk
./unified.log:DNS-reply,Sep 18 10:47:01,servfail,AAAA,AAAA,Unk,hq4ypryg.r.us-west-2.awstrack.me,192.168.50.223,ServFail,unk
./unified.log:DNS-reply,Sep 18 10:47:01,servfail,AAAA,AAAA,Unk,hq4ypryg.r.us-west-2.awstrack.me,192.168.50.223,ServFail,unk
./unified.log:DNS-reply,Sep 18 10:47:01,servfail,AAAA,AAAA,Unk,hq4ypryg.r.us-west-2.awstrack.me,192.168.50.223,ServFail,unk
./unified.log:DNS-reply,Sep 18 10:47:01,servfail,AAAA,AAAA,Unk,hq4ypryg.r.us-west-2.awstrack.me,192.168.50.223,ServFail,unk
./unified.log:DNS-reply,Sep 18 10:47:01,servfail,AAAA,AAAA,Unk,hq4ypryg.r.us-west-2.awstrack.me,192.168.50.223,ServFail,unk
./unified.log:DNS-reply,Sep 18 10:47:01,servfail,AAAA,AAAA,Unk,hq4ypryg.r.us-west-2.awstrack.me,192.168.50.223,ServFail,unk
./unified.log:DNS-reply,Sep 18 10:47:09,servfail,AAAA,AAAA,Unk,awstrack.me,192.168.50.223,ServFail,unk
./unified.log:DNS-reply,Sep 18 10:47:09,servfail,AAAA,AAAA,Unk,awstrack.me,192.168.50.223,ServFail,unk
./unified.log:DNS-reply,Sep 18 10:47:09,servfail,AAAA,AAAA,Unk,awstrack.me,192.168.50.223,ServFail,unk
./unified.log:DNS-reply,Sep 18 10:47:09,servfail,AAAA,AAAA,Unk,awstrack.me,192.168.50.223,ServFail,unk
./unified.log:DNS-reply,Sep 18 10:47:09,servfail,AAAA,AAAA,Unk,awstrack.me,192.168.50.223,ServFail,unk
./unified.log:DNS-reply,Sep 18 10:47:09,servfail,AAAA,AAAA,Unk,awstrack.me,192.168.50.223,ServFail,unk
./unified.log:DNS-reply,Sep 18 10:49:26,resolver,A,A,60,hq4ypryg.r.us-west-2.awstrack.me,127.0.0.1,0.0.0.0,prv
./unified.log:DNS-reply,Sep 18 10:49:26,resolver,A,A,60,hq4ypryg.r.us-west-2.awstrack.me,127.0.0.1,0.0.0.0,prv
./unified.log:DNS-reply,Sep 18 10:49:26,resolver,A,A,60,hq4ypryg.r.us-west-2.awstrack.me,127.0.0.1,0.0.0.0,prv
./unified.log:DNS-reply,Sep 18 10:49:26,resolver,AAAA,AAAA,Unk,hq4ypryg.r.us-west-2.awstrack.me,127.0.0.1,ServFail,unk
./unified.log:DNS-reply,Sep 18 10:49:26,resolver,CNAME,CNAME,60,hq4ypryg.r.us-west-2.awstrack.me,127.0.0.1,0.0.0.0,prv
./unified.log:DNS-reply,Sep 18 11:17:27,resolver,A,A,60,hq4ypryg.r.us-west-2.awstrack.me,127.0.0.1,0.0.0.0,prv
./unified.log:DNS-reply,Sep 18 11:17:27,resolver,A,A,60,hq4ypryg.r.us-west-2.awstrack.me,127.0.0.1,0.0.0.0,prv
./unified.log:DNS-reply,Sep 18 11:17:27,resolver,A,A,60,hq4ypryg.r.us-west-2.awstrack.me,127.0.0.1,0.0.0.0,prv
./unified.log:DNS-reply,Sep 18 11:17:27,resolver,AAAA,AAAA,Unk,hq4ypryg.r.us-west-2.awstrack.me,127.0.0.1,ServFail,unk
./unified.log:DNS-reply,Sep 18 11:17:27,resolver,CNAME,CNAME,60,hq4ypryg.r.us-west-2.awstrack.me,127.0.0.1,0.0.0.0,prv
./unified.log:DNS-reply,Sep 18 12:23:09,reply,A,SOA,1800,awstrack.me.networkingtitan.com,192.168.50.241,SOA,unk
./unified.log:DNS-reply,Sep 18 12:23:09,reply,AAAA,SOA,1800,awstrack.me.networkingtitan.com,192.168.50.241,SOA,unk
./unified.log:DNS-reply,Sep 18 12:23:09,servfail,AAAA,AAAA,Unk,awstrack.me,192.168.50.241,ServFail,unk
./dns_reply.log:DNS-reply,Sep 18 10:41:42,servfail,HTTPS,HTTPS,Unk,hq4ypryg.r.us-west-2.awstrack.me,192.168.50.241,ServFail,unk
./dns_reply.log:DNS-reply,Sep 18 10:41:42,servfail,HTTPS,HTTPS,Unk,hq4ypryg.r.us-west-2.awstrack.me,192.168.50.241,ServFail,unk
./dns_reply.log:DNS-reply,Sep 18 10:42:09,servfail,HTTPS,HTTPS,Unk,hq4ypryg.r.us-west-2.awstrack.me,192.168.50.241,ServFail,unk
./dns_reply.log:DNS-reply,Sep 18 10:42:09,servfail,HTTPS,HTTPS,Unk,hq4ypryg.r.us-west-2.awstrack.me,192.168.50.241,ServFail,unk
./dns_reply.log:DNS-reply,Sep 18 10:45:49,servfail,HTTPS,HTTPS,Unk,hq4ypryg.r.us-west-2.awstrack.me,192.168.50.241,ServFail,unk
./dns_reply.log:DNS-reply,Sep 18 10:45:49,servfail,HTTPS,HTTPS,Unk,hq4ypryg.r.us-west-2.awstrack.me,192.168.50.241,ServFail,unk
./dns_reply.log:DNS-reply,Sep 18 10:45:57,servfail,HTTPS,HTTPS,Unk,hq4ypryg.r.us-west-2.awstrack.me,192.168.50.241,ServFail,unk
./dns_reply.log:DNS-reply,Sep 18 10:45:57,servfail,HTTPS,HTTPS,Unk,hq4ypryg.r.us-west-2.awstrack.me,192.168.50.241,ServFail,unk
./dns_reply.log:DNS-reply,Sep 18 10:46:38,servfail,HTTPS,HTTPS,Unk,hq4ypryg.r.us-west-2.awstrack.me,192.168.50.241,ServFail,unk
./dns_reply.log:DNS-reply,Sep 18 10:46:38,servfail,HTTPS,HTTPS,Unk,hq4ypryg.r.us-west-2.awstrack.me,192.168.50.241,ServFail,unk
./dns_reply.log:DNS-reply,Sep 18 10:47:01,servfail,AAAA,AAAA,Unk,hq4ypryg.r.us-west-2.awstrack.me,192.168.50.223,ServFail,unk
./dns_reply.log:DNS-reply,Sep 18 10:47:01,servfail,AAAA,AAAA,Unk,hq4ypryg.r.us-west-2.awstrack.me,192.168.50.223,ServFail,unk
./dns_reply.log:DNS-reply,Sep 18 10:47:01,servfail,AAAA,AAAA,Unk,hq4ypryg.r.us-west-2.awstrack.me,192.168.50.223,ServFail,unk
./dns_reply.log:DNS-reply,Sep 18 10:47:01,servfail,AAAA,AAAA,Unk,hq4ypryg.r.us-west-2.awstrack.me,192.168.50.223,ServFail,unk
./dns_reply.log:DNS-reply,Sep 18 10:47:01,servfail,AAAA,AAAA,Unk,hq4ypryg.r.us-west-2.awstrack.me,192.168.50.223,ServFail,unk
./dns_reply.log:DNS-reply,Sep 18 10:47:01,servfail,AAAA,AAAA,Unk,hq4ypryg.r.us-west-2.awstrack.me,192.168.50.223,ServFail,unk
./dns_reply.log:DNS-reply,Sep 18 10:47:09,servfail,AAAA,AAAA,Unk,awstrack.me,192.168.50.223,ServFail,unk
./dns_reply.log:DNS-reply,Sep 18 10:47:09,servfail,AAAA,AAAA,Unk,awstrack.me,192.168.50.223,ServFail,unk
./dns_reply.log:DNS-reply,Sep 18 10:47:09,servfail,AAAA,AAAA,Unk,awstrack.me,192.168.50.223,ServFail,unk
./dns_reply.log:DNS-reply,Sep 18 10:47:09,servfail,AAAA,AAAA,Unk,awstrack.me,192.168.50.223,ServFail,unk
./dns_reply.log:DNS-reply,Sep 18 10:47:09,servfail,AAAA,AAAA,Unk,awstrack.me,192.168.50.223,ServFail,unk
./dns_reply.log:DNS-reply,Sep 18 10:47:09,servfail,AAAA,AAAA,Unk,awstrack.me,192.168.50.223,ServFail,unk
./dns_reply.log:DNS-reply,Sep 18 10:49:26,resolver,A,A,60,hq4ypryg.r.us-west-2.awstrack.me,127.0.0.1,0.0.0.0,prv
./dns_reply.log:DNS-reply,Sep 18 10:49:26,resolver,A,A,60,hq4ypryg.r.us-west-2.awstrack.me,127.0.0.1,0.0.0.0,prv
./dns_reply.log:DNS-reply,Sep 18 10:49:26,resolver,A,A,60,hq4ypryg.r.us-west-2.awstrack.me,127.0.0.1,0.0.0.0,prv
./dns_reply.log:DNS-reply,Sep 18 10:49:26,resolver,AAAA,AAAA,Unk,hq4ypryg.r.us-west-2.awstrack.me,127.0.0.1,ServFail,unk
./dns_reply.log:DNS-reply,Sep 18 10:49:26,resolver,CNAME,CNAME,60,hq4ypryg.r.us-west-2.awstrack.me,127.0.0.1,0.0.0.0,prv
./dns_reply.log:DNS-reply,Sep 18 11:17:27,resolver,A,A,60,hq4ypryg.r.us-west-2.awstrack.me,127.0.0.1,0.0.0.0,prv
./dns_reply.log:DNS-reply,Sep 18 11:17:27,resolver,A,A,60,hq4ypryg.r.us-west-2.awstrack.me,127.0.0.1,0.0.0.0,prv
./dns_reply.log:DNS-reply,Sep 18 11:17:27,resolver,A,A,60,hq4ypryg.r.us-west-2.awstrack.me,127.0.0.1,0.0.0.0,prv
./dns_reply.log:DNS-reply,Sep 18 11:17:27,resolver,AAAA,AAAA,Unk,hq4ypryg.r.us-west-2.awstrack.me,127.0.0.1,ServFail,unk
./dns_reply.log:DNS-reply,Sep 18 11:17:27,resolver,CNAME,CNAME,60,hq4ypryg.r.us-west-2.awstrack.me,127.0.0.1,0.0.0.0,prv
./dns_reply.log:DNS-reply,Sep 18 12:23:09,reply,A,SOA,1800,awstrack.me.networkingtitan.com,192.168.50.241,SOA,unk
./dns_reply.log:DNS-reply,Sep 18 12:23:09,reply,AAAA,SOA,1800,awstrack.me.networkingtitan.com,192.168.50.241,SOA,unk
./dns_reply.log:DNS-reply,Sep 18 12:23:09,servfail,AAAA,AAAA,Unk,awstrack.me,192.168.50.241,ServFail,unk

                    Firewall: NetGate,Palo Alto-VM,Juniper SRX
                    Routing: Juniper, Arista, Cisco
                    Switching: Juniper, Arista, Cisco
                    Wireless: Unifi, Aruba IAP
                    JNCIP,CCNP Enterprise

                    GertjanG 1 Reply Last reply Reply Quote 0
                    • GertjanG
                      Gertjan @michmoor
                      last edited by Gertjan

                      When I see this ( many identical fragments in the log ) :

                      @michmoor said in DNS Resolver not resolving a specific hostname:

                      resolver,A,A,60,hq4ypryg.r.us-west-2.awstrack.me,127.0.0.1,0.0.0.0,prv

                      Then the resolver got a question about 60,hq4ypryg.r.us-west-2.awstrack.me for an A record, coming in into its 127.0.0.1 and it had an answer (and not a fail !) : 0.0.0.0
                      For me : 0.0.0.0 = you've been "DNSBL".

                      No "help me" PM's please. Use the forum, the community will thank you.
                      Edit : and where are the logs ??

                      M 1 Reply Last reply Reply Quote 0
                      • M
                        michmoor LAYER 8 Rebel Alliance @Gertjan
                        last edited by

                        @Gertjan Ok...Figured it out. It was due to logging settings

                        Previous global letting setting wouldn't have shown me the blocks

                        feca942d-38a8-4749-a922-7f2e5815f008-image.png

                        After changing, that and reloading....its in the blacklist you specified.

                        7cc211f0-79e6-4bfb-bd6c-0edb9e54c2c8-image.png

                        Firewall: NetGate,Palo Alto-VM,Juniper SRX
                        Routing: Juniper, Arista, Cisco
                        Switching: Juniper, Arista, Cisco
                        Wireless: Unifi, Aruba IAP
                        JNCIP,CCNP Enterprise

                        bmeeksB 1 Reply Last reply Reply Quote 1
                        • bmeeksB
                          bmeeks @michmoor
                          last edited by

                          @michmoor said in DNS Resolver not resolving a specific hostname:

                          Ok...Figured it out. It was due to logging settings

                          Previous global letting setting wouldn't have shown me the blocks

                          Lesson to be learned ... 🙂 -

                          Anytime you have a blocking package installed (pfBlockerNG, DNSBL, Snort, or Suricata) and something acts weird or does not work, 99 times out of 100 it's going to be the blocking package(s) that is the cause.

                          1 Reply Last reply Reply Quote 1
                          • First post
                            Last post