Big Problem with GoDaddy

GoDaddy's blocking me with their error of bogus Helo.

Spending some time with them on the phone today they could
offer nothing 
except to say that since my email address is schaseelpasohonda.com - 
that IP Address resolves back to my network domain name.

Obviously - like most of us my web domains are different
from my network 
domain.  I host multiple company domains in fact.  Yet
they're refusing 
to unblock for as long as elpasohonda.com's ip rDNS doesn't
resolve to 
elpasohonda.com

however, if you do a lookup on elpasohonda.com - it will
show the same 
ip address, rDNS will show the network domain name.

Anyone else run into this garbage from godaddy's ?

Stuart Chase wrote:
> GoDaddy's blocking me with their error of bogus Helo.
>
> Spending some time with them on the phone today they
could offer
> nothing except to say that since my email address is
> schaseelpasohonda.com - that IP Address resolves back to my
network
> domain name.
>
> Obviously - like most of us my web domains are
different from my
> network domain.  I host multiple company domains in
fact.  Yet they're
> refusing to unblock for as long as elpasohonda.com's ip
rDNS doesn't
> resolve to elpasohonda.com
>
> however, if you do a lookup on elpasohonda.com - it
will show the same
> ip address, rDNS will show the network domain name.
>
> Anyone else run into this garbage from godaddy's ?
>
You setup your primary mx record to be mail.elpasohonda.com.
 which
resolves to 209.30.134.202.  The reverse lookup for that ip
address is:

;; ANSWER SECTION:
202.134.30.209.in-addr.arpa. 6898 IN    CNAME  
202.200.134.30.209.in-addr.arpa.
202.200.134.30.209.in-addr.arpa. 3299 IN PTR   
mail.ephweb.com.
202.200.134.30.209.in-addr.arpa. 3299 IN PTR   
mail.elpasohonda.com.
202.200.134.30.209.in-addr.arpa. 3299 IN PTR   
server.ephweb.com.

Actually the order of the three ptr records varies each time
I query
it.  Lose the other two ptr records.  It just confuses
things. (and it
answers as mail.elpasohonda.com when connecting on port 25)
Then you can
tell them that the primary mx record points to an A record
and the
reverse lookup on that ip address matches the hostname for
the primary
mx record.  That should be exactly what they are looking
for.

Most likely they look at(or see) the first ptr record only.

Lyle

Thanks Lyle,

I added the PTR's at godaddy's suggestion to do so, earlier
I just had 
server.ephweb.com which they wouldn't let through.

They're wanting to see it, what other choice is there - make
all mx's 
server.ephweb.com ?  if that's the case, can I still setup 
elpasohonda.com to use mail.elpasohonda.com as their outlook
mail server 
settings?

Lyle Giese wrote:
> Stuart Chase wrote:
>> GoDaddy's blocking me with their error of bogus
Helo.
>>
>> Spending some time with them on the phone today
they could offer
>> nothing except to say that since my email address
is
>> schaseelpasohonda.com - that IP Address resolves
back to my network
>> domain name.
>>
>> Obviously - like most of us my web domains are
different from my
>> network domain.  I host multiple company domains in
fact.  Yet they're
>> refusing to unblock for as long as
elpasohonda.com's ip rDNS doesn't
>> resolve to elpasohonda.com
>>
>> however, if you do a lookup on elpasohonda.com - it
will show the same
>> ip address, rDNS will show the network domain name.
>>
>> Anyone else run into this garbage from godaddy's ?
>>
> You setup your primary mx record to be
mail.elpasohonda.com.  which
> resolves to 209.30.134.202.  The reverse lookup for
that ip address is:
> 
> ;; ANSWER SECTION:
> 202.134.30.209.in-addr.arpa. 6898 IN    CNAME  
> 202.200.134.30.209.in-addr.arpa.
> 202.200.134.30.209.in-addr.arpa. 3299 IN PTR   
mail.ephweb.com.
> 202.200.134.30.209.in-addr.arpa. 3299 IN PTR   
mail.elpasohonda.com.
> 202.200.134.30.209.in-addr.arpa. 3299 IN PTR   
server.ephweb.com.
> 
> Actually the order of the three ptr records varies each
time I query
> it.  Lose the other two ptr records.  It just confuses
things. (and it
> answers as mail.elpasohonda.com when connecting on port
25) Then you can
> tell them that the primary mx record points to an A
record and the
> reverse lookup on that ip address matches the hostname
for the primary
> mx record.  That should be exactly what they are
looking for.
> 
> Most likely they look at(or see) the first ptr record
only.
> 
> Lyle
> 
> 

