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

    I need HELP on DNS RESOLVER!

    Scheduled Pinned Locked Moved DHCP and DNS
    78 Posts 6 Posters 15.6k Views
    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.
    • GertjanG
      Gertjan
      last edited by Gertjan

      I know ;)

      From my pfSense and one Windows PC, it resolves just fine - although I got back an IP like 72.21.91.97
      and after that another IP : 93.184.220.97

      I went to Services => DNS Resolver Advanced => Settings => Log level and set it to level 3.

      Result : https://pastebin.com/51vZi2xX which proofs my Resolver received the requests from my Windows device, and unbound starts to doing "the thing ....".

      Btw : my LAN and other OPTx firewall rules :
      0_1535981921463_3c8affc8-943f-4d54-a374-da873ee175a7-image.png

      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
      • E
        emirefek
        last edited by emirefek

        Hehe I caught something nice in logs. @Gertjan @johnpoz @yellowbrick
        I think dns resolver can solve domain. But It cannot stream it to local network. because its cname when I look dns resolver logs. no output about "cs71.wac.edgecastcdn.net" no one try to reach server. They are stuck on "ubnt.i.lithium.com" after that I try to solve "cs71.wac.edgecastcdn.net" on LAN side and pfsense dnslookup and you will see screenshots below no one can solve this hostname pfsense box too.

        0_1535981839392_dnsresolver-log.PNG
        0_1535982490821_dnslookup-pfsensebox.PNG

        After that I try ping and nslookup and dig to "cs71.wac.edgecastcdn.net" on lan, wlan side no one can reach because box cannot solve this hostname. But Im getting logs about this now domain.

        0_1535982167964_dnsresolver-log2.PNG
        0_1535982748540_dnsresolver-log-edgecast.PNG

        In this logs I get this IP and I cannot found something usefull same outputs everywhere related this hostname. Then I try to reach this IP.
        PING ON PFSENSE BOX:
        PING 192.41.162.30 (192.41.162.30): 56 data bytes
        64 bytes from 192.41.162.30: icmp_seq=0 ttl=54 time=63.971 ms
        64 bytes from 192.41.162.30: icmp_seq=1 ttl=54 time=63.075 ms
        64 bytes from 192.41.162.30: icmp_seq=2 ttl=54 time=63.915 ms
        --- 192.41.162.30 ping statistics ---
        3 packets transmitted, 3 packets received, 0.0% packet loss
        round-trip min/avg/max/stddev = 63.075/63.654/63.971/0.410 ms

        THEN I TRY TRACEROUTE ON PfSense Box:
        1 81.212.171.204.static.turktelekom.com.tr (81.212.171.204) 5.063 ms 8.821 ms 5.137 ms
        2 93.155.0.146 (93.155.0.146) 5.936 ms 5.808 ms 5.478 ms
        3 81.212.108.162.static.turktelekom.com.tr (81.212.108.162) 5.954 ms 6.220 ms 6.479 ms
        4 16-bursa-h2-1---16-bursa-t3-3.statik.turktelekom.com.tr (81.212.244.145) 6.501 ms 7.990 ms 6.530 ms
        5 00-gayrettepe-xrs-t2-1---16-bursa-h2-1.statik.turktelekom.com.tr (81.212.248.78) 14.719 ms 14.797 ms 14.508 ms
        6 305-vie-col-3---00-gayrettepe-xrs-t2-1.statik.turktelekom.com.tr (212.156.140.116) 57.184 ms
        305-vie-col-3---00-gayrettepe-xrs-t2-1.statik.turktelekom.com.tr (212.156.140.188) 54.735 ms 62.927 ms
        7 83.231.187.25 (83.231.187.25) 59.980 ms 59.758 ms 60.243 ms
        8 ae-3.r01.vienat01.at.bb.gin.ntt.net (129.250.2.37) 57.501 ms 58.023 ms 57.462 ms
        9 ae-7.r25.amstnl02.nl.bb.gin.ntt.net (129.250.2.111) 62.239 ms 61.583 ms 71.028 ms
        10 ae-8.r03.amstnl02.nl.bb.gin.ntt.net (129.250.2.109) 62.696 ms 62.066 ms 62.185 ms
        11 81.20.65.178 (81.20.65.178) 61.976 ms 61.782 ms 61.981 ms
        12 * * *
        13 * * *
        14 * * *
        15 * * *
        16 * * *
        17 * * *
        18 * * *
        EDIT: TurkTelekom is My ISP

        (Its little dirty. Our team is working on office.)Resolver log: https://pastebin.com/1db0p7wt

        I Can "81.20.65.178" reach it but I think it isnt related with edgecast. I think Its for dns stufs. Im stuck in here If you need more informaiton or logs please tell me I need to fix that issue

        1 Reply Last reply Reply Quote 0
        • E
          emirefek
          last edited by

          Guys @Gertjan @johnpoz @yellowbrick I need your help? Nothing fixed yet.

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

            @emirefek said in I need HELP on DNS RESOLVER!:

            ubnt.i.lithium.com"

            Did another test just now :
            Flushed dns on my PC.
            Flushed Resolver cache (by setting log details to level 2).
            On my PC :

            C:\Documents and Settings\Gertjan.BUREAU>ipconfig /flushdns

