dig segment fault

Adam Tkac atkac at redhat.com
Mon Feb 18 14:05:25 UTC 2008


On Mon, Feb 18, 2008 at 08:44:10AM -0500, Tom Greaser wrote:
> We have Redhat ES 5.1 running BIND 9.3.3rc2
> I can do 99.98% of all lookups of remote sites 
> Im having issues with just two sites that it just can not resolve. 
> I get a Segmentation fault at the end when i should be giving me 
> back the A record info im requesting. 
> dig reymem.com +trace   
> .                       376331  IN      NS      k.root-servers.net. 
> .                       376331  IN      NS      l.root-servers.net. 
> .                       376331  IN      NS      m.root-servers.net. 
> .                       376331  IN      NS      a.root-servers.net. 
> .                       376331  IN      NS      b.root-servers.net. 
> .                       376331  IN      NS      c.root-servers.net. 
> .                       376331  IN      NS      d.root-servers.net. 
> .                       376331  IN      NS      e.root-servers.net. 
> .                       376331  IN      NS      f.root-servers.net. 
> .                       376331  IN      NS      g.root-servers.net. 
> .                       376331  IN      NS      h.root-servers.net. 
> .                       376331  IN      NS      i.root-servers.net. 
> .                       376331  IN      NS      j.root-servers.net. 
> ;; Received 488 bytes from 157.182.94.70#53(157.182.94.70) in 0 ms 
> 
> com.                    172800  IN      NS      a.gtld-servers.net. 
> com.                    172800  IN      NS      b.gtld-servers.net. 
> com.                    172800  IN      NS      c.gtld-servers.net. 
> com.                    172800  IN      NS      d.gtld-servers.net. 
> com.                    172800  IN      NS      e.gtld-servers.net. 
> com.                    172800  IN      NS      f.gtld-servers.net. 
> com.                    172800  IN      NS      g.gtld-servers.net. 
> com.                    172800  IN      NS      h.gtld-servers.net. 
> com.                    172800  IN      NS      i.gtld-servers.net. 
> com.                    172800  IN      NS      j.gtld-servers.net. 
> com.                    172800  IN      NS      k.gtld-servers.net. 
> com.                    172800  IN      NS      l.gtld-servers.net. 
> com.                    172800  IN      NS      m.gtld-servers.net. 
> ;; Received 488 bytes from 193.0.14.129#53(k.root-servers.net) in 94 ms 
> 
> reymem.com.             172800  IN      NS      dns1.carebridge.net. 
> reymem.com.             172800  IN      NS      dns2.carebridge.net. 
> ;; Received 112 bytes from 192.5.6.30#53(a.gtld-servers.net) in 37 ms 
> 
> Segmentation fault 
> 
> Why seg fault ?  How can i tell what caused the seg fault ? I have
> logging 
> turned up on our named process and i dont see any errors  
> severity debug 3; 
> 
> I seen dsn1 and 2 are .carebridge.net NS servers. So i did a dig 
> to it and got NO Seg Fault.!! 
> 
> dig dns1.carebridge.net +trace 
> 
> ; <<>> DiG 9.3.3rc2 <<>> dns1.carebridge.net +trace 
> ;; global options:  printcmd 
> .                       375958  IN      NS      c.root-servers.net. 
> .                       375958  IN      NS      d.root-servers.net. 
> .                       375958  IN      NS      e.root-servers.net. 
> .                       375958  IN      NS      f.root-servers.net. 
> .                       375958  IN      NS      g.root-servers.net. 
> .                       375958  IN      NS      h.root-servers.net. 
> .                       375958  IN      NS      i.root-servers.net. 
> .                       375958  IN      NS      j.root-servers.net. 
> .                       375958  IN      NS      k.root-servers.net. 
> .                       375958  IN      NS      l.root-servers.net. 
> .                       375958  IN      NS      m.root-servers.net. 
> .                       375958  IN      NS      a.root-servers.net. 
> .                       375958  IN      NS      b.root-servers.net. 
> ;; Received 488 bytes from 157.182.94.70#53(157.182.94.70) in 0 ms 
> 
> net.                    172800  IN      NS      J.GTLD-SERVERS.net. 
> net.                    172800  IN      NS      G.GTLD-SERVERS.net. 
> net.                    172800  IN      NS      E.GTLD-SERVERS.net. 
> net.                    172800  IN      NS      M.GTLD-SERVERS.net. 
> net.                    172800  IN      NS      L.GTLD-SERVERS.net. 
> net.                    172800  IN      NS      F.GTLD-SERVERS.net. 
> net.                    172800  IN      NS      B.GTLD-SERVERS.net. 
> net.                    172800  IN      NS      I.GTLD-SERVERS.net. 
> net.                    172800  IN      NS      A.GTLD-SERVERS.net. 
> net.                    172800  IN      NS      K.GTLD-SERVERS.net. 
> net.                    172800  IN      NS      D.GTLD-SERVERS.net. 
> net.                    172800  IN      NS      H.GTLD-SERVERS.net. 
> net.                    172800  IN      NS      C.GTLD-SERVERS.net. 
> ;; Received 506 bytes from 192.33.4.12#53(c.root-servers.net) in 29 ms 
> 
> dns1.carebridge.net.    172800  IN      A       139.177.224.79 
> carebridge.net.         172800  IN      NS      dns1.carebridge.net. 
> carebridge.net.         172800  IN      NS      dns2.carebridge.net. 
> ;; Received 118 bytes from 192.48.79.30#53(J.GTLD-SERVERS.net) in 214
> ms 
> 
> 
> The other domain other domain i have issues with is smokefreemonc.org 
> Anyone know what the next step in looking into these WEIRD issues are ? 
> I've even brought up a named box outside our firewall to test and no
> luck. get the same thing
> 

I believe this problem is bug in dig utility

2091.   [port] dighost.c: race condition on cleanup. [RT #16417]

Fix is part of bind-9.3.4-P1 which is scheduled as update for RHEL
5.2. You will try proposed update if you want (el5 srpm is located on
http://people.redhat.com/atkac/bind/). You will also add yourself to
https://bugzilla.redhat.com/show_bug.cgi?id=423741 which is about this
issue.

Adam

-- 
Adam Tkac, Red Hat, Inc.



More information about the bind-users mailing list