JWM wrote:
Stefano,
I really appreciate your help in this ordeal.
I copied your response to Register. According them, RFCs are now simply
'suggestions'... Is that true? I thought they were already mandatory.
Hi JWM,
I just wrote a unittest for the current James trunk to test the scenario
and it seems that James trunk already correctly resolve this mx server.
I'm not able to run the test against 2.2.0 right now.
Are you able to run a test using 2.3.0a1 or a recent nightly build?
Stefano
JWM wrote:
Stefano,
The domain in question is: brandilyncollins.com
# host -t mx brandilyncollins.com
brandilyncollins.com mail is handled by 0 mxmail.register.com.
# host -t a mxmail.register.com.
mxmail.register.com is an alias for rcom-outblaze-com.mr.outblaze.com.
rcom-outblaze-com.mr.outblaze.com has address 205.158.62.41
rcom-outblaze-com.mr.outblaze.com has address 205.158.62.200
rcom-outblaze-com.mr.outblaze.com has address 205.158.62.206
rcom-outblaze-com.mr.outblaze.com has address 205.158.62.207
rcom-outblaze-com.mr.outblaze.com has address 205.158.62.229
rcom-outblaze-com.mr.outblaze.com has address 205.158.62.230
So, it is clear that the mx host name for brandilyncollins.com does not
have A or RR but instead it only provide a CNAME.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
