Cannot resolve a specific domain

[David E. Meier]

> David E. Meier wrote:
>> Hi list,
>>
>> I got a complaint from a client of mine not being able to mail to a
>> certain domain (apexshipping.com.tw). Otherwise I am not aware of any
>> resolving problems of my DNS.
>>
>> First thing, I downloaded the current named.root file and restarted
>> named.
>> Then I ran:
>>
>> $ dig apexshipping.com.tw +trace
>>
>> ; <<>> DiG 9.3.4-P1 <<>> apexshipping.com.tw +trace
>> ;; global options:  printcmd
>> :
>> ;; Received 488 bytes from 193.17.199.10#53(193.17.199.10) in 5 ms
>> :
>> ;; Received 423 bytes from 192.203.230.10#53(E.ROOT-SERVERS.NET) in 161
>> ms
>> :
>> ;; Received 356 bytes from 61.220.48.1#53(C.DNS.tw) in 291 ms
>>
>> apexshipping.com.tw.    86400   IN      NS      dns.apexshipping.com.tw.
>> apexshipping.com.tw.    86400   IN      NS
>> dns1.apexshipping.com.tw.
>> ;; Received 106 bytes from 220.229.225.196#53(f.twnic.net.tw) in 318 ms
>>
>> dig: couldn't get address for 'dns.apexshipping.com.tw': not found
>>
>> My DNS runs on FreeBSD 6.2-STABLE and the current version of bind is:
>> $ named -v
>>
>>> BIND 9.3.4-P1
>>>
>>
>> The server is used exclusively as DNS. I know the domain exists and is
>> resolvable through other DNS. I wonder if I could track down the problem
>> in any other way. Or would upgrading bind solve the problem?
>>
>> Thanks for input. David.
>>
>>
>>
> Looks like the domain is badly configured! dns.apexshipping.com.tw does
> not respond for the domain but dns1.apexshipping.com.tw does. You should
> contact their Hostmaster!
> --
>
> Howard Wilkinson

Thanks for the quick reply, Howard.

So the domain is badly configured and this will happen to all other DNS
querying for the domain as well. So I wonder why others can and what's
wrong with my DNS. Is there a way to force bind to query both DNS at
apexshipping?

David