MX record lookup problem.

[Barry Margolin]

In article <d0nt8h$30gf$1 at sf1.isc.org>,
 Grahame Cooper <Grahame at JandG-Cooper.com> wrote:

> I have a domain name jandg-cooper.com registered with Enom.
> 
> jandg-cooper.com does not refer to any host, so there is no A or CNAME 
> record for that, but there is an MX record for jandg-cooper.com, which 
> points to cooper-linux.jandg-cooper.com
> 
> The problem is that if an MX query for jandg-cooper is preceded by an A 
> record query, then the MX query fails:
> 
>   $ host -t MX jandg-cooper.com
>   jandg-cooper.com mail is handled by 10 cooper-linux.jandg-cooper.com.
> 
>   $ host jandg-cooper.com
>   Host jandg-cooper.com not found: 3(NXDOMAIN)
> 
>   $ host cooper-linux.jandg-cooper.com
>   cooper-linux.jandg-cooper.com has address 213.106.40.103
> 
>   $ host -t MX jandg-cooper.com
>   Host jandg-cooper.com not found: 3(NXDOMAIN)
> 
> I'm not sure whether this is a problem with Bind or Enom.
> 
> Any clues?

I can't reproduce your problem.  I suggest you try it with "dig" instead 
of "host" so you can see the queries and responses in detail.

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