Problems resolving my domain

Comments

8 comments

  • Avatar
    rotblitz

    The problems with your DNS I could see is that your two nameservers point to the same IP address but should point to different subnets.  Further, this IP address could be dynamic.  Nameservers have to be behind static IP addresses.  And the mail address hi-vps@webfusion.com from the SOA record does not exist.

    In case this domain or its DNS is relatively new, i.e. less than 72 hours, you may have to wait for full propagation before everything around the world reports consistent results.  If not, better open a support ticket.

    0
    Comment actions Permalink
  • Avatar
    pgs

    Thanks, I've fixed that incorrect SOA entry.

    The IP is static, but yes, I appreciate that the two nameservers should be on different subnets. Surely OpenDNS wouldn't be penalizing because of this though? I assume, too, that OpenDNS will use the same policy/configuration across their nameservers, which leaves me wondering why some NS are seeing my domain's A record, and some aren't.

    It's actually around 4 days since I made any changes to the DNS on that domain, so it should have had a chance to propagate (isn't that what the 'refresh cache' link is for on the Cache Check page anyway - to flush the zone from the OpenDNS nameservers and cause them to re-query my nameservers?)

     

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    "Surely OpenDNS wouldn't be penalizing because of this though?"

    No, not that I knew.

    " I assume, too, that OpenDNS will use the same policy/configuration across their nameservers"

    These are not "nameservers", but recursive resolvers, being fed by the parent nameservers in the hierarchy.

    "isn't that what the 'refresh cache' link is for on the Cache Check page anyway - to flush the zone from the OpenDNS nameservers and cause them to re-query my nameservers?"

     Some OpenDNS locations may not get a response on the queries against the parents.

    As said, if you are concerned, you may raise a support ticket.

    If you just want to use your domain without this hurdle, simply use a temporary hosts file entry  like:

    37.122.211.206   littlemedia.co.uk   www.littlemedia.co.uk   ns1.little-media.co.uk   ns2.little-media.co.uk

    0
    Comment actions Permalink
  • Avatar
    andreaf1

    Hello!

    I'm experiencing a similar problem, a domain of mine is not resolved by OpenDNS.

    Also in my case the opendns cache shows that most caches works while others don't.

    Did you manage to resolve the problem?

    Thanks!

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    Did you open a support ticket, or did you tell us (users) what domain is impacted?

    0
    Comment actions Permalink
  • Avatar
    andreaf1

    Hello,I did open a support ticket

    #95021

    The impacted domain is : wow.poste.it

     

    Thanks

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    Ah, that's a duplicate of https://support.opendns.com/entries/43338810-OpenDNS-doesn-t-resolve-this-domain
    Why do you do this?

    Pretty clear that you have to wait for OpenDNS staff to respond, as said in the other thread.

    0
    Comment actions Permalink
  • Avatar
    Kristy Patullo

    I have responded to your support ticket @andreaf1.  Since there are a variety of factors that could prevent domains from resolving properly we recommend opening a support ticket to troubleshoot these types of issues.

    0
    Comment actions Permalink

Post is closed for comments.