There's not a typo in your A record line is there? Something like:

mail. IN A 123.123.123.123

the 553 line made me think of that.

In reply to 29 Feb message from [EMAIL PROTECTED]:

>I am getting a headache....everything was working
>until about 3 or 4 hours ago....I know the DNS records
>are a mess and I am trying to get through and correct
>things, but why would the mx records which are
>resolving to mail.tidalwave.net and that goes to
>208.206.112.71, which is the IMAIL server for
>tidalwave not be working for some people all of a
>sudden. 

>For people that have sent me error messages one has
>been the following: 

>>-----Original Message-----
>>From: Mail Delivery Subsystem [SMTP:[EMAIL PROTECTED]]
>><mailto:[SMTP:[EMAIL PROTECTED]]>
>>Sent: Tuesday, February 29, 2000 1:36 PM
>>To: [EMAIL PROTECTED];
>><mailto:[EMAIL PROTECTED];>  [EMAIL PROTECTED]
>><mailto:[EMAIL PROTECTED]>
>>Subject: Returned mail: Local configuration error
>>
>>The original message was received at Tue, 29 Feb 2000
13:36:18 -0500 from
>>ems.prc.com [140.188.192.203]
>> ----- The following addresses had permanent fatal errors -----
>><[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> >
>> ----- Transcript of session follows -----
>>553 mail. config error: mail loops back to me (MX problem?)
>>554 <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> >... Local
>>configuration error <<ATT566847.TXT>>  <<FW: no email>>
>>
>>
>>
>>
>>The original message was received at Tue, 29 Feb 2000
13:49:38 -0500 from
>>ems.prc.com [140.188.192.203]
>> ----- The following addresses had permanent fatal errors -----
>><[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> >
>> ----- Transcript of session follows -----
>>553 mail. config error: mail loops back to me (MX problem?)
>>554 <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> >... Local
>>configuration error



>Thank You,
>Anthony Poisson
>Network Administrator
>Tidalwave Internet Network Services

>A little Microsoft Haiku:

>Stay the patient course.
>   Of little worth is your ire.
>The network is down.

>----- Original Message -----
>From: "Len Conrad" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Sent: Tuesday, February 29, 2000 2:19 PM
>Subject: Re: [IMail Forum] a favor please


>>
>> "The zone contains more than one authoritative name
server with the same
>IP
>> address
>>
>> The name servers "ns2.tidalwave.net." and
"nereid1.tidalwave.net.", which
>> are authoritative for "tidalwave.net.", have the same IP address
>> (208.206.112.2)."
>>
>> Len
>>
>> =============
>>
>>
>>
>> >Hi,
>> >
>> >i see a mx record for tidalwave.net pointing to mail.tidalwave.net
>> >there is an a record for mail.tidalwave.net, 208.206.112.71.
>> >
>> >I don't however, see an mx record for mail.tidalwave.net.
>> >
>> >Depending on which smtp server the mail is being sent
with, if someone
>> >send mail to
<mailto:[EMAIL PROTECTED]>[EMAIL PROTECTED], it
>> >won't get to them.
>> >
>> >Sincerely,
>> >Daniel J. Vance
>> >>----- Original Message -----
>> >>From: <mailto:[EMAIL PROTECTED]>Anthony Poisson
>> >>To: <mailto:[EMAIL PROTECTED]>imail list
>> >>Sent: Tuesday, February 29, 2000 10:51 AM
>> >>Subject: [IMail Forum] a favor please
>> >>
>> >>can someone run a MX record check on us at
>> >><http://www.tidalwave.net>www.tidalwave.net
>> >>
>> >>mail hostname is mail.tidalwave.net
>> >>
>> >>ip should be 208.206.112.71
>> >>
>> >>Customers are complaining that some external sources
cannot get to us
>and
>> >>we did have a problem with DNS possibly this morning,
but everything
>> >>looks all right now, it seems to only affect certain areas.
>> >>
>> >>Thank You,
>> >>Anthony Poisson
>> >>Network Administrator
>> >>Tidalwave Internet Network Services
>> >>
>> >>A little Microsoft Haiku:
>> >>
>> >>Stay the patient course.
>> >>    Of little worth is your ire.
>> >>The network is down.
>>
>> Please visit http://www.ipswitch.com/support/mailing-lists.html
>> to be removed from this list.
>>

>Please visit
>http://www.ipswitch.com/support/mailing-lists.html to
>be removed from this list.



Please visit http://www.ipswitch.com/support/mailing-lists.html 
to be removed from this list.

Reply via email to