3

Bing.com not resolving

net::ERR_NAME_NOT_RESOLVED

This is the third day I've been experiencing this.

18 replies

null
    • Clmbtti
    • 7 mths ago
    • Reported - view

    Samesies. 

    • ycyc
    • 7 mths ago
    • Reported - view

    I am experiencing the same issue.

    • Jarek
    • 7 mths ago
    • Reported - view

    It started to work on Windows, but not on Android.

    • Aldunn
    • 7 mths ago
    • Reported - view

    Can confirm, Bing.com isn't responding anymore.

    • Jose_Manoel
    • 7 mths ago
    • Reported - view

    I'm having the same problem...

    • R_P_M
    • 7 mths ago
    • Reported - view

    Could everyone please check what server you are connected to while this is happening, see if anything correlates.

    https://ping.nextdns.io

    (no problem for me here if you’re interested)

      • ycyc
      • 7 mths ago
      • Reported - view

       

      • ycyc
      • 7 mths ago
      • Reported - view

      On my Android phone, connecting to the “zepto-hkg” server, which differs from the server that the browser connects to (anexia-hkg (IPv6)), it seems can access bing.com.

    • Onslaught
    • 7 mths ago
    • Reported - view

    Same here…

     

    bing.com also copilot.microsoft.com could not be resolved when using NextDNS.

    the services are only reachable when not using nextDNS Config. 
     

    for testing, i disabled all block lists or other features from nextdns. Didn’t solve the problem.

    • NextDNs
    • 7 mths ago
    • Reported - view

    We can’t reproduce the issue. Can you please provide a dig output?

    • Martheen
    • 7 mths ago
    • Reported - view

    This is likely a regional problem with Bing nameserver. Since yesterday I noticed that curl, if set to use DoH parameter, can't load the www subdomain of bing (but *can* load the naked domain) with Google, AdGuard, and a couple other DoH servers running on a Japan VPS. Cloudflare DoH can load it normally, and from Indonesia all servers, currently, works normally (they didn't yesterday)

    • Clmbtti
    • 7 mths ago
    • Reported - view

    The issue remains pertinent in my local area today, but also exclusively on android. I am using the private DNS feature.

    • Jardel
    • 7 mths ago
    • Reported - view

    Same problem here.

    From Brazil: "edgeuno-cwb (IPv6)"

    • BigDargon
    • 7 mths ago
    • Reported - view

    bing.com accesses normally, I don't have any network problems. Please check with the command nslookup/dig then traceroute to those domains. And check your network connection.

     

    ; <<>> DiG 9.16.28 <<>> bing.com CHAOS
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15485
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 7
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;bing.com.                      CH      A
;; ANSWER SECTION:
bing.com.               191     IN      A       204.79.197.200
bing.com.               191     IN      A       13.107.21.200
;; ADDITIONAL SECTION:
proto.nextdns.io.       0       CH      TXT     "DOH"
server.nextdns.io.      0       CH      TXT     "lightnode-sgn-1"
profile.nextdns.io.     0       CH      TXT     "XXX"
client.nextdns.io.      0       CH      TXT     "171.XXX.XXX.XXX"
client-name.nextdns.io. 0       CH      TXT     "nextdns-windows"
smart-ecs.nextdns.io.   0       CH      TXT     "not sent"
;; Query time: 17 msec
;; SERVER: 9.9.9.11#53(9.9.9.11)
;; WHEN: Mon Apr 15 11:07:11 SE Asia Standard Time 2024
;; MSG SIZE  rcvd: 346

