No announcement yet.

Unnecessary DNS records

  • Filter
  • Time
  • Show
Clear All
new posts

  • Unnecessary DNS records


    I've noticed some additional MX records on a domain which point to the same place as the normal dns records effectively unnecessary (unless Im missing something hence the question). So is there any time you would need to create additional mx records with and point them to the same place as your mx records?


  • #2
    Can you post screenshot of this occurrence? You know, a picture, a thousands words and all that.
    1 1 was a racehorse.
    2 2 was 1 2.
    1 1 1 1 race 1 day,
    2 2 1 1 2


    • #3
      Depends. You may have your MX records pointing to an FQDN. How would it then know how to contact the correct server, yep it will search for an A record.

      However without an example of what you mean its a bit difficult.


      • #4
        Hi guys, here's a pic of what I mean - both AND pointing to exactly the same place wouldn't you just need 1 set of mx records which manage the domain as a whole?

        Click image for larger version

Name:	Image.png
Views:	1
Size:	27.6 KB
ID:	515395


        • #5
 and are not the same thing.

          In esscence is a child domain of and as such could potentially run its own email server. The fact that it points to the same email server would sat to me that it is one big org. However the use of www if very confusing IMO, unless of course you have changed the domain names.

          Think of it like this

          We are a global company that is divided into 3 parts, AMER, EMEA, APAC. my domain is Each site is a child domain of so looks like:

          However as it is all one big forest email is for all intents and purposes a single app, if your using exchange that is.

          So your MX records could look like this

 MX 100
 MX 100

 MX 100
 MX 100

 MX 100
 MX 100

          All it basically means is the the servers listed will accept email for the corresponding domain.