Configuration IP de Windows

Cache de résolution DNS vidé.

C:\Documents and Settings\Gertjan.BUREAU>nslookup
Serveur par dÚfaut :  pfsense.brit-hotel-fumel.net
Address:  192.168.1.1

> ubnt.i.lithium.com
Serveur :  pfsense.brit-hotel-fumel.net
Address:  192.168.1.1

Réponse ne faisant pas autorité :
Nom :    cs71.wac.edgecastcdn.net
Address:  93.184.220.97
Aliases:  ubnt.i.lithium.com.

            This is what pfSense told me (read from bottom to top) :

            09-11-2018	17:12:44	Daemon.Info	192.168.1.1	Sep 11 17:12:46 unbound: [96547:0] info: query response was nodata ANSWER
09-11-2018	17:12:44	Daemon.Info	192.168.1.1	Sep 11 17:12:46 unbound: [96547:0] info: reply from <lithium.com.> 208.74.204.2#53
09-11-2018	17:12:44	Daemon.Info	192.168.1.1	Sep 11 17:12:46 unbound: [96547:0] info: response for ns4.lithium.com. AAAA IN
09-11-2018	17:12:44	Daemon.Info	192.168.1.1	Sep 11 17:12:46 unbound: [96547:0] info: Verified that unsigned response is INSECURE
09-11-2018	17:12:44	Daemon.Info	192.168.1.1	Sep 11 17:12:46 unbound: [96547:0] info: NSEC3s for the referral proved no DS.
09-11-2018	17:12:44	Daemon.Info	192.168.1.1	Sep 11 17:12:46 unbound: [96547:0] info: Verified that unsigned response is INSECURE
09-11-2018	17:12:44	Daemon.Info	192.168.1.1	Sep 11 17:12:46 unbound: [96547:0] info: NSEC3s for the referral proved no DS.
09-11-2018	17:12:44	Daemon.Info	192.168.1.1	Sep 11 17:12:46 unbound: [96547:0] info: query response was ANSWER
09-11-2018	17:12:44	Daemon.Info	192.168.1.1	Sep 11 17:12:46 unbound: [96547:0] info: reply from <edgecastcdn.net.> 72.21.80.6#53
09-11-2018	17:12:44	Daemon.Info	192.168.1.1	Sep 11 17:12:46 unbound: [96547:0] info: response for ubnt.i.lithium.com. A IN
09-11-2018	17:12:44	Daemon.Info	192.168.1.1	Sep 11 17:12:46 unbound: [96547:0] info: query response was REFERRAL
09-11-2018	17:12:44	Daemon.Info	192.168.1.1	Sep 11 17:12:46 unbound: [96547:0] info: reply from <net.> 2001:503:231d::2:30#53
09-11-2018	17:12:44	Daemon.Info	192.168.1.1	Sep 11 17:12:46 unbound: [96547:0] info: response for ubnt.i.lithium.com. A IN
09-11-2018	17:12:44	Daemon.Info	192.168.1.1	Sep 11 17:12:46 unbound: [96547:0] info: query response was nodata ANSWER
09-11-2018	17:12:44	Daemon.Info	192.168.1.1	Sep 11 17:12:46 unbound: [96547:0] info: reply from <lithium.com.> 208.94.148.13#53
09-11-2018	17:12:44	Daemon.Info	192.168.1.1	Sep 11 17:12:46 unbound: [96547:0] info: response for ns5.lithium.com. AAAA IN
09-11-2018	17:12:44	Daemon.Info	192.168.1.1	Sep 11 17:12:46 unbound: [96547:0] info: resolving net. DNSKEY IN
09-11-2018	17:12:44	Daemon.Info	192.168.1.1	Sep 11 17:12:46 unbound: [96547:0] info: resolving ubnt.i.lithium.com. A IN
09-11-2018	17:12:44	Daemon.Info	192.168.1.1	Sep 11 17:12:46 unbound: [96547:0] info: query response was CNAME
09-11-2018	17:12:44	Daemon.Info	192.168.1.1	Sep 11 17:12:46 unbound: [96547:0] info: reply from <lithium.com.> 208.80.124.13#53
09-11-2018	17:12:44	Daemon.Info	192.168.1.1	Sep 11 17:12:46 unbound: [96547:0] info: response for ubnt.i.lithium.com. A IN
09-11-2018	17:12:44	Daemon.Info	192.168.1.1	Sep 11 17:12:46 unbound: [96547:0] info: resolving ns4.lithium.com. AAAA IN
09-11-2018	17:12:44	Daemon.Info	192.168.1.1	Sep 11 17:12:46 unbound: [96547:0] info: resolving ns5.lithium.com. AAAA IN
09-11-2018	17:12:44	Daemon.Info	192.168.1.1	Sep 11 17:12:46 unbound: [96547:0] info: query response was REFERRAL
09-11-2018	17:12:44	Daemon.Info	192.168.1.1	Sep 11 17:12:46 unbound: [96547:0] info: reply from <com.> 192.43.172.30#53
09-11-2018	17:12:44	Daemon.Info	192.168.1.1	Sep 11 17:12:46 unbound: [96547:0] info: response for ubnt.i.lithium.com. A IN
09-11-2018	17:12:44	Daemon.Info	192.168.1.1	Sep 11 17:12:45 unbound: [96547:0] info: resolving com. DNSKEY IN
09-11-2018	17:12:44	Daemon.Info	192.168.1.1	Sep 11 17:12:45 unbound: [96547:0] info: resolving ubnt.i.lithium.com. A IN

            Looks good to me. Not sure when reading the logs, but nslookup on my PC gave an answer.

            Check if you have the same.
            If some device (PC) doesn't show DNS logs on pfSense, then that device has no DNS (so : no answer!) or that device doesn't use pfSense as a DNS.

            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
              last edited by

              They do have a bit of a problem to be honest with their setup... So the roots for .net only show 2 NS for that domain

              dig @e.gtld-servers.net edgecastcdn.net NS                     