; <<>> DiG 9.16.28 <<>> bing.com AAAA CHAOS
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41508
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 7
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;bing.com.                      CH      AAAA
;; ANSWER SECTION:
bing.com.               284     IN      AAAA    2620:1ec:c11::200
;; ADDITIONAL SECTION:
proto.nextdns.io.       0       CH      TXT     "DOH"
server.nextdns.io.      0       CH      TXT     "lightnode-sgn-1"
profile.nextdns.io.     0       CH      TXT     "XXX"
client-name.nextdns.io. 0       CH      TXT     "nextdns-windows"
client.nextdns.io.      0       CH      TXT     "171.XXX.XXX.XXX"
smart-ecs.nextdns.io.   0       CH      TXT     "not sent"
;; Query time: 12 msec
;; SERVER: 9.9.9.11#53(9.9.9.11)
;; WHEN: Mon Apr 15 11:07:17 SE Asia Standard Time 2024
;; MSG SIZE  rcvd: 334

    Tracing route to bing.com [204.79.197.200]
over a maximum of 30 hops:
  1     1 ms     3 ms     1 ms  192.168.1.1
  2     5 ms     8 ms     7 ms  125.235.251.199
  3    11 ms     3 ms     2 ms  10.207.244.131
  4     6 ms    20 ms     4 ms  27.68.209.61
  5     *        *        *     Request timed out.
  6    43 ms    31 ms    27 ms  27.68.255.86
  7    79 ms    31 ms    40 ms  27.68.233.242
  8    56 ms     *        *     27.68.255.98
  9    58 ms    80 ms    54 ms  117.1.220.246
 10     *        *        *     Request timed out.
 11    68 ms    60 ms    59 ms  104.44.212.216
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14    64 ms    64 ms    97 ms  204.79.197.200
Trace complete.

Tracing route to bing.com [2620:1ec:c11::200]
over a maximum of 30 hops:
  1     4 ms     3 ms     2 ms  2402:800:634c:543d:b28b:92ff:fe36:ba57
  2    11 ms     6 ms    10 ms  2402:800:633c::1
  3    11 ms     8 ms    13 ms  2402:800:63ff:e::e:1
  4    51 ms    53 ms    31 ms  2402:800:1120:75::1
  5     *       79 ms     *     ::ffff:27.68.255.97
  6    29 ms    28 ms    61 ms  ::ffff:27.68.250.113
  7    26 ms     *       77 ms  2620:0:1cff:dead:beee::14b7
  8    32 ms    29 ms    38 ms  2a01:111:2000:1::22a5
  9    57 ms    53 ms    57 ms  2a01:111:224:108::6e
 10     *        *        *     Request timed out.
 11    34 ms    38 ms    33 ms  2620:1ec:c11::200
Trace complete.
      • Clmbtti
      • 7 mths ago
      • Reported - view

      tracert bing.com

      Tracing route to bing.com [2620:1ec:c11::200]
      over a maximum of 30 hops:

        1     1 ms     1 ms     1 ms  2804:1e68:c609:d07f::1
        2    29 ms    38 ms    33 ms  2001:1291::2ae
        3    23 ms    23 ms    22 ms  2001:1291:0:4a0::a
        4     *        *        *     Request timed out.
        5    25 ms    24 ms    28 ms  2a01:111:222:1ba::6e
        6     *        *        *     Request timed out.
        7     *        *        *     Request timed out.
        8    23 ms    23 ms    23 ms  2620:1ec:c11::200

      Trace complete.

      nslookup bing.com
      Server:  UnKnown
      Address:  2804:1e68:c609:d07f::1

      Non-authoritative answer:
      Name: bing.com
      Addresses:  2620:1ec:c11::200
                204.79.197.200
                13.107.21.200
       

      Cannot open bing.com on any of my devices this morning.

    • Levanderi
    • 7 mths ago
    • Reported - view

    Same issue. Can't access bing.com on android with DoT

    • Jardel
    • 7 mths ago
    • Reported - view

    Disabling "Anonymized EDNS Client Subnet" the bing.com and Copilot back to online for me.

    • Jarek
    • 7 mths ago
    • Reported - view

    It works for me on all devices since yesterday. FYI, I connect to Warsaw servers.

    I guess Microsoft fixed some mistake in their configuration.

Login to reply

Content aside

  • 3 Likes
  • 7 mths agoLast active
  • 18Replies
  • 313Views
  • 11 Following