# MQTT via IPv6 on broker.hivemq.com **URL:** \ **Category:** HiveMQ Cloud\ **Created:** [November 29, 2025, 10:32am UTC](https://community.hivemq.com/t/mqtt-via-ipv6-on-broker-hivemq-com/3951 "2025-11-29T10:32:04Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![GeorgBraunHM](https://avatars.discourse-cdn.com/v4/letter/g/f05b48/32.png) [@GeorgBraunHM](https://community.hivemq.com/u/GeorgBraunHM)\ **Post date:** [November 29, 2025, 10:32am UTC](https://community.hivemq.com/t/mqtt-via-ipv6-on-broker-hivemq-com/3951/1 "2025-11-29T10:32:04Z")
Dear HiveMQ Team, I am using `broker.hivemq.com` for my IoT lecture at Hochschule München. Thanks a lot for providing this public, free-of-charge service. When the FQDN `broker.hivemq.com` is resolved to IP-Adresses via DNS, IPv6 addresses are first returned, followed by some IPv4 addresses. Connecting to `broker.hivemq.com` via IPv4 works fine as usual. However, using the IPv6 addresses, an MQTT connection is not possible. This could either be a client problem on our side (we are using various MQTT tools and some Python libraries), or, it could be that `broker.hivemq.com` does not support MQTT via IPv6. As a workaround, we are currently using [www.mqtt-dashboard.com](http://www.mqtt-dashboard.com) , which seems to be a DNS alias for `broker.hivemq.com` but is resolved only to IPv4, which keeps our clients functional. So I have 2 questions: 1. Is the broker on [broker.hivemq.com](http://broker.hivemq.com) supporting MQTT via IPv6? 2. Is it save to rely on that [www.mqtt-dashboard.com](http://www.mqtt-dashboard.com) is resolved to IPv4 only? Many thanks and best regards, Georg ---
**Author:** ![Daria\_H](https://avatars.discourse-cdn.com/v4/letter/d/dfb087/32.png) [@Daria\_H](https://community.hivemq.com/u/Daria_H)\ **Post date:** [December 1, 2025, 8:32am UTC](https://community.hivemq.com/t/mqtt-via-ipv6-on-broker-hivemq-com/3951/2 "2025-12-01T08:32:02Z")
Hi @GeorgBraunHM Welcome to the HiveMQ Community. It’s great to have you here, and we’re glad you’re exploring MQTT and HiveMQ. At this time, `broker.hivemq.com` does **not** support MQTT connections over IPv6. Although some DNS queries may return IPv6 records, the broker itself is only reachable via IPv4. If your MQTT client supports connections **only via IP address** rather than a fully qualified domain name (FQDN), you may use a workaround by resolving the hostname first and then connecting using the resulting IPv4 address. For example: ```auto ~ » nslookup broker.hivemq.com Server: 192.168.2.1 Address: 192.168.2.1#53 Non-authoritative answer: Name: broker.hivemq.com Address: 3.124.233.95 Name: broker.hivemq.com Address: 3.120.52.75 Name: broker.hivemq.com Address: 3.120.253.146 Name: broker.hivemq.com Address: 3.121.19.141 Name: broker.hivemq.com Address: 35.157.13.55 Name: broker.hivemq.com Address: 3.120.17.26 Name: broker.hivemq.com Address: 3.127.155.35 Name: broker.hivemq.com Address: 3.74.147.108 ``` Please be aware that these IP addresses can change periodically—typically only a few times per year—so they should not be considered fully reliable for long-term static configuration. We hope this information is helpful. If you have any further questions, please feel free to reach out. Kind regards, Dasha from HiveMQ Team ---
**Author:** ![GeorgBraunHM](https://avatars.discourse-cdn.com/v4/letter/g/f05b48/32.png) [@GeorgBraunHM](https://community.hivemq.com/u/GeorgBraunHM)\ **Post date:** [December 23, 2025, 10:06am UTC](https://community.hivemq.com/t/mqtt-via-ipv6-on-broker-hivemq-com/3951/3 "2025-12-23T10:06:06Z")
Dear Dasha and MiveMQ Team, thanks for your reply. Using static IPv4 addresses is not an option, since they can become invalid at any time as you already mentioned. For our own programs, which are implemented in CPython and MicroPython, we can make sure that the DNS-Lookup-Results are filtered for IPv4. So we have a solution for this use case. However, there are applications, like the famous “IoT MQTT Panel” on `[https://play.google.com/store/apps/details?id=snr.lab.iotmqttpanel.prod\`](https://play.google.com/store/apps/details?id=snr.lab.iotmqttpanel.prod%5C%60) and on `https://apps.apple.com/us/app/iot-mqtt-panel/id6466780124` where we have no access to the source code. For such applications, it is a killer when DNS provides an IPv6 address without having MQTT on IPv6. Our current workaround is to replace `broker.hivemq.com` with `www.mqtt-dashboard.com` This seems to work quite stable, as `www.mqtt-dashboard.com` is currently resolved to IPv4 address only. So my remaining question is: Is it save to use `www.mqtt-dashboard.com` for the time being to get working IPv4 MQTT connections? Many thanks and best regards, Georg ---
**Author:** ![Daria\_H](https://avatars.discourse-cdn.com/v4/letter/d/dfb087/32.png) [@Daria\_H](https://community.hivemq.com/u/Daria_H)\ **Post date:** [December 29, 2025, 8:46am UTC](https://community.hivemq.com/t/mqtt-via-ipv6-on-broker-hivemq-com/3951/4 "2025-12-29T08:46:40Z")
Hi @GeorgBraunHM Thank you for your questions. We appreciate you taking the time to look into this and are happy to clarify. Please note the following points: 1. **[broker.hivemq.com](http://broker.hivemq.com)** and **[www.mqtt-dashboard.com](http://www.mqtt-dashboard.com)** are functionally served from the same underlying system; they are simply accessed via different DNS names. To verify this, you can run the commands below and compare their outputs: ```auto nslookup broker.hivemq.com nslookup www.mqtt-dashboard.com ``` 1. **IPv6 support** : At this time, this does does not support IPv6 for the MQTT protocol. If an IPv6 address is resolved, the connection will fall back to IPv4. 2. **IP address changes** : The IP addresses associated with **[broker.hivemq.com](http://broker.hivemq.com)** or **[www.mqtt-dashboard.com](http://www.mqtt-dashboard.com)** may change. For this reason, we recommend using the DNS names rather than hardcoding IP addresses. We hope this information is helpful. Please do not hesitate to reach out if you have any further questions or need additional assistance. Kind regards, Dasha from The HiveMQ Team