The standard is that the helo response should match the host
name in the
MX record and that should point to an A record and that ip
address
should be a ptr back to the host name in the MX record. 
That's the
standard and if GoDaddy tells you anything else ask to talk
to a 2nd
level support person or a supervisor.

Lyle

Stuart Chase wrote:
> Thanks Lyle,
>
> I added the PTR's at godaddy's suggestion to do so,
earlier I just had
> server.ephweb.com which they wouldn't let through.
>
> They're wanting to see it, what other choice is there -
make all mx's
> server.ephweb.com ?  if that's the case, can I still
setup
> elpasohonda.com to use mail.elpasohonda.com as their
outlook mail
> server settings?
>
> Lyle Giese wrote:
>> Stuart Chase wrote:
>>> GoDaddy's blocking me with their error of bogus
Helo.
>>>
>>> Spending some time with them on the phone today
they could offer
>>> nothing except to say that since my email
address is
>>> schaseelpasohonda.com - that IP Address resolves
back to my network
>>> domain name.
>>>
>>> Obviously - like most of us my web domains are
different from my
>>> network domain.  I host multiple company
domains in fact.  Yet they're
>>> refusing to unblock for as long as
elpasohonda.com's ip rDNS doesn't
>>> resolve to elpasohonda.com
>>>
>>> however, if you do a lookup on elpasohonda.com
- it will show the same
>>> ip address, rDNS will show the network domain
name.
>>>
>>> Anyone else run into this garbage from
godaddy's ?
>>>
>> You setup your primary mx record to be
mail.elpasohonda.com.  which
>> resolves to 209.30.134.202.  The reverse lookup for
that ip address is:
>>
>> ;; ANSWER SECTION:
>> 202.134.30.209.in-addr.arpa. 6898 IN    CNAME 
>> 202.200.134.30.209.in-addr.arpa.
>> 202.200.134.30.209.in-addr.arpa. 3299 IN PTR   
mail.ephweb.com.
>> 202.200.134.30.209.in-addr.arpa. 3299 IN PTR   
mail.elpasohonda.com.
>> 202.200.134.30.209.in-addr.arpa. 3299 IN PTR   
server.ephweb.com.
>>
>> Actually the order of the three ptr records varies
each time I query
>> it.  Lose the other two ptr records.  It just
confuses things. (and it
>> answers as mail.elpasohonda.com when connecting on
port 25) Then you can
>> tell them that the primary mx record points to an A
record and the
>> reverse lookup on that ip address matches the
hostname for the primary
>> mx record.  That should be exactly what they are
looking for.
>>
>> Most likely they look at(or see) the first ptr
record only.
>>
>> Lyle

That may be where it's going awry.

The helo's saying server.ephweb.com
I had MX as mx.elpasohonda.com
There are A records going to both.

So then, would this work ok.

DNS in zone elpasohonda.com
        A       209.30.134.202
       MX    10     server.ephweb.com.
mail   A       209.30.134.202

But someones outlook still have incoming and outgoing mail
servers as
mail.elpasohonda.com




Lyle Giese wrote:
> The standard is that the helo response should match the
host name in the
> MX record and that should point to an A record and that
ip address
> should be a ptr back to the host name in the MX record.
 That's the