; <<>> DiG 9.9.5-3ubuntu0.17-Ubuntu <<>> @e.gtld-servers.net edgecastcdn.net NS
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16422
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 5
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;edgecastcdn.net.               IN      NS

;; AUTHORITY SECTION:
edgecastcdn.net.        172800  IN      NS      ns1.edgecastcdn.net.
edgecastcdn.net.        172800  IN      NS      ns2.edgecastcdn.net.

;; ADDITIONAL SECTION:
ns1.edgecastcdn.net.    172800  IN      AAAA    2606:2800:1::5
ns1.edgecastcdn.net.    172800  IN      A       72.21.80.5
ns2.edgecastcdn.net.    172800  IN      AAAA    2606:2800:1::6
ns2.edgecastcdn.net.    172800  IN      A       72.21.80.6

;; Query time: 17 msec
;; SERVER: 2001:502:1ca1::30#53(2001:502:1ca1::30)
;; WHEN: Tue Sep 11 12:39:14 CDT 2018
;; MSG SIZE  rcvd: 168

              But if you ask the SOA for that domain for its NS.. you get back 4 of them.

              dig @ns1.edgecastcdn.net edgecastcdn.net NS

; <<>> DiG 9.9.5-3ubuntu0.17-Ubuntu <<>> @ns1.edgecastcdn.net edgecastcdn.net NS
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22695
;; flags: qr aa rd; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 9
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;edgecastcdn.net.               IN      NS

