MX doesn't resolve if not helped a bit...

[Kevin Darcy]

I think you've buried yourself in glue here. Let's see: cogito-info.com is
served by cogito-info.ch nameservers, cogito-info.ch is served by
labourey.com nameservers, labourey.com is served by ascio.net nameservers,
and, finally, ascio.net nameservers serve the ascio.net domain. This is an
awful lot of work you're subjecting nameservers to, just to resolve an MX for
cogito-info.com, and is exacerbated by the fact that, unlike .net and .com,
which have overlapping sets of nameservers (and thus share glue records), .ch
is a totally separate TLD which doesn't share any glue records. BIND 8 and
its "lack of query restart" just can't deal with it at all. I was eventually
able to resolve the MX record, but only after doing *several* queries.
Resolvers embedded in mailers typically aren't that patient/perserverant.

You might want to consider short-circuiting that glue chain a little bit.
Would it hurt to have the cogito-info.com domain served by cogito-info.com
nameservers? I mean, the nameservers could stay the same, just refer to them
by different names...


- Kevin

Sacha Labourey wrote:

> Hello James and Mark,
>
> Thank you for your this info. I've corrected it. Nevertheless, my problem
> still seems to happen.
>
> What do you get when you try to MX-resolve cogito-info.com. from a "clean"
> DNS (without any cached info)? does it work?
>
> Thank you a lot for your time. Cheers,
>
>                                                 Sacha
>
> P.S.: James, what is this "Sender: artch at cogito-info.com" testing for?
>
> > > I have a strange problem. Mail sent to @cogito-info.com is either
> > > correctly and promptly delivered, either delayed or never arrives.
> > > While it seems as a truism, the last two cases are *very* frequent.
> > >
> > > To check the problem, I have subscribed to a yahoogroups which gives
> > > history information about unsucessfull delivery. Result : I have
> > > plenty of "No MX or A record for cogito-info.com" in my history.
> > >
> > > some info regarding cogito-info.com. :
> > >  - DNS1: 194.38.95.241, NS1.COGITO-INFO.CH (please read *ch* and not
> > > *com* here)
> > >  - DNS2: 194.38.95.241, NS2.COGITO-INFO.CH
> > >
> > [SNIP]
> >
> > There is a difference in the name servers for cogito-info.com from the
> > .com GTLD (non-auth) and the  name servers from the (auth) servers.  See
> > the 'doc' run below:
> ...
> > cogito-info.com.ERROR: NS list from cogito-info.com. authoritative
> > servers does not
> >   === match NS list from parent (com.) servers
> > NS list summary for cogito-info.com. from authoritative servers
> >   == cogito-ns1.labourey.com. cogito-ns2.labourey.com.
> > ERROR: ns1.cogito-info.ch. claims to be authoritative, but does not
> > appear in
> > NS list from authoritative servers
> > ERROR: ns2.cogito-info.ch. claims to be authoritative, but does not
> > appear in
> > NS list from authoritative servers
> ...