Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

Could help me to solve the bind software problem? I installed the bind SW on my redhat server, the version of bind is BIND 9.7.1-P2. The bind SW cannot query some domains, example nhaban.com, themix-org.mail.eo.outlook.com,.. When I used google dns (8.8.8.8), I can query these domains.

Here are some traces of dig command

[root@dns2 etc]# dig @117.120.24.4 +trace themix-org.mail.eo.outlook.com

; <<>> DiG 9.2.5 <<>> @117.120.24.4 +trace themix-org.mail.eo.outlook.com
; (1 server found)
;; global options:  printcmd
.                       405594  IN      NS      i.root-servers.net.
.                       405594  IN      NS      a.root-servers.net.
.                       405594  IN      NS      f.root-servers.net.
.                       405594  IN      NS      l.root-servers.net.
.                       405594  IN      NS      b.root-servers.net.
.                       405594  IN      NS      m.root-servers.net.
.                       405594  IN      NS      h.root-servers.net.
.                       405594  IN      NS      j.root-servers.net.
.                       405594  IN      NS      g.root-servers.net.
.                       405594  IN      NS      e.root-servers.net.
.                       405594  IN      NS      d.root-servers.net.
.                       405594  IN      NS      c.root-servers.net.
.                       405594  IN      NS      k.root-servers.net.
;; Received 244 bytes from 117.120.24.4#53(117.120.24.4) in 0 ms

com.                    172800  IN      NS      g.gtld-servers.net.
com.                    172800  IN      NS      d.gtld-servers.net.
com.                    172800  IN      NS      c.gtld-servers.net.
com.                    172800  IN      NS      e.gtld-servers.net.
com.                    172800  IN      NS      i.gtld-servers.net.
com.                    172800  IN      NS      k.gtld-servers.net.
com.                    172800  IN      NS      j.gtld-servers.net.
com.                    172800  IN      NS      l.gtld-servers.net.
com.                    172800  IN      NS      b.gtld-servers.net.
com.                    172800  IN      NS      a.gtld-servers.net.
com.                    172800  IN      NS      h.gtld-servers.net.
com.                    172800  IN      NS      m.gtld-servers.net.
com.                    172800  IN      NS      f.gtld-servers.net.
;; Received 504 bytes from 192.36.148.17#53(i.root-servers.net) in 145 ms

outlook.com.            172800  IN      NS      nse1.msft.net.
outlook.com.            172800  IN      NS      nse5.msft.net.
outlook.com.            172800  IN      NS      nse2.msft.net.
outlook.com.            172800  IN      NS      nse3.msft.net.
outlook.com.            172800  IN      NS      nse4.msft.net.
;; Received 371 bytes from 192.42.93.30#53(g.gtld-servers.net) in 244 ms

mail.eo.outlook.com.    7200    IN      NS      ns2-prodeodns.glbdns.o365filtering.com.
mail.eo.outlook.com.    7200    IN      NS      ns1-prodeodns.glbdns.o365filtering.com.
;; Received 144 bytes from 65.55.37.62#53(nse1.msft.net) in 223 ms

themix-org.mail.eo.outlook.com. 10 IN   A       216.32.181.178
themix-org.mail.eo.outlook.com. 10 IN   A       65.55.88.22
;; Received 140 bytes from 65.55.169.42#53(ns2-prodeodns.glbdns.o365filtering.com) in 255 ms

[root@dns2 etc]# dig @117.120.24.4 themix-org.mail.eo.outlook.com

; <<>> DiG 9.2.5 <<>> @117.120.24.4 themix-org.mail.eo.outlook.com
; (1 server found)
;; global options:  printcmd
;; connection timed out; no servers could be reached


[root@dns2 etc]# dig @117.120.24.4 +trace nhaban.com

; <<>> DiG 9.2.5 <<>> @117.120.24.4 +trace nhaban.com
; (1 server found)
;; global options:  printcmd
.                       404154  IN      NS      d.root-servers.net.
.                       404154  IN      NS      a.root-servers.net.
.                       404154  IN      NS      k.root-servers.net.
.                       404154  IN      NS      c.root-servers.net.
.                       404154  IN      NS      l.root-servers.net.
.                       404154  IN      NS      f.root-servers.net.
.                       404154  IN      NS      h.root-servers.net.
.                       404154  IN      NS      j.root-servers.net.
.                       404154  IN      NS      b.root-servers.net.
.                       404154  IN      NS      m.root-servers.net.
.                       404154  IN      NS      g.root-servers.net.
.                       404154  IN      NS      e.root-servers.net.
.                       404154  IN      NS      i.root-servers.net.
;; Received 244 bytes from 117.120.24.4#53(117.120.24.4) in 0 ms

com.                    172800  IN      NS      k.gtld-servers.net.
com.                    172800  IN      NS      m.gtld-servers.net.
com.                    172800  IN      NS      e.gtld-servers.net.
com.                    172800  IN      NS      h.gtld-servers.net.
com.                    172800  IN      NS      g.gtld-servers.net.
com.                    172800  IN      NS      i.gtld-servers.net.
com.                    172800  IN      NS      b.gtld-servers.net.
com.                    172800  IN      NS      a.gtld-servers.net.
com.                    172800  IN      NS      j.gtld-servers.net.
com.                    172800  IN      NS      d.gtld-servers.net.
com.                    172800  IN      NS      l.gtld-servers.net.
com.                    172800  IN      NS      f.gtld-servers.net.
com.                    172800  IN      NS      c.gtld-servers.net.
;; Received 488 bytes from 199.7.91.13#53(d.root-servers.net) in 364 ms

nhaban.com.             172800  IN      NS      ns1.sieutructuyen.net.
nhaban.com.             172800  IN      NS      ns2.sieutructuyen.net.
;; Received 113 bytes from 192.52.178.30#53(k.gtld-servers.net) in 458 ms

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

many thanks, HoaPV.

share|improve this question
    
So your setup can't resolve ns1.sieutructuyen.net (Checking here, I can). What is the purpose of this BIND installation? Is it just a caching resolver? What, if any, forwarders do you have configured? –  SmallClanger Apr 11 '13 at 8:10
    
Yes, I cannot resolve nhaban.com, themix-org.mail.eo.outlook.com and some other domains. I install my DNS for our company domain and our staffs will use this dns system. After I configured forwarder for these domains and I can resolve these domains. –  user169008 Apr 11 '13 at 9:38
    
Well, your first dig command to the outlook.com address actually worked. It was only the second one that didn't. Still, if it's working now that you've configured forwarders, then there's your answer. –  SmallClanger Apr 11 '13 at 12:05
    
Yes, that is my answer.Can you please help me check why my dns cannot query themix-org.mail.eo.outlook.com if I don't configure forwarders? –  user169008 Apr 12 '13 at 1:12
    
I found out the problem. The problem happen because I added query-source port 53; to named.conf. –  user169008 Apr 23 '13 at 2:34

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.