1

Issues with 45.90.28.x?

I'm seeing intermittent timeouts from 45.90.28.x:

# dig @45.90.28.163 us.mqtt.bambulab.com AAAA
;; communications error to 45.90.28.163#53: timed out
;; communications error to 45.90.28.163#53: timed out
;; communications error to 45.90.28.163#53: timed out
; <<>> DiG 9.20.15-1~deb13u1-Debian <<>> @45.90.28.163 us.mqtt.bambulab.com AAAA
; (1 server found)
;; global options: +cmd
;; no servers could be reached

The DNS server (45.90.28.163) is pingable.  The secondary, 45.90.30.163, responds to the same query without any issues.

I've disabled 45.90.28.163 for now, which appears to have fixed the issue but leaves me with a single upstream DNS server.

Could someone from NextDNS look into this please?  I'm happy to help with troubleshooting.

2 replies

null
    • aix
    • 3 wk ago
    • Reported - view

    Further observations:

    1. Sometimes, 45.90.28.163 does respond.  When it has, it then keeps responding to the same query for a short while before starting to time out again.  (Seems like some caching/TTL thing, though I haven't tried to correlate it with anything.)
    2. I'm yet to see 45.90.30.163 time out once.
    3. 45.90.28.0 and 45.90.30.0 behave exactly as do the .163 (.28.0 times out, while .30.0 does not).
    • serval
    • 4 days ago
    • Reported - view

    ay, same. i got 45.90.28.186, ipv4 only. i'm on linux, it's been going out CONSTANTLYYY.

Login to reply

Content aside

  • 1 Votes
  • 4 days agoLast active
  • 2Replies
  • 61Views
  • 2 Following