on 19-05-2012 13:32
I just installed a new Superhub and it worked pretty well out of the box. Usual messing around getting it set up, but wired and wireless connections worked fine. Until I came to use my main machine which has a static IP address (good reasons not relevant here). It could see the other machines on my network. I could log in and do management stuff on the superhub (including making sure that the DHCP range did not intersect the static address); the hub could see the static address (big label on the DHCP server page: STATIC ADDRESS) but it could not see the web: could not find server stuff. The DNS address was OK. The machine was on the trusted list. Switching to DHCP and restarting the connection got me through (and here I am), so it is definitely something to do with the way the superhub handles a static address. Ideas anyone ?
on 19-05-2012 14:31
on 20-05-2012 07:58
The network controlled by the Superhub is 192.168.0.xxx (although it can be changed via the admin logon). The superhub is the DNS for that network, forwarding all such requests to one of the upstream DNSs: 192.168.4.100 or 192.168.8.100. So any machine on the 192.168.0.xxx network *should* be able to access the upstream DNSs provided it has 192.168.0.1 in its own DNS field (which it did). It should not matter whether the address is 192.168.0.10, or 192.168.0.100 (as long as it is not 192.168.0.1 or 192.168.0.255 of course).
20-05-2012 10:08 - edited 20-05-2012 10:08
The Superhub does not seem to handle DNS resolution.
When using Static addresses on my Apple Macs, I could not get on the net without manually specifying the DNS server addresses.
Using DHCP, the Superhub told my Macs to automatically use the Virgin DNS servers, and not its local LAN IP (192.168.0.1) for DNS resolution.
20-05-2012 19:06 - edited 20-05-2012 19:17
The superhub is the DNS for that network, forwarding all such requests to one of the upstream DNSs: 192.168.4.100 or 192.168.8.100.
184.108.40.206 & 220.127.116.11
As I have said use real DNS IP's no point in saying what should happen because the hub does not work like that you DHCP to the hub in router mode you get VM DNS IP's you then NAT over with real DNS IP's therefore you must use real DNS IP's.
on 05-08-2012 16:27
I doubt it!
My super hub is acting the same.
The poster saying it MUST use an Internet DNS server missed the point that the DHCP server is required to act as the LOCAL DNS for the LAN. It does not. I have a number of devices on the LAN that get their DHCP address from the Superhub but if I try to access one by name, my readynas of example, it will not resolve it. Even though its in the DHCP table and has the correct host name.
One seriously wonders who the 'advanced' interface was aimed at! The lack of basic router functionally is frankly appalling.
on 24-10-2012 22:16
I've got the same problem.
Adding VMs public DNS IPs into the computers with the static address sorts it (I used 18.104.22.168 if anyones interested) but is there anything I can set in the SuperHub that'll fix this centrally? Like the first poster, I have a few statically assigned bits of kit and it'd be much easier if possible.
on 25-10-2012 14:28
For anyone interested - I solved this by having to:
a) Change my scope to include the statically assigned IP Addresses
b) Add the IP addresses into the reservation list.
Why this should make a difference is beyond me, but it does. Hope that helps someone else.