New - RBRE960 / RBSE960 Firmware Version 6.3.7.5 Released

The update itself worked fine (satellites first, router last, no factory reset), but I notice a weird regression with this version.

The RBKE963 mesh system is configured in AP mode, as stations of another router and I've given router and both satellites (internal-) DNS (A) records to access them more comfortably than having to remember their IP addresses. This worked fine with 6.0.3.85 and continues to work with 6.3.7.5 for the satellites, but the router only answers to its domain name with "500 Internal Server Error" (I can access the web interface via its IP address just fine).

router (affected):

http://172.21.253.36/ <-- works fine

http://rbre960/ (relying on the configured search domain) <-- 500 Internal Server Error

http://rbre960.fully.qualified.domain.example.com/ <-- 500 Internal Server Error

satellites (fine):

http://172.21.253.37/, http://rbse960-oben/, http://rbse960-oben.fully.qualified.domain.example.com/ <-- works fine
http://172.21.253.38/, http://rbse960-unten/, http://rbse960-unten.fully.qualified.domain.example.com/ <-- works fine

The name resolution works just fine, I can ping rbre960 and rbre960.fully.qualified.domain.example.com without any problem, it's just the webinterface that doesn't like being accessed by its externally configured domain name.

> nslookup rbre960
Server: router.fully.qualified.domain.example.com
Address: fd01:xxxx:xxxx:xxxx::1

Name: rbre960.fully.qualified.domain.example.com
Address: 172.21.253.36

> ping rbre960

Ping wird ausgeführt für rbre960.fully.qualified.domain.example.com [172.21.253.36] mit 32 Bytes Daten:
Antwort von 172.21.253.36: Bytes=32 Zeit<1ms TTL=64
Antwort von 172.21.253.36: Bytes=32 Zeit<1ms TTL=64
Antwort von 172.21.253.36: Bytes=32 Zeit<1ms TTL=64
Antwort von 172.21.253.36: Bytes=32 Zeit<1ms TTL=64

Ping-Statistik für 172.21.253.36:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 0ms, Maximum = 0ms, Mittelwert = 0ms

(configured lan network, 172.20.0.0/14)

This worked fine in the previous version and is reproducible in the current versions of firefox, chrome and edge (including incognito mode of either of them).