Strange problem

Barry Margolin barmar at alum.mit.edu
Wed Aug 11 03:56:43 UTC 2004


In article <cfbjho$2vr9$1 at sf1.isc.org>, "Alex Shi" <chpshi at stonix.com> 
wrote:

> Hi All,
> 
> I got a very strange problem. It might not be as strange as I feel it to you
> DNS gurus. But to me as a newbie I really find it hard to understand. Here
> is the situation:
> 
> 1. A domain name say it is adomainname.com, and a subdomain based
> on is sub1.adomainname.com. The name servers for this subdomain are
> ns1.adomainname.com
> ns2.adomainname.com
> This subdomain is hosted on host called BHOST.
> 
> 2. From all over the world I can ping, dig and lynx this subdomain, except
> on one server, where the primary domain, adomainname.com is hosted.
> Say this server is called AHOST. On AHOST I can dig and lynx whatever
> subdomains based on adomainname.com but cannot ping them. If ping
> them always got a error saying "host unknown".
> 
> I guess the reason to cause the problem might be from conflict zones.
> AHOST belongs to a hosting company which have their own name servers.
> And, in there name servers there is a zone for adomainnames.com.
> However, adomainname.com is registered with ns1/ns2.adomainname.com
> as its name servers. And, to be strange is that why the conflict zones
> only have affection to ping but not to dig and lynx?
> 
> Thanks in advance for any help.

Why does the hosting company have this zone on their servers if they're 
not supposed to be authoritative for it?  Just tell them to get rid of 
the incorrect zone -- it doesn't belong there.

-- 
Barry Margolin, barmar at alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***


More information about the bind-users mailing list