This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

URGENT...RED won't connect anymore still the current broker?

nslookup :


*** wurde von nicht gefunden: Server failed.

This thread was automatically locked due to age.
  • Maybe a temporary glitch.

    E.U. view: is an alias for is an alias for has address

    U.S. view: is an alias for is an alias for has address

    Google ( and Cloudflare ( both give US view when tested, and Telekom ( E.U view.

  • EU-IP does not resolve over here when using Telekom DNS

    EU-IP does resolve, when using MK Netzdienste DNS

    US-IP does resolve when using DSN or DSN

    Seems to be a Telekom problem.

    Mit freundlichem Gruß, best regards from Germany,

    Philipp Rusch

    New Vision GmbH, Germany
    Sophos Silver-Partner

    If a post solves your question please use the 'Verify Answer' button.

  • ~> dig @

    ; <<>> DiG 9.16.42 <<>> @
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34270
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

    ; EDNS: version: 0, flags:; udp: 512
    ;                        IN      A

    ;; ANSWER SECTION:         181     IN      CNAME     121     IN      CNAME 199     IN      A

    ;; Query time: 32 msec
    ;; SERVER:
    ;; WHEN: Thu Aug 03 20:24:12 CEST 2023
    ;; MSG SIZE  rcvd: 107

    Telekom DNS answers only if asked from a Telekom IP, it's not public accessible.

    We see such glitches often for names that make heavy use of geolocation (most notably

  • I'm unable to resolve it here in the U.S. either, using various lookup sites.

    OPNSense 64-bit | Intel Xeon 4-core v3 1225 3.20Ghz
    16GB Memory | 500GB SSD HDD | ATT Fiber 1GB
    (Former Sophos UTM Veteran, Former XG Rookie)

Reply Children