> standard and if GoDaddy tells you anything else ask to
talk to a 2nd
> level support person or a supervisor.
> 
> Lyle
> 
> Stuart Chase wrote:
>> Thanks Lyle,
>>
>> I added the PTR's at godaddy's suggestion to do so,
earlier I just had
>> server.ephweb.com which they wouldn't let through.
>>
>> They're wanting to see it, what other choice is
there - make all mx's
>> server.ephweb.com ?  if that's the case, can I
still setup
>> elpasohonda.com to use mail.elpasohonda.com as
their outlook mail
>> server settings?
>>
>> Lyle Giese wrote:
>>> Stuart Chase wrote:
>>>> GoDaddy's blocking me with their error of
bogus Helo.
>>>>
>>>> Spending some time with them on the phone
today they could offer
>>>> nothing except to say that since my email
address is
>>>> schaseelpasohonda.com - that IP Address resolves
back to my network
>>>> domain name.
>>>>
>>>> Obviously - like most of us my web domains
are different from my
>>>> network domain.  I host multiple company
domains in fact.  Yet they're
>>>> refusing to unblock for as long as
elpasohonda.com's ip rDNS doesn't
>>>> resolve to elpasohonda.com
>>>>
>>>> however, if you do a lookup on
elpasohonda.com - it will show the same
>>>> ip address, rDNS will show the network
domain name.
>>>>
>>>> Anyone else run into this garbage from
godaddy's ?
>>>>
>>> You setup your primary mx record to be
mail.elpasohonda.com.  which
>>> resolves to 209.30.134.202.  The reverse lookup
for that ip address is:
>>>
>>> ;; ANSWER SECTION:
>>> 202.134.30.209.in-addr.arpa. 6898 IN    CNAME 
>>> 202.200.134.30.209.in-addr.arpa.
>>> 202.200.134.30.209.in-addr.arpa. 3299 IN PTR   
mail.ephweb.com.
>>> 202.200.134.30.209.in-addr.arpa. 3299 IN PTR   
mail.elpasohonda.com.
>>> 202.200.134.30.209.in-addr.arpa. 3299 IN PTR   
server.ephweb.com.
>>>
>>> Actually the order of the three ptr records
varies each time I query
>>> it.  Lose the other two ptr records.  It just
confuses things. (and it
>>> answers as mail.elpasohonda.com when connecting
on port 25) Then you can
>>> tell them that the primary mx record points to
an A record and the
>>> reverse lookup on that ip address matches the
hostname for the primary
>>> mx record.  That should be exactly what they
are looking for.
>>>
>>> Most likely they look at(or see) the first ptr
record only.
>>>
>>> Lyle
> 
> 

Actually the server is ephweb.com when it answers on port
25, but that's
configurable in Surge.

Lyle