;; ANSWER SECTION:
edgecastcdn.net.        3600    IN      NS      ns1.edgecastcdn.net.
edgecastcdn.net.        3600    IN      NS      ns2.edgecastcdn.net.
edgecastcdn.net.        3600    IN      NS      ns3.edgecastcdn.net.
edgecastcdn.net.        3600    IN      NS      ns4.edgecastcdn.net.

;; ADDITIONAL SECTION:
ns1.edgecastcdn.net.    172800  IN      AAAA    2606:2800:1::5
ns2.edgecastcdn.net.    172800  IN      AAAA    2606:2800:1::6
ns3.edgecastcdn.net.    3600    IN      AAAA    2606:2800:e::5
ns4.edgecastcdn.net.    3600    IN      AAAA    2606:2800:e::6
ns1.edgecastcdn.net.    172800  IN      A       72.21.80.5
ns2.edgecastcdn.net.    172800  IN      A       72.21.80.6
ns3.edgecastcdn.net.    3600    IN      A       192.229.254.5
ns4.edgecastcdn.net.    3600    IN      A       192.229.254.6

;; Query time: 10 msec
;; SERVER: 2606:2800:1::5#53(2606:2800:1::5)
;; WHEN: Tue Sep 11 12:41:52 CDT 2018
;; MSG SIZE  rcvd: 292

              This really shoudn't stop you from resolving - but it does reflect a lack of proper dns control..

              Did you run the dig +trace command pfsense?

              [2.4.3-RELEASE][root@sg4860.local.lan]/: dig cs71.wac.edgecastcdn.net +trace +nodnssec

; <<>> DiG 9.11.2-P1 <<>> cs71.wac.edgecastcdn.net +trace +nodnssec
;; global options: +cmd
.                       485599  IN      NS      f.root-servers.net.
.                       485599  IN      NS      d.root-servers.net.
.                       485599  IN      NS      i.root-servers.net.
.                       485599  IN      NS      g.root-servers.net.
.                       485599  IN      NS      c.root-servers.net.
.                       485599  IN      NS      e.root-servers.net.
.                       485599  IN      NS      l.root-servers.net.
.                       485599  IN      NS      h.root-servers.net.
.                       485599  IN      NS      k.root-servers.net.
.                       485599  IN      NS      j.root-servers.net.
.                       485599  IN      NS      m.root-servers.net.
.                       485599  IN      NS      a.root-servers.net.
.                       485599  IN      NS      b.root-servers.net.
;; Received 239 bytes from 127.0.0.1#53(127.0.0.1) in 0 ms

net.                    172800  IN      NS      a.gtld-servers.net.
net.                    172800  IN      NS      b.gtld-servers.net.
net.                    172800  IN      NS      c.gtld-servers.net.
net.                    172800  IN      NS      d.gtld-servers.net.
net.                    172800  IN      NS      e.gtld-servers.net.
net.                    172800  IN      NS      f.gtld-servers.net.
net.                    172800  IN      NS      g.gtld-servers.net.
net.                    172800  IN      NS      h.gtld-servers.net.
net.                    172800  IN      NS      i.gtld-servers.net.
net.                    172800  IN      NS      j.gtld-servers.net.
net.                    172800  IN      NS      k.gtld-servers.net.
net.                    172800  IN      NS      l.gtld-servers.net.
net.                    172800  IN      NS      m.gtld-servers.net.
;; Received 846 bytes from 2001:500:1::53#53(h.root-servers.net) in 106 ms

