I have a registered domain, for example foo.com hosted by site5.com
I have set up a host entry for my NAS which points to an address on my local network: nas.foo.com -> 192.168.1.99
When I was on Sky broadband, any device on my network could resolve this with nslookup nas.foo.com
Now I have switched to BT, the Home Hub 5 fails to resolve.
I checked against the BT name servers and this resolves:
dig @81.139.57.100 nas.foo.com@81.139.57.100 nas.foo.com
But it doesn't resolve using the DNS server in the HH.
dig @192.168.1.254 nas.foo.com
Any ideas? Or does BT really take standard products and the cripple them?
Hi,
I assume you only want to access the NAS from your LAN. If so it would be simpler to create a shortcut to the NAS drive and put a copy of the shortcut on each machine on the LAN. Like in the screen dump. Works fine here.
On the other hand if you want to access the NAS from the Internet you would need to set up port forwarding for the NAS.
See if this applies to you?
http://btsupport.custhelp.com/app/answers/detail/a_id/44044/c/6433
Some home hubs also do not allow NAT loopback.
@nigel_h wrote:Any ideas? Or does BT really take standard products and the cripple them?
Of course not. They design them like that
If you want to do anything out of the ordinary you'll need a decent router.
I have a router running advanced Tomato firmware which supports NAT loopback so you can access your internal servers using a FQDN.