Home / server / Questions / 517821
Accepted
Michael
Asked: 2013-06-23 11:32:15 +0800 CST

Setting up Outlook.com as mail server MX record trailing dot

  • 772

Outlook.com is allowing to connect your domain to their email servers. To validate the domain they give you the following instructions: enter image description here

In my domain registrar i've defined

mysite.org.il.     86400   IN      TXT     v=spf1 include:hotmail.com ~all
mysite.org.il.     86400   IN      MX      0       *******523fc85f4870.pamx1.hotmail.com

As they asked, and it doesn't work.

I have also tried to define *******523fc85f4870.pamx1.hotmail.com. with the trailing dot at the end and I saw that it automatically appends my fqdn to the end of the address. When I did that, the domain was verified correctly but occasionally it was de-verified (every time I refreshed it was either verified or not-verified)

What is the correct way to define it ?

Adding my complete record set:

mysite.org.il.  86400   IN  NS  ns1.sitesdepot.com.
mysite.org.il.  86400   IN  NS  ns2.sitesdepot.com.
mysite.org.il.  86400   IN  A   80.244.162.32
ftp.mysite.org.il.  86400   IN  CNAME   mysite.org.il.
www.mysite.org.il.  86400   IN  CNAME   myapp.herokuapp.com.
mysite.org.il.  86400   IN  TXT v=spf1 include:hotmail.com ~all
mysite.org.il.  86400   IN  MX  0   ******6aea9523fc85f4870.pamx1.hotmail.com
domain-name-system

1 Answers

  1. Best Answer

    The syntax of DNS names that appear in zone files is that that if a final dot is not given, the current $ORIGIN is appended to the name. So when you define:

    ***.org.il.    IN   MX   10 mx.example.com

    the meaning of this is that the MX record contains the name "mx.example.com"+whatever the value of $ORIGIN is at the time. Since the default $ORIGIN is the name of the zone, that means you're probably actually defining:

    ***.org.il.    IN   MX   10 mx.example.com.***.org.il.

    So you certainly want to use the final dot in this context.

    If you have the problem that "occasionally it was de-verified", then you might have some problem with your DNS setup. Check if your secondary nameservers are up to date and serving the same, correct, information as the primary. Related to this, make sure you didn't forget to update the SOA serial number when you updated the primary.

    • 1