0

Bad resolving from NextDNS

$ dig @1.1.1.1 simplelabcloud.fr

;; ANSWER SECTION:
simplelabcloud.fr.      30      IN      A       65.109.18.169

$ dig @8.8.8.8 simplelabcloud.fr

;; ANSWER SECTION:
simplelabcloud.fr.      30      IN      A       65.109.18.169

$ dig @45.90.28.172 simplelabcloud.fr

;; ANSWER SECTION:
simplelabcloud.fr.      30      IN      A       51.159.11.50

4 replies

null
    • acsf
    • 2 yrs ago
    • Reported - view

    Good reply here perhaps: 

    $ dig @45.90.30.172 simplelabcloud.fr

;; ANSWER SECTION:
simplelabcloud.fr.      23      IN      A       65.109.18.169
    • acsf
    • 2 yrs ago
    • Reported - view

    Strange... if i try the same query from another server the good result is returned.

    Why on earth the resolver returns different results for the same query? 馃え

      • Calvin_Hobbes
      • 2 yrs ago
      • Reported - view

      acsf That can happen if they're using DNS load balancing (round robin) or with some CDNs.   It doesn't look like that's the case here.   I'm not seeing the wrong answer now.

      Here's a way to easily check global propagation. https://www.whatsmydns.net

      Looks like most of the world has the same answer right now. If you do a lookup of google's main site https://www.whatsmydns.net/#A/www.google.com , you'll see that it's pretty common to get different answers.

    • acsf
    • 2 yrs ago
    • Reported - view

    Sure, they have many A entries, not my case here. I'm quering the same provider, I'm expecting the same values. Note that I've waited 2h between queries before report it. TTL is 1mn...

Login to reply

Content aside

  • 2 yrs agoLast active
  • 4Replies
  • 38Views
  • 2 Following