edgecastcdn.net.        172800  IN      NS      ns1.edgecastcdn.net.
edgecastcdn.net.        172800  IN      NS      ns2.edgecastcdn.net.
;; Received 177 bytes from 192.5.6.30#53(a.gtld-servers.net) in 39 ms

cs71.wac.edgecastcdn.net. 3600  IN      A       72.21.91.97
;; Received 69 bytes from 72.21.80.5#53(ns1.edgecastcdn.net) in 11 ms

[2.4.3-RELEASE][root@sg4860.local.lan]/:

              This will tell you if pfsense would have a problem with resolving it.. I added the +nodnssec option to make the trace look cleaner - ie not include the dnssec info that roots and .net servers hand out

              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.11 | Lab VMs 2.8, 24.11

              1 Reply Last reply Reply Quote 1
              • GertjanG
                Gertjan
                last edited by

                Things didn't get any better this morning : https://zonemaster.iis.se/?resultid=87deb85f04a58f9e

                @emirefek : what about testing google.com *** ? So we can focus on your issues, not the one of the guy with severe DNS problems ?

                *** well, maybe google.com isn't perfect neither. This one is.

                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
                • E
                  emirefek
                  last edited by

                  @johnpoz
                  I typed your commands one by one and these are my outputs. And all outs from pfsense boxes comand prompt

                  dig @e.gtld-servers.net edgecastcdn.net NS

                  ; <<>> DiG 9.11.2-P1 <<>> @e.gtld-servers.net edgecastcdn.net NS
; (2 servers found)
;; global options: +cmd
;; connection timed out; no servers could be reached

                  dig @ns1.edgecastcdn.net edgecastcdn.net NS

                  dig: couldn't get address for 'ns1.edgecastcdn.net': not found

                  dig cs71.wac.edgecastcdn.net +trace +nodnssec

                  ; <<>> DiG 9.11.2-P1 <<>> cs71.wac.edgecastcdn.net +trace +nodnssec
;; global options: +cmd
.			24997	IN	NS	m.root-servers.net.
.			24997	IN	NS	g.root-servers.net.
.			24997	IN	NS	a.root-servers.net.
.			24997	IN	NS	j.root-servers.net.
.			24997	IN	NS	l.root-servers.net.
.			24997	IN	NS	d.root-servers.net.
.			24997	IN	NS	k.root-servers.net.
.			24997	IN	NS	b.root-servers.net.
.			24997	IN	NS	i.root-servers.net.
.			24997	IN	NS	h.root-servers.net.
.			24997	IN	NS	c.root-servers.net.
.			24997	IN	NS	f.root-servers.net.
.			24997	IN	NS	e.root-servers.net.
;; Received 811 bytes from 127.0.0.1#53(127.0.0.1) in 0 ms

;; connection timed out; no servers could be reached

                  these are my results. I dont know but I cannot solve that damn domain.
                  And little info my setup on vmware esxi with pppoe

                  1 Reply Last reply Reply Quote 0
                  • E
                    emirefek
                    last edited by

                    @Gertjan I can solve this domain mate. This output from pfsense box.

                    dig test-domaine.fr

                    ; <<>> DiG 9.11.2-P1 <<>> test-domaine.fr
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38644
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;test-domaine.fr.		IN	A

