OpenDNS unable to resolve blog.fastmail.com, forced to switch back to google's or ISP's DNS

Comments

8 comments

  • Avatar
    rotblitz

    Correct, I can confirm your observation.  OpenDNS does not respond on queries for the alias blog.fastmail.com and its real name www.fastmail.com.  I suggest you open a support ticket to get this reviewed.

    As a temporary workaround, you can add the following entry into your local hosts file:

    66.111.4.147 www.fastmail.com blog.fastmail.com

    And no, you are not forced to switch to another DNS service.

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    It seems the problem has been cleared in the meantime.

    nslookup blog.fastmail.com. 208.67.222.222
    Server: resolver1.opendns.com
    Address: 208.67.222.222

    Nicht autorisierende Antwort:
    Name: www.fastmail.com
    Addresses: 66.111.4.148
    66.111.4.147
    Aliases: blog.fastmail.com

     

    0
    Comment actions Permalink
  • Avatar
    edwh

    Also classic.fastmail.com and m.fastmail.com.

    There may be others.

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    Raise a support ticket with OpenDNS.  We users cannot help you with this.

    0
    Comment actions Permalink
  • Avatar
    mpdharley

    I will be opening a ticket for this, but there appears to be an issue with fastmail.com in general.  If you use MacOS server and smtp.fastmail.com as your mail relay, it will fail.  OpenDNS will not return a MX record for smtp.fastmail.com.  Google and Comcast DNS do.

     

    0
    Comment actions Permalink
  • Avatar
    rotblitz (Edited )

    smtp.fastmail.com doesn't have to have an MX record, but has two A records.  This is fastmail.com which needs to have the MX records which it has.  But you are correct, OpenDNS doesn't respond on queries for smtp.fastmail.com, same as for classic.fastmail.com and m.fastmail.com and blog.fastmail.com.  Please keep us updated on the results of your ticket.

    0
    Comment actions Permalink
  • Avatar
    mpdharley

    Working with OpenDNS support and paraphrasing their answer, they discovered that "fastmail.com triggered a security feature" which was causing resolution issues for fastmail.com and they were only responding to fastmail.com queries in specific circumstances.  They have added a cache entry to allow resolution and initial tests show it resolved my issue.

    They also sent the information to their engineering team to investigate why fastmail.com traffic triggered their security.

    Mike

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    Great, thank you for the feedback.

    0
    Comment actions Permalink

Please sign in to leave a comment.