Unable to look up zone sencia.ca [BIND 8.4].
jwark at tbaytel.net
Fri Oct 12 18:17:00 UTC 2007
I should make a note as well. Each time we experience trouble with this customer, they have taken a name server of theirs offline
to move it. Sometimes it is for a few minutes, sometimes for a couple hours. However, once one of their servers is offline, we
seem to be stuck and unable to look up their hosted domains.
On Fri, 12 Oct 2007 09:57:52 -0400
Jeff Wark <jwark at tbaytel.net> wrote:
>> This morning we received a call from a customer [we're a small ISP]. They said that people from our ISP were unable to lookup
>> domains on their name servers. The domain is 'sencia.ca'.
>> Sure enough, when I did a simple 'host sencia.ca', the connection timed out. I then issued the 'dumpdb' command from the ndc
>> prompt. This is the resulting information:
>> $ORIGIN ca.
>> sencia 1473 IN NS ns2.s7host.net. ;Cr=addtnl [188.8.131.52]
>> 1473 IN NS ns1.s7host.net. ;Cr=addtnl [184.108.40.206]
>> $ORIGIN NET.
>> s7host 1400 IN NS ns1.s7host.net. ;Cr=addtnl [220.127.116.11]
>> 1400 IN NS ns2.s7host.net. ;Cr=addtnl [18.104.22.168]
>> $ORIGIN s7host.NET.
>> ns2 1400 IN A 22.214.171.124 ;NT=134 Cr=answer [126.96.36.199]
>> ns1 1400 IN A 188.8.131.52 ;NT=20401 Cr=answer [184.108.40.206]
>> It seems as though we had all the information required to lookup the A record for sencia.ca, but it didn't do it.
>> enough, after the database dump, both of our name servers looked up the host without problem.
>> We are running BIND 8.4.6-1 which is the version number in Debian Sarge.
>> Does anyone have any ideas as to why this problem may be occurring? Any input would be appreciated.
>> Jeff Wark
>> TBayTel Internet
More information about the bind-users