;; ANSWER SECTION:
test-domaine.fr.	10092	IN	A	5.196.43.182

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri Sep 14 12:56:48 +03 2018
;; MSG SIZE  rcvd: 60
                    1 Reply Last reply Reply Quote 0
                    • GertjanG
                      Gertjan
                      last edited by

                      Logic ☺ I'm the DNS administrator of that domain.

                      But your test tells me that your Resolver (DNS) works fine.
                      For what it's worth : when you setup pfSense (that is : assign LAN, WAN) and then you set up your WAN interface any device on your LAN should be able to access the net with any troubles.
                      Initially : do not touch firewall rules, VLAN's, DNS, nothing.

                      Btw : again : you are not responsible for not resolving of sub domains. The fact that something works on this side of the planet doesn't mean it isn't broken on your side.
                      Seek contact with the guy that manages ubnt.i.lithium.com - or put in a DNS host over ride.

                      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
                        last edited by

                        looks to me like you can not talk to roots..

                        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.11 | Lab VMs 2.8, 24.11

                        E 1 Reply Last reply Reply Quote 1
                        • E
                          emirefek @johnpoz
                          last edited by

                          @johnpoz I can talk with blabla.root-servers.net. I try 5 or 6 of them with random choose.

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

                            Then why does your trace not get an answer back ??

                            You should of gotten back the next level - the NS for .net when you did your trace..

                            example
                            net. 172800 IN NS k.gtld-servers.net.
                            net. 172800 IN NS l.gtld-servers.net.
                            net. 172800 IN NS m.gtld-servers.net.
                            ;; Received 846 bytes from 2001:500:1::53#53(h.root-servers.net) in 106 ms

                            Mine talked via ipv6 when I did the trace - but ipv4 would do the same thing.. You just stopped at roots..

                            How did you test talking to them - a ping or an actual dns query?

                            example

                            C:\>dig @m.root-servers.net net NS

; <<>> DiG 9.12.2 <<>> @m.root-servers.net net NS
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23008
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 13, ADDITIONAL: 27
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;net.                           IN      NS

;; AUTHORITY SECTION:
net.                    172800  IN      NS      m.gtld-servers.net.
net.                    172800  IN      NS      i.gtld-servers.net.
net.                    172800  IN      NS      a.gtld-servers.net.
net.                    172800  IN      NS      h.gtld-servers.net.
net.                    172800  IN      NS      k.gtld-servers.net.
net.                    172800  IN      NS      b.gtld-servers.net.
net.                    172800  IN      NS      c.gtld-servers.net.
net.                    172800  IN      NS      l.gtld-servers.net.
net.                    172800  IN      NS      g.gtld-servers.net.
net.                    172800  IN      NS      d.gtld-servers.net.
net.                    172800  IN      NS      j.gtld-servers.net.
net.                    172800  IN      NS      f.gtld-servers.net.
net.                    172800  IN      NS      e.gtld-servers.net.

;; ADDITIONAL SECTION:
a.gtld-servers.net.     172800  IN      A       192.5.6.30
b.gtld-servers.net.     172800  IN      A       192.33.14.30
c.gtld-servers.net.     172800  IN      A       192.26.92.30
d.gtld-servers.net.     172800  IN      A       192.31.80.30
e.gtld-servers.net.     172800  IN      A       192.12.94.30
f.gtld-servers.net.     172800  IN      A       192.35.51.30
g.gtld-servers.net.     172800  IN      A       192.42.93.30
h.gtld-servers.net.     172800  IN      A       192.54.112.30
i.gtld-servers.net.     172800  IN      A       192.43.172.30
j.gtld-servers.net.     172800  IN      A       192.48.79.30
k.gtld-servers.net.     172800  IN      A       192.52.178.30
l.gtld-servers.net.     172800  IN      A       192.41.162.30
m.gtld-servers.net.     172800  IN      A       192.55.83.30
a.gtld-servers.net.     172800  IN      AAAA    2001:503:a83e::2:30
b.gtld-servers.net.     172800  IN      AAAA    2001:503:231d::2:30
c.gtld-servers.net.     172800  IN      AAAA    2001:503:83eb::30
d.gtld-servers.net.     172800  IN      AAAA    2001:500:856e::30
e.gtld-servers.net.     172800  IN      AAAA    2001:502:1ca1::30
f.gtld-servers.net.     172800  IN      AAAA    2001:503:d414::30
g.gtld-servers.net.     172800  IN      AAAA    2001:503:eea3::30
h.gtld-servers.net.     172800  IN      AAAA    2001:502:8cc::30
i.gtld-servers.net.     172800  IN      AAAA    2001:503:39c1::30
j.gtld-servers.net.     172800  IN      AAAA    2001:502:7094::30
k.gtld-servers.net.     172800  IN      AAAA    2001:503:d2d::30
l.gtld-servers.net.     172800  IN      AAAA    2001:500:d937::30
m.gtld-servers.net.     172800  IN      AAAA    2001:501:b1f9::30