Stuart Chase wrote:
> That may be where it's going awry.
>
> The helo's saying server.ephweb.com
> I had MX as mx.elpasohonda.com
> There are A records going to both.
>
> So then, would this work ok.
>
> DNS in zone elpasohonda.com
>        A       209.30.134.202
>       MX    10     server.ephweb.com.
> mail   A       209.30.134.202
>
> But someones outlook still have incoming and outgoing
mail servers as
> mail.elpasohonda.com
>
>
>
>
> Lyle Giese wrote:
>> The standard is that the helo response should match
the host name in the
>> MX record and that should point to an A record and
that ip address
>> should be a ptr back to the host name in the MX
record.  That's the
>> standard and if GoDaddy tells you anything else ask
to talk to a 2nd
>> level support person or a supervisor.
>>
>> Lyle
>>
>> Stuart Chase wrote:
>>> Thanks Lyle,
>>>
>>> I added the PTR's at godaddy's suggestion to do
so, earlier I just had
>>> server.ephweb.com which they wouldn't let
through.
>>>
>>> They're wanting to see it, what other choice is
there - make all mx's
>>> server.ephweb.com ?  if that's the case, can I
still setup
>>> elpasohonda.com to use mail.elpasohonda.com as
their outlook mail
>>> server settings?
>>>
>>> Lyle Giese wrote:
>>>> Stuart Chase wrote:
>>>>> GoDaddy's blocking me with their error
of bogus Helo.
>>>>>
>>>>> Spending some time with them on the
phone today they could offer
>>>>> nothing except to say that since my
email address is
>>>>> schaseelpasohonda.com - that IP
Address resolves back to my network
>>>>> domain name.
>>>>>
>>>>> Obviously - like most of us my web
domains are different from my
>>>>> network domain.  I host multiple
company domains in fact.  Yet
>>>>> they're
>>>>> refusing to unblock for as long as
elpasohonda.com's ip rDNS doesn't
>>>>> resolve to elpasohonda.com
>>>>>
>>>>> however, if you do a lookup on
elpasohonda.com - it will show the
>>>>> same
>>>>> ip address, rDNS will show the network
domain name.
>>>>>
>>>>> Anyone else run into this garbage from
godaddy's ?
>>>>>
>>>> You setup your primary mx record to be
mail.elpasohonda.com.  which
>>>> resolves to 209.30.134.202.  The reverse
lookup for that ip address
>>>> is:
>>>>
>>>> ;; ANSWER SECTION:
>>>> 202.134.30.209.in-addr.arpa. 6898 IN   
CNAME
>>>> 202.200.134.30.209.in-addr.arpa.
>>>> 202.200.134.30.209.in-addr.arpa. 3299 IN
PTR    mail.ephweb.com.
>>>> 202.200.134.30.209.in-addr.arpa. 3299 IN
PTR    mail.elpasohonda.com.
>>>> 202.200.134.30.209.in-addr.arpa. 3299 IN
PTR    server.ephweb.com.
>>>>
>>>> Actually the order of the three ptr records
varies each time I query
>>>> it.  Lose the other two ptr records.  It
just confuses things. (and it
>>>> answers as mail.elpasohonda.com when
connecting on port 25) Then
>>>> you can
>>>> tell them that the primary mx record points
to an A record and the
>>>> reverse lookup on that ip address matches
the hostname for the primary
>>>> mx record.  That should be exactly what
they are looking for.
>>>>
>>>> Most likely they look at(or see) the first
ptr record only.
>>>>
>>>> Lyle
>>
>>
>

ok, so do you think that config I typed would solve the
problem? - at 
least correctness.

