Daniel Higgins writes: 

> erm well that domain has been around for 6+ years 
> 
> the MX is pointing at the mail server, but not the A record (which we're not
> pointing anywhere right now, but might in the future) and that causes that
> problem

No, you were not listening to me.  Two of the six top level servers for .ca 
didn't know anything about this domain.  That was the problem. 

Looks like someone fixed it, so you should be ok from now on. 

> right now the fix is to point the A to the mail server, and to remove the MX
> (or else we get a looping case, or so we figured with another domain, in the
> .com) 
> 
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Sam
> Varshavchik
> Sent: Wednesday, January 16, 2002 10:19 PM
> To: [EMAIL PROTECTED]
> Subject: [courier-users] Re: weird domain bug and rfc1035 
> 
> 
> Feyr Tlincail writes: 
> 
>> some of my domains get a domain does not exist error 
>>
>> Jan 16 19:42:44 netcom courieresmtpd:
>> error,relay=::ffff:207.139.145.204,from=<[EMAIL PROTECTED]>:
>> 517-Domain does not exist: acces-cible.qc.ca.
>> Jan 16 19:42:44 netcom courieresmtpd:
>> error,relay=::ffff:207.139.145.204,from=<[EMAIL PROTECTED]>: 517
>> Invalid domain, see <URL:ftp://ftp.isi.edu/in-notes/rfc1035.txt> 
>>
>> the domain has its primary MX pointing to the mail server, and is listed
> in
>> both esmtpdacceptmailfor.dir and locals (the ones that are supposed to get
>> delivered locally)
> 
> Looks like there are transient failures in NSes for the .ca TLD. 
> 
> ca.                   86194   IN      NS      merle.cira.ca.
> ca.                   86194   IN      NS      relay.cdnnet.ca.
> ca.                   86194   IN      NS      clouso.risq.qc.ca.
> ca.                   86194   IN      NS      ns2.uunet.ca.
> ca.                   86194   IN      NS      ns3.utoronto.ca.
> ca.                   86194   IN      NS      rs0.netsol.com. 
> 
> Right now merle.cira.ca and clouso.risq.qc.ca do not resolve
> acces-cible.qc.ca.  If this is a new domain, wait a few more days for .ca
> TLD changes to fully propagate.  Otherwise, 1/3 of queries that go through
> the .ca TLD NSes will fail. 
> 
>> does anyone know how i would fix these? (im mostly concerned about the
> first
>> one)
> 
> Wait for changes to the .ca TLD to propagate, or for someone to fix the
> servers. 
> 
> --
> Sam 
> 
> 
> _______________________________________________
> courier-users mailing list
> [EMAIL PROTECTED]
> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users 
> 
> 
> _______________________________________________
> courier-users mailing list
> [EMAIL PROTECTED]
> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
 


-- 
Sam 


_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to