Re: MX and A records

The A record for mail pointing to the Public IP is correct and you should be able to see this at www.dnsstuff.com. Go the DNS Lookup Tab, put the domain name not MX record in the box and then select MX. You should see the correct IP with A Record.

As for the other customer having issues with send mail, this is most likely not the MX record since they still receiving mail correctly.

--
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2007
Microsoft Certified Partner


"jeffuk123" <jeffuk123@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:BD27EEA6-F56A-454F-8C6A-D7A0FE4770F1@xxxxxxxxxxxxxxxx
Hello,

I'm a little confused.

The IT company I work for, if I go to www.dnsstuff.com, I see that our MX
records are mail.ourcompanyname.org.uk and the A record points to our public
ip address. This works fine. I can log into our server remotely and we can
send and receive external emails.

Now, one of our customers, if I go to www.dnsstuff.com, I see that their MX
records are mail.companyname.org.uk but the A records show an ip address that
is their 'Internet or www address'. This is not their public ip address yet I
am still able to log in remotely to their server and send and receive emails.
However, If I log into the control panel of their ISP, I see that there is
another A record called 'mail' which points to their public ip address, why
does this not show up at www.dnsstuff.com

i'm a little puzzled about MX and A records. The reason I ask, is that
suddenly another customer of ours, I can no longer log in remotely to their
SBS2003 server and cannot send email, but can receive. This has just
happened. I do not have access to their MX and A records, but in
www.dnsstuff.com the A record points to their 'internet or www address' and
not the public ip address, but I believe it may have worked before and that
they may have another A record which does point to their public ip address. I
cannot work out why this has suddenly just happened, as all port forwarding
is correct on the customers router, antivirus was disabled to diagnose this
in case this was causing problems, and therefore, I assumed it must be the MX
records etc that are at fault, but cannot be certain.

Any ideas would truly appreciated,

Thanks,
Jeff

.

Quantcast