;; Query time: 77 msec
;; SERVER: 202.12.27.33#53(202.12.27.33)
;; WHEN: Fri Sep 14 08:03:45 Central Daylight Time 2018
;; MSG SIZE  rcvd: 825

                            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.11 | Lab VMs 2.8, 24.11

                            1 Reply Last reply Reply Quote 1
                            • E
                              emirefek
                              last edited by emirefek

                              @johnpoz said in I need HELP on DNS RESOLVER!:

                              @m.root-servers.net net NS

                              This output from my pfsense box. But I cannot talk it from my centos server and Im sure my centos dns settings are pointing my pfsense box.

                              dig @m.root-servers.net net NS

                              ; <<>> DiG 9.11.2-P1 <<>> @m.root-servers.net net NS
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10472
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 13, ADDITIONAL: 27
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;net.				IN	NS

;; AUTHORITY SECTION:
net.			172800	IN	NS	l.gtld-servers.net.
net.			172800	IN	NS	b.gtld-servers.net.
net.			172800	IN	NS	h.gtld-servers.net.
net.			172800	IN	NS	i.gtld-servers.net.
net.			172800	IN	NS	d.gtld-servers.net.
net.			172800	IN	NS	e.gtld-servers.net.
net.			172800	IN	NS	f.gtld-servers.net.
net.			172800	IN	NS	a.gtld-servers.net.
net.			172800	IN	NS	m.gtld-servers.net.
net.			172800	IN	NS	c.gtld-servers.net.
net.			172800	IN	NS	k.gtld-servers.net.
net.			172800	IN	NS	j.gtld-servers.net.
net.			172800	IN	NS	g.gtld-servers.net.

;; ADDITIONAL SECTION:
a.gtld-servers.net.	172800	IN	A	192.5.6.30
b.gtld-servers.net.	172800	IN	A	192.33.14.30
c.gtld-servers.net.	172800	IN	A	192.26.92.30
d.gtld-servers.net.	172800	IN	A	192.31.80.30
e.gtld-servers.net.	172800	IN	A	192.12.94.30
f.gtld-servers.net.	172800	IN	A	192.35.51.30
g.gtld-servers.net.	172800	IN	A	192.42.93.30
h.gtld-servers.net.	172800	IN	A	192.54.112.30
i.gtld-servers.net.	172800	IN	A	192.43.172.30
j.gtld-servers.net.	172800	IN	A	192.48.79.30
k.gtld-servers.net.	172800	IN	A	192.52.178.30
l.gtld-servers.net.	172800	IN	A	192.41.162.30
m.gtld-servers.net.	172800	IN	A	192.55.83.30
a.gtld-servers.net.	172800	IN	AAAA	2001:503:a83e::2:30
b.gtld-servers.net.	172800	IN	AAAA	2001:503:231d::2:30
c.gtld-servers.net.	172800	IN	AAAA	2001:503:83eb::30
d.gtld-servers.net.	172800	IN	AAAA	2001:500:856e::30
e.gtld-servers.net.	172800	IN	AAAA	2001:502:1ca1::30
f.gtld-servers.net.	172800	IN	AAAA	2001:503:d414::30
g.gtld-servers.net.	172800	IN	AAAA	2001:503:eea3::30
h.gtld-servers.net.	172800	IN	AAAA	2001:502:8cc::30
i.gtld-servers.net.	172800	IN	AAAA	2001:503:39c1::30
j.gtld-servers.net.	172800	IN	AAAA	2001:502:7094::30
k.gtld-servers.net.	172800	IN	AAAA	2001:503:d2d::30
l.gtld-servers.net.	172800	IN	AAAA	2001:500:d937::30
m.gtld-servers.net.	172800	IN	AAAA	2001:501:b1f9::30

;; Query time: 84 msec
;; SERVER: 202.12.27.33#53(202.12.27.33)
;; WHEN: Fri Sep 14 16:06:49 +03 2018
;; MSG SIZE  rcvd: 825

                              Output from centos:

                              [root@ekcentos ~]# dig @m.root-servers.net net NS

; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7_5.1 <<>> @m.root-servers.net net NS
; (2 servers found)
;; global options: +cmd
;; connection timed out; no servers could be reached
[root@ekcentos ~]#

                              EDIT:I blocked all other dns servers to LAN side from rules section when I do that centos cannot solve that hostname but when I allow all dns servers to lan side centos can solve this domain too.

                              1 Reply Last reply Reply Quote 0
                              • nodauN
                                nodau
                                last edited by

                                one question? are you using carp? if so, use the carp vips on dns resolver. for outbound interface you only need localhost.

                                Norman

                                virtualized pfSense 2.7.2 HA-Cluster on vsphere 8

                                E 1 Reply Last reply Reply Quote 0
                                • E
                                  emirefek @nodau
                                  last edited by

                                  @bahsig No Im not my setup is very simple. 1 WAN(PPPOE) - and 2 LAN (one of them for WIFIaps)

                                  I seeted up my box with that tutorial: https://www.youtube.com/watch?v=RrQrt8r_uYg

                                  And my plugins are pfblocker, snort and squid but I didnt configure it yet.

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

                                    So your problem has nothing to do with dns it seems like, but more your dns rules?

                                    Lets see these rules for your centos box network interface on pfsense..

                                    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.11 | Lab VMs 2.8, 24.11

                                    E 1 Reply Last reply Reply Quote 0
                                    • E
                                      emirefek @johnpoz
                                      last edited by

                                      @johnpoz
                                      here they are I block all other dns servers because of I dont want to clients pass pfblocker with other dns servers.
                                      0_1536932941642_LANrules.PNG

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

                                        @emirefek said in I need HELP on DNS RESOLVER!:

                                        EDIT:I blocked all other dns servers to LAN side from rules section when I do that centos cannot solve that hostname but when I allow all dns servers to lan side centos

                                        Your DNS ! ONLY ! to pfSEnse rule is UDP only .... 👎

                                        Read this https://serverfault.com/questions/404840/when-do-dns-queries-use-tcp-instead-of-udp and start slapping yourself.

                                        Act upon this information (and also activate DNSSEC, it will work this time ^^).

                                        edit : https://en.wikipedia.org/wiki/Domain_Name_System#Protocol_transport - see "DNS Protocol transport"

                                        edit : tip : Instead of "192.168.1.1" as a destination address, use "LAN Address". This will protect you for the next pitfall : the day you introduce IPv6.

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

                                        E 1 Reply Last reply Reply Quote 0
                                        • E
                                          emirefek @Gertjan
                                          last edited by emirefek

                                          @gertjan Oh. I change it to TCP/UDP and I can solve it now on centos. And I was enable DNSSEC now and I change To LAN Address on rules section.

                                          But I cannot solve damn edgecastcdn.net anyway.

                                          [root@ekcentos ~]# dig @e.gtld-servers.net edgecastcdn.net NS

; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7_5.1 <<>> @e.gtld-servers.net edgecastcdn.net NS
; (2 servers found)
;; global options: +cmd
;; connection timed out; no servers could be reached
[root@ekcentos ~]# dig @e.gtld-servers.net edgecastcdn.net NS
^C[root@ekcentos ~]# dig @ns1.edgecastcdn.net edgecastcdn.net NS
^C^C^C^Cdig: couldn't get address for 'ns1.edgecastcdn.net': not found
[root@ekcentos ~]#
                                          1 Reply Last reply Reply Quote 0
                                          • GertjanG
                                            Gertjan
                                            last edited by

                                            @emirefek said in I need HELP on DNS RESOLVER!:

                                            ig @ns1.edgecastcdn.net edgecastcdn.net NS

                                            Possible that you test also with another PC with some Microsoft OS on your LAN - and then use the 'dig' of Microsoft : nslookup.
                                            Just to be sure that your Centos does things as they should.

                                            Btw : try also disabling for some time your rule number 3 (the DNS block rule).

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

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