Well, after increasing the debug level of the client it gave me more information that the DNS server I was trying to troubleshoot wasn't giving me. It was actually a lame server problem which the DNS server returned as a SERVFAIL.... I got it all sorted out now that I found out exactly what the problem was. Thanks for the reply :)
Later, Trevor >> >> >>When I use either dig or nslookup on the domain from some remote >> location say for example a.domain.com it returns the correct answer. I >> then proceed to look up b.domain.com which returns a SERVFAIL. If I >> restart the Bind DNS server I am using for the lookups and switch the >> order, so I lookup b.domain.com first it returns the answer and of >> course a.domain.com returns the SERVFAIL. >> > Hmm. Did you try looking up both domains a second time? Have you > tried getting iptables/ipchains to log all DNS ports or (even better) > used tcpdump, so you can see the net traffic? > > HJ Hornbeck