Lyle Giese wrote:
> Actually the server is ephweb.com when it answers on
port 25, but that's
> configurable in Surge.
> 
> Lyle
> 
> Stuart Chase wrote:
>> That may be where it's going awry.
>>
>> The helo's saying server.ephweb.com
>> I had MX as mx.elpasohonda.com
>> There are A records going to both.
>>
>> So then, would this work ok.
>>
>> DNS in zone elpasohonda.com
>>        A       209.30.134.202
>>       MX    10     server.ephweb.com.
>> mail   A       209.30.134.202
>>
>> But someones outlook still have incoming and
outgoing mail servers as
>> mail.elpasohonda.com
>>
>>
>>
>>
>> Lyle Giese wrote:
>>> The standard is that the helo response should
match the host name in the
>>> MX record and that should point to an A record
and that ip address
>>> should be a ptr back to the host name in the MX
record.  That's the
>>> standard and if GoDaddy tells you anything else
ask to talk to a 2nd
>>> level support person or a supervisor.
>>>
>>> Lyle
>>>
>>> Stuart Chase wrote:
>>>> Thanks Lyle,
>>>>
>>>> I added the PTR's at godaddy's suggestion
to do so, earlier I just had
>>>> server.ephweb.com which they wouldn't let
through.
>>>>
>>>> They're wanting to see it, what other
choice is there - make all mx's
>>>> server.ephweb.com ?  if that's the case,
can I still setup
>>>> elpasohonda.com to use mail.elpasohonda.com
as their outlook mail
>>>> server settings?
>>>>
>>>> Lyle Giese wrote:
>>>>> Stuart Chase wrote:
>>>>>> GoDaddy's blocking me with their
error of bogus Helo.
>>>>>>
>>>>>> Spending some time with them on the
phone today they could offer
>>>>>> nothing except to say that since my
email address is
>>>>>> schaseelpasohonda.com - that IP
Address resolves back to my network
>>>>>> domain name.
>>>>>>
>>>>>> Obviously - like most of us my web
domains are different from my
>>>>>> network domain.  I host multiple
company domains in fact.  Yet
>>>>>> they're
>>>>>> refusing to unblock for as long as
elpasohonda.com's ip rDNS doesn't
>>>>>> resolve to elpasohonda.com
>>>>>>
>>>>>> however, if you do a lookup on
elpasohonda.com - it will show the
>>>>>> same
>>>>>> ip address, rDNS will show the
network domain name.
>>>>>>
>>>>>> Anyone else run into this garbage
from godaddy's ?
>>>>>>
>>>>> You setup your primary mx record to be
mail.elpasohonda.com.  which
>>>>> resolves to 209.30.134.202.  The
reverse lookup for that ip address
>>>>> is:
>>>>>
>>>>> ;; ANSWER SECTION:
>>>>> 202.134.30.209.in-addr.arpa. 6898 IN   
CNAME
>>>>> 202.200.134.30.209.in-addr.arpa.
>>>>> 202.200.134.30.209.in-addr.arpa. 3299
IN PTR    mail.ephweb.com.
>>>>> 202.200.134.30.209.in-addr.arpa. 3299
IN PTR    mail.elpasohonda.com.
>>>>> 202.200.134.30.209.in-addr.arpa. 3299
IN PTR    server.ephweb.com.
>>>>>
>>>>> Actually the order of the three ptr
records varies each time I query
>>>>> it.  Lose the other two ptr records. 
It just confuses things. (and it
>>>>> answers as mail.elpasohonda.com when
connecting on port 25) Then
>>>>> you can
>>>>> tell them that the primary mx record
points to an A record and the
>>>>> reverse lookup on that ip address
matches the hostname for the primary
>>>>> mx record.  That should be exactly what
they are looking for.
>>>>>
>>>>> Most likely they look at(or see) the
first ptr record only.
>>>>>
>>>>> Lyle
>>>
> 
> 
> 

I am having a brain cramp here.  The only piece left in my
opinion is to
get Surge to answer as server.ephweb.com and all will match.
 But I
cann't find that setting in Surge right now.

Lyle

