[TriLUG] Bind Question

[Dan Monjar]

Nick trilug wrote:
> Hey,
> 
> I am having trouble figuring out why a domain which my company hosts is
> not resolving. When I dig I receive a SERVFAIL error. However I am
> unaware of any changes either on the DNS box or the network. I have
> googled but have not found anything that clearly explains what to look
> for. Any help is appreciated. Below is the output of dig.
> 
> 
>>dig sedrasmith.org
> 
> 
> ; <<>> DiG 9.2.2 <<>> sedrasmith.org
> ;; global options:  printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 54530
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
> 
> ;; QUESTION SECTION:
> ;sedrasmith.org.                        IN      A
> 
> ;; Query time: 765 msec
> ;; SERVER: 207.217.126.81#53(207.217.126.81)
> ;; WHEN: Wed May 25 15:21:26 2005
> ;; MSG SIZE  rcvd: 32
> 
> 
> 

Here's what dnsstuff says... excuse the wrapping:


DNS Lookup: sedrasmith.org A record
Generated by www.DNSstuff.com

How I am searching:
Searching for sedrasmith.org A record at k.root-servers.net
[193.0.14.129]: Got referral to tld6.ultradns.co.uk. [took 81 ms]
Searching for sedrasmith.org A record at tld6.ultradns.co.uk.
[198.133.199.11]: Got referral to dns1.uk.hub.oup.com. [took 13 ms]
Searching for sedrasmith.org A record at dns1.uk.hub.oup.com.
[194.200.69.108]: Got referral to D.ROOT-SERVERS.NET. [took 93 ms]
Searching for sedrasmith.org A record at D.ROOT-SERVERS.NET.
[128.8.10.90]: Got referral to TLD6.ULTRADNS.CO.UK. [took 71 ms]
Searching for sedrasmith.org A record at TLD6.ULTRADNS.CO.UK.
[198.133.199.11]: Got referral to dns0.hk.hub.oup.com. [took 8 ms]
Searching for sedrasmith.org A record at dns0.hk.hub.oup.com.
[202.130.159.180]: Server failure! [took 238 ms].

Answer:
Server failure.  There's a problem with the DNS server for sedrasmith.org.

To see the DNS traversal, to make sure that all DNS servers are
reporting the correct results, you can Click Here.

Note that these results are obtained in real-time, meaning that these
are not cached results.
These results are what DNS resolvers all over the world will see right
now (unless they have cached information).



-- 
Dan Monjar