Unnecessary DNS records

Home Forums Microsoft Networking and Management Services DNS Unnecessary DNS records

This topic contains 4 replies, has 4 voices, and was last updated by  Dext 1 year ago.

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts

  • 5habbaranks
    Member
    #167336

    Hi,

    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 http://www.domainname.com and point them to the same place as your domainname.com mx records?

    Thanks


    biggles77
    Spectator
    #214372

    Can you post screenshot of this occurrence? You know, a picture, a thousands words and all that. :smile:


    wullieb1
    Moderator
    #245716

    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.


    Dext
    Member
    #379156

    Hi guys, here’s a pic of what I mean – both http://www.domain.com AND domain.com pointing to exactly the same place wouldn’t you just need 1 set of mx records which manage the domain as a whole?

    [ATTACH=JSON]{“data-align”:”none”,”data-size”:”medium”,”data-attachmentid”:515395}[/ATTACH]


    wullieb1
    Moderator
    #245718

    http://www.domain.com and domain.com are not the same thing.

    In esscence http://www.domain.com is a child domain of domain.com 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 bigcompany.org. Each site is a child domain of bigcompany.org so looks like:

    bigcompany.org
    AMER.bigcompany.org
    EMEA.bigcompany.org
    APAC.bigcompany.org

    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

    AMER.bigcompany.com MX 100 inbound1.bigcompany.org
    AMER.bigcompany.org MX 100 inbound2.bigcompany.org

    EMEA.bigcompany.com MX 100 inbound1.bigcompany.org
    EMEA.bigcompany.org MX 100 inbound2.bigcompany.org

    APAC.bigcompany.com MX 100 inbound1.bigcompany.org
    APAC.bigcompany.org MX 100 inbound2.bigcompany.org

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

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.