Stuart Chase wrote:
> ok, so do you think that config I typed would solve the
problem? - at
> least correctness.
>
> Lyle Giese wrote:
>> Actually the server is ephweb.com when it answers
on port 25, but that's
>> configurable in Surge.
>>
>> Lyle
>>
>> Stuart Chase wrote:
>>> That may be where it's going awry.
>>>
>>> The helo's saying server.ephweb.com
>>> I had MX as mx.elpasohonda.com
>>> There are A records going to both.
>>>
>>> So then, would this work ok.
>>>
>>> DNS in zone elpasohonda.com
>>>        A       209.30.134.202
>>>       MX    10     server.ephweb.com.
>>> mail   A       209.30.134.202
>>>
>>> But someones outlook still have incoming and
outgoing mail servers as
>>> mail.elpasohonda.com
>>>
>>>
>>>
>>>
>>> Lyle Giese wrote:
>>>> The standard is that the helo response
should match the host name
>>>> in the
>>>> MX record and that should point to an A
record and that ip address
>>>> should be a ptr back to the host name in
the MX record.  That's the
>>>> standard and if GoDaddy tells you anything
else ask to talk to a 2nd
>>>> level support person or a supervisor.
>>>>
>>>> Lyle
>>>>
>>>> Stuart Chase wrote:
>>>>> Thanks Lyle,
>>>>>
>>>>> I added the PTR's at godaddy's
suggestion to do so, earlier I just
>>>>> had
>>>>> server.ephweb.com which they wouldn't
let through.
>>>>>
>>>>> They're wanting to see it, what other
choice is there - make all mx's
>>>>> server.ephweb.com ?  if that's the
case, can I still setup
>>>>> elpasohonda.com to use
mail.elpasohonda.com as their outlook mail
>>>>> server settings?
>>>>>
>>>>> Lyle Giese wrote:
>>>>>> Stuart Chase wrote:
>>>>>>> GoDaddy's blocking me with
their error of bogus Helo.
>>>>>>>
>>>>>>> Spending some time with them on
the phone today they could offer
>>>>>>> nothing except to say that
since my email address is
>>>>>>> schaseelpasohonda.com - that IP
Address resolves back to my
>>>>>>> network
>>>>>>> domain name.
>>>>>>>
>>>>>>> Obviously - like most of us my
web domains are different from my
>>>>>>> network domain.  I host
multiple company domains in fact.  Yet
>>>>>>> they're
>>>>>>> refusing to unblock for as long
as elpasohonda.com's ip rDNS
>>>>>>> doesn't
>>>>>>> resolve to elpasohonda.com
>>>>>>>
>>>>>>> however, if you do a lookup on
elpasohonda.com - it will show the
>>>>>>> same
>>>>>>> ip address, rDNS will show the
network domain name.
>>>>>>>
>>>>>>> Anyone else run into this
garbage from godaddy's ?
>>>>>>>
>>>>>> You setup your primary mx record to
be mail.elpasohonda.com.  which
>>>>>> resolves to 209.30.134.202.  The
reverse lookup for that ip address
>>>>>> is:
>>>>>>
>>>>>> ;; ANSWER SECTION:
>>>>>> 202.134.30.209.in-addr.arpa. 6898
IN    CNAME
>>>>>> 202.200.134.30.209.in-addr.arpa.
>>>>>> 202.200.134.30.209.in-addr.arpa.
3299 IN PTR    mail.ephweb.com.
>>>>>> 202.200.134.30.209.in-addr.arpa.
3299 IN PTR   
>>>>>> mail.elpasohonda.com.
>>>>>> 202.200.134.30.209.in-addr.arpa.
3299 IN PTR    server.ephweb.com.
>>>>>>
>>>>>> Actually the order of the three ptr
records varies each time I query
>>>>>> it.  Lose the other two ptr
records.  It just confuses things.
>>>>>> (and it
>>>>>> answers as mail.elpasohonda.com
when connecting on port 25) Then
>>>>>> you can
>>>>>> tell them that the primary mx
record points to an A record and the
>>>>>> reverse lookup on that ip address
matches the hostname for the
>>>>>> primary
>>>>>> mx record.  That should be exactly
what they are looking for.
>>>>>>
>>>>>> Most likely they look at(or see)
the first ptr record only.
>>>>>>
>>>>>> Lyle
>>>>
>>
>>
>>
>

I tried out the bit of having all mx's be server.ephweb.com

Godaddy unblocked me, and I got at least one email through. 
I'll give it a
few more days to see what happens.  But if that's all it
takes, it's a minor
fix.  PITA but minor.

I'll let the list know after the 1st.

Thanks for your help Lyle, you kinda triggered the thought
process on it.

-----Original Message-----
From: Lyle Giese [mailto:lylelcrcomputer.info] 
Sent: Friday, December 22, 2006 2:20 PM
To: surgemail-listnetwinsite.com
Subject: Re: [SurgeMail List] Big Problem with GoDaddy

I am having a brain cramp here.  The only piece left in my
opinion is to
get Surge to answer as server.ephweb.com and all will match.
 But I
cann't find that setting in Surge right now.

Lyle

