# DNS
You need to configure your router to point DNS locally to where Bumper is running.  
The easiest way is overriding the main domains used by EcoVacs using DNSMasq/PiHole, by adding address entries in a custom config.

## Custom DNSMasq Config

Typically written at /etc/dnsmasq.d/{##}-{name}.conf  
  - Ex: `/etc/dnsmasq.d/02-custom.conf`

**File Contents:**
````
address=/ecouser.net/{bumper server ip}
address=/ecovacs.com/{bumper server ip}
address=/ecovacs.net/{bumper server ip}
````
**Note:** *Replace `{bumper server ip}` with your server's IP*

If using PiHole, reload FTL to apply changes:
  
  `sudo service pihole-FTL reload`

## Manual Override

If overriding DNS for the top-level domains isn't an option, you'll need to configure your router DNS to point a number of domains used by the app/robot to the Bumper server.  

**Note:** Depending on country, your phone/robot may be using a different domain.  Most of these domains contain country-specific placeholders.  

Not all domains have been documented at this point, and this list will be updated as more are identified/seen. The preferred way to ensure Bumper works is to override the full domains as above.
**Note:** The app dynamically gets the required domains from the endpoint `api/appsvr/service/list` and therefore ecovacs can use different domains for different models.

Replacement Examples:

  - {countrycode}
    - If you see `eco-{countrycode}-api.ecovacs.com` and you live in the US/North America you would use: `eco-us-api.ecovacs.com`
    - **Note**: {countrycode} may also be generalized regions such as "EU".
  - {region}
    - If you see `portal-{region}.ecouser.net` and you live in the US/North America you would use: `portal-na.ecouser.net`
    - **Note**: {region} may also be generalized regions such as "EU".
    

| Address                                 | Description                                    |
| --------------------------------------- | ---------------------------------------------- |
| `lb-{countrycode}.ecovacs.net`          | Load-balancer that is checked by the app/robot |
| `lb-{countrycode}.ecouser.net`          | Load-balancer that is checked by the app/robot |
| `lbus.ecouser.net`                      | Load-balancer that is checked by the app/robot |
| `lb{countrycode}.ecouser.net`           | Load-balancer that is checked by the app/robot |
| `eco-{countrycode}-api.ecovacs.com`     | Used for Login                                 |
| `gl-{countrycode}-api.ecovacs.com`      | Used by EcoVacs Home app                       |
| `gl-{countrycode}-openapi.ecovacs.com`  | Used by EcoVacs Home app                       |
| `portal.ecouser.net`                    | Used for Login and Rest API                    |
| `portal-{countrycode}.ecouser.net`      | Used for Login and Rest API                    |
| `portal-{region}.ecouser.net`           | Used for Login and Rest API                    |
| `portal-ww.ecouser.net`                 | Used for various Rest APIs                     |
| `msg-{countrycode}.ecouser.net`         | Used for XMPP                                  |
| `msg-{region}.ecouser.net`              | Used for XMPP                                  |
| `msg-ww.ecouser.net`                    | Used for XMPP                                  |
| `mq-{countrycode}.ecouser.net`          | Used for MQTT                                  |
| `mq-{region}.ecouser.net`               | Used for MQTT                                  |
| `mq-ww.ecouser.net`                     | Used for MQTT                                  |
| `gl-{countrycode}-api.ecovacs.com`      | Used by Ecovacs Home app for API               |
| `recommender.ecovacs.com`               | Used by Ecovacs Home app                       |
| `bigdata-international.ecovacs.com`     | Telemetry/tracking                             |
| `bigdata-northamerica.ecovacs.com`      | Telemetry/tracking                             |
| `bigdata-europe.ecovacs.com`            | Telemetry/tracking                             |
| `bigdata-{unknown regions}.ecovacs.com` | Telemetry/tracking                             |
| `api-app.ww.ecouser.net`                | Api for App (v2+)                              |
| `api-app.dc-{region}.ww.ecouser.net`    | Api for App (v2+)                              |
| `users-base.dc-{region}.ww.ecouser.net` | Accounts for App (v2+)                         |
| `jmq-ngiot-{region}.dc.ww.ecouser.net`  | MQTT for App (v2+)                             |
| `api-rop.dc-{region}.ww.ecouser.net`    | App (v2+)                                      |
| `jmq-ngiot-{region}.area.ww.ecouser.net`| App (v2+)                                      |

## Newer Bots: Port 443 Redirect (jmq-ngiot protocol)

Some newer robots (confirmed: OZMO 920 series) do **not** connect to Bumper on the standard MQTT port (8883). Instead they connect on **port 443**, likely to bypass firewall restrictions. The bot uses a `jmq-ngiot-{countrycode}.area.ww.ecouser.net` hostname for this connection.

Because Bumper's MQTT server listens on 8883, connections arriving on 443 must be redirected using `iptables`:

```bash
# Redirect bot MQTT traffic from port 443 → 8883
# Replace 192.168.x.x with your bot's IP address
sudo iptables -t nat -A PREROUTING -s 192.168.x.x -p tcp --dport 443 -j REDIRECT --to-port 8883
```

**How to find your bot's IP:** Check your router's DHCP client list, or run `sudo arp-scan --localnet` on the Bumper host.

**Note:** This rule does not persist across reboots. To make it permanent, use `iptables-persistent` (`sudo apt install iptables-persistent`) or add it to your startup script.

**To remove the rule** (e.g. to restore normal cloud access):
```bash
sudo iptables -t nat -D PREROUTING -s 192.168.x.x -p tcp --dport 443 -j REDIRECT --to-port 8883
```

**How to identify if your bot uses port 443:** After setting up DNS redirection, run `sudo tcpdump -i any -n "src host <bot-ip> and (port 443 or port 8883)"` and power-cycle the bot. If you see connections on port 443 with no activity on 8883, your bot needs this redirect.