[ On Monday, February 10, 2003 at 14:54:24 (-0800), Gary Ray wrote: ]
> Subject: RE: Re: 500 Error: bad syntax
>
> ======================================================
> - The following addresses had transient non-fatal errors -
> grayrunlevel6.com
> ----- Transcript of session follows -----
> 451 grayrunlevel6.com... runlevel6.com: Name server timeout
> Warning: message still undelivered after 4 hours
> Will keep trying until message is 5 days old
> ======================================================
>
> As my BIND is newly installed also, it could potentially be a DNS
> issue. Dnsreport.com gives me a warning that may be relevant:

It's not your BIND software that's having problems -- it's your entire
DNS infrastructure (if I can be so bold as to call one lonely nameserver
an "infrastructure" :-)

        $ host -C runlevel6.com
         !!! runlevel6.com has only one nameserver NS1.runlevel6.com
        runlevel6.com NS NS1.runlevel6.com
        ns1.runlevel6.com gray.runlevel6.com (1044426630 10800 3600 604800 38400)

Your domain registrar (Active Domain Co.) should lose their license to
operate a domain registry for allowing you do do this!

No wonder other resolvers are sometimes complaining about timeouts with
your domain! (I'm seeing lengthy transaction times looking at your DNS)

> WARNING: One or more of your MX records did not return an A record;
> most likely, they have a CNAME. CNAMEs are prohibited in MX records,
> according to RFC974, RFC1034 3.6.2, RFC1912 2.4, and RFC2181 10.3. The
> problem MX records are:
> smtp.runlevel6.com.->runlevel6.com.->66.159.220.130

Yes, that's a major problem too.

        $ host -t mx runlevel6.com
        runlevel6.com MX 10 smtp.runlevel6.com
         *** runlevel6.com MX host smtp.runlevel6.com is not canonical

The target hostname of an MX records _MUST_ be a name that resolves to a
valid A record. SMTP mailers compliant with RFC 2821 are required to
report unusable MX records as errors and to bounce/reject the message.

The simplest fix to this problem is to change the MX target to be the
real hostname, i.e. ns1.runlevel6.com.

You've also got some issues with your reverse DNS that you really should
get resolved too:

        $ host -A ns1.runlevel6.com
         !!! ns1.runlevel6.com address 66.159.220.130 maps to netblock-66-159-220-130.dslextreme.com

> Ideas?

Fix your DNS first! ;-)

Then see how well your e-mail works.

-- 
								Greg A. Woods
+1 416 218-0098;            <g.a.woodsieee.org>;           <woodsrobohack.ca>
Planix, Inc. <woodsplanix.com>; VE3TCP; Secrets of the Weird <woodsweird.com>

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]