Stuart Chase wrote:
> ok, so do you think that config I typed would solve the
problem? - at
> least correctness.
>
> Lyle Giese wrote:
>> Actually the server is ephweb.com when it answers
on port 25, but that's
>> configurable in Surge.
>>
>> Lyle
>>
>> Stuart Chase wrote:
>>> That may be where it's going awry.
>>>
>>> The helo's saying server.ephweb.com
>>> I had MX as mx.elpasohonda.com
>>> There are A records going to both.
>>>
>>> So then, would this work ok.
>>>
>>> DNS in zone elpasohonda.com
>>>        A       209.30.134.202
>>>       MX    10     server.ephweb.com.
>>> mail   A       209.30.134.202
>>>
>>> But someones outlook still have incoming and
outgoing mail servers as
>>> mail.elpasohonda.com
>>>
>>>
>>>
>>>
>>> Lyle Giese wrote:
>>>> The standard is that the helo response
should match the host name
>>>> in the
>>>> MX record and that should point to an A
record and that ip address
>>>> should be a ptr back to the host name in
the MX record.  That's the
>>>> standard and if GoDaddy tells you anything
else ask to talk to a 2nd
>>>> level support person or a supervisor.
>>>>
>>>> Lyle
>>>>
>>>> Stuart Chase wrote:
>>>>> Thanks Lyle,
>>>>>
>>>>> I added the PTR's at godaddy's
suggestion to do so, earlier I just
>>>>> had
>>>>> server.ephweb.com which they wouldn't
let through.
>>>>>
>>>>> They're wanting to see it, what other
choice is there - make all mx's
>>>>> server.ephweb.com ?  if that's the
case, can I still setup
>>>>> elpasohonda.com to use
mail.elpasohonda.com as their outlook mail
>>>>> server settings?
>>>>>
>>>>> Lyle Giese wrote:
>>>>>> Stuart Chase wrote:
>>>>>>> GoDaddy's blocking me with
their error of bogus Helo.
>>>>>>>
>>>>>>> Spending some time with them on
the phone today they could offer
>>>>>>> nothing except to say that
since my email address is
>>>>>>> schaseelpasohonda.com - that IP
Address resolves back to my
>>>>>>> network
>>>>>>> domain name.
>>>>>>>
>>>>>>> Obviously - like most of us my
web domains are different from my
>>>>>>> network domain.  I host
multiple company domains in fact.  Yet
>>>>>>> they're
>>>>>>> refusing to unblock for as long
as elpasohonda.com's ip rDNS
>>>>>>> doesn't
>>>>>>> resolve to elpasohonda.com
>>>>>>>
>>>>>>> however, if you do a lookup on
elpasohonda.com - it will show the
>>>>>>> same
>>>>>>> ip address, rDNS will show the
network domain name.
>>>>>>>
>>>>>>> Anyone else run into this
garbage from godaddy's ?
>>>>>>>
>>>>>> You setup your primary mx record to
be mail.elpasohonda.com.  which
>>>>>> resolves to 209.30.134.202.  The
reverse lookup for that ip address
>>>>>> is:
>>>>>>
>>>>>> ;; ANSWER SECTION:
>>>>>> 202.134.30.209.in-addr.arpa. 6898
IN    CNAME
>>>>>> 202.200.134.30.209.in-addr.arpa.
>>>>>> 202.200.134.30.209.in-addr.arpa.
3299 IN PTR    mail.ephweb.com.
>>>>>> 202.200.134.30.209.in-addr.arpa.
3299 IN PTR   
>>>>>> mail.elpasohonda.com.
>>>>>> 202.200.134.30.209.in-addr.arpa.
3299 IN PTR    server.ephweb.com.
>>>>>>
>>>>>> Actually the order of the three ptr
records varies each time I query
>>>>>> it.  Lose the other two ptr
records.  It just confuses things.
>>>>>> (and it
>>>>>> answers as mail.elpasohonda.com
when connecting on port 25) Then
>>>>>> you can
>>>>>> tell them that the primary mx
record points to an A record and the
>>>>>> reverse lookup on that ip address
matches the hostname for the
>>>>>> primary
>>>>>> mx record.  That should be exactly
what they are looking for.
>>>>>>
>>>>>> Most likely they look at(or see)
the first ptr record only.
>>>>>>
>>>>>> Lyle
>>>>
>>
>>
>>
>