Ask
Reply
Solution
13-05-2017 10:32 PM
I have a domain name that resolves to a number of servers at home. They are all for personal use, I just have this so I can get to them when I am out and about.
I have some links to the domain names in my favourites and all was fine. After I updated to 5.4.8.1.271.1.59 though the links work externally to my network. If you are on my network however the URLs no longer resolve. I can happily access the services with the IP address.
I tried setting up a DNS on an internal server however it appears you cannot set the DNS on the router to a server on the local network, it only seems to work if the server is external.
Feels like something was done that seperates the Wan routing from the LAN routing somehow. i.e. the domain name resolves the WAN ipaddress of the server on the LAN and yet it is not forwarded to the internal server as definded in the port rules.
What can I do about this?
14-05-2017 08:49 AM
Hi @tre4bax
The best way to get a quick answer to the problem is to contact the Broadband Team direct. They will be able to advise further. Please see below.
14-05-2017 07:17 PM - edited 14-05-2017 07:18 PM
Hi teb4ax
Quick answer.. VF router is broken, we know that.
I also have devices behind mine that I refer to by hostname. Always worked fine with my previous setup, but I digress.
Disable the marvelous VF DHCP service on your router.
Set up a DHCP server of your own (I'm a linux guy.. isc? Other products are available) which gives all the clients the DNS server(s) on your network.
Worked for me... other issues exist.
HTH
Quick postscript, do not contact the BB team... you have way more clue than them.
14-05-2017 07:30 PM - edited 14-05-2017 07:40 PM
Replying to self here, for which I should be shot, but I'm new to VF BB. And I must say that with other providers it was actually the same in my experience that the external WAN ip wouldn't work internally. Therfore a need for your own local name servers.
But... hmm... my remaining bugbear. Are you a Unix/linux person? Try a dig . Maybe dig @yournameserver then a dig @ipofrouter
Good luck. Stuck with forwarders .
14-05-2017 09:44 PM
Ouch. Not good to hear. I was doing resolving using dnsmasq so I can just add DHCP to that.
What a pain. Wish I hadn't upgraded but doing that risks challenges itself.
15-05-2017 01:09 PM