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:

*snip*
$ORIGIN ca.

sencia 1473 IN NS ns2.s7host.net. ;Cr=addtnl [129.33.164.73]
1473 IN NS ns1.s7host.net. ;Cr=addtnl [129.33.164.73]


$ORIGIN NET.
s7host 1400 IN NS ns1.s7host.net. ;Cr=addtnl [192.5.6.30]
1400 IN NS ns2.s7host.net. ;Cr=addtnl [192.5.6.30]

$ORIGIN s7host.NET.
ns2 1400 IN A 24.109.252.254 ;NT=134 Cr=answer [192.5.6.30]
ns1 1400 IN A 216.211.21.143 ;NT=20401 Cr=answer [192.5.6.30]
*snip*

It seems as though we had all the information required to lookup the A record for sencia.ca, but it didn't do it. Interestingly
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