Plus Two DNS Issues

[#1]

Personally, I think you're creating problems for yourself with this behaviour.

Both the router's firewall and the native security solutions provided with most modern operating systems are pefectly adequate in terms of keeping you safe. Add to this the fact that many applications these days expect an always-on connection, and that probably includes your security software.

If you can browse then the problem cannot be solely the fault of the router's DNS forwarding/DHCP allocation. Browsing wouldn't be possbile if it was. You also say you've tried explicitly setting DNS on the affected machine itself and this hasn't helped. In this configuration the router has very little to do with the DNS resolution process.

During a time the problem exists, what is the output of the commands below?: -

route print
nslookup bbc.co.uk 212.159.6.10
nslookup bbc.co.uk 192.168.1.254

Whilst I recognise you don't have this problem with the Hub One, I'm still not seeing anything specific that suggests the router is doing something it shouldn't, and given the niche setup you have, it's going to be very tricky to replicate.

[#2]

Hello Bob.

Route print while disconnected and then reconnected (with connection error problems) and then after ipconfig /release, /flushdns, and /renew is exactly the same so I have just included one:

===========================================================================
Interface List
2...f0 1f af 20 d1 03 ......Intel(R) 82579LM Gigabit Network Connection
6...3c a9 f4 51 45 44 ......Intel(R) Centrino(R) Ultimate-N 6300 AGN
17...3c a9 f4 51 45 45 ......Microsoft Wi-Fi Direct Virtual Adapter
12...3e a9 f4 51 45 44 ......Microsoft Wi-Fi Direct Virtual Adapter #2
1...........................Software Loopback Interface 1
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.254 192.168.1.112 25
127.0.0.0 255.0.0.0 On-link 127.0.0.1 331
127.0.0.1 255.255.255.255 On-link 127.0.0.1 331
127.255.255.255 255.255.255.255 On-link 127.0.0.1 331
192.168.1.0 255.255.255.0 On-link 192.168.1.112 281
192.168.1.112 255.255.255.255 On-link 192.168.1.112 281
192.168.1.255 255.255.255.255 On-link 192.168.1.112 281
224.0.0.0 240.0.0.0 On-link 127.0.0.1 331
224.0.0.0 240.0.0.0 On-link 192.168.1.112 281
255.255.255.255 255.255.255.255 On-link 127.0.0.1 331
255.255.255.255 255.255.255.255 On-link 192.168.1.112 281
===========================================================================
Persistent Routes:
None

IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
1 331 ::1/128 On-link
2 281 fe80::/64 On-link
2 281 fe80::9cf:65a5:b63d:33d5/128
On-link
1 331 ff00::/8 On-link
2 281 ff00::/8 On-link
===========================================================================
Persistent Routes:
None

Nslookup bbc.co.uk 212.159.6.10 after reconnection (and connection error problems) and then after ipconfig /release, /flushdns, and /renew is exactly the same so I have just included one:

Server: cdns02.plus.net
Address: 212.159.6.10

Non-authoritative answer:

Name: bbc.co.uk
Addresses: 2a04:4e42::81
2a04:4e42:200::81
2a04:4e42:400::81
2a04:4e42:600::81
151.101.0.81
151.101.64.81
151.101.128.81
151.101.192.81

Nslookup bbc.co.uk 192.168.1.254 after reconnection (and connection error problems) and then after ipconfig /release, /flushdns, and /renew is exactly the same so I have just included one:

Server: UnKnown
Address: 192.168.1.254

Non-authoritative answer:

Name: bbc.co.uk
Addresses: 2a04:4e42::81
2a04:4e42:200::81
2a04:4e42:400::81
2a04:4e42:600::81
151.101.0.81
151.101.64.81
151.101.128.81
151.101.192.81

Thanks for all your help so far.

I understand there are plans to move the phone network to IP by 2025 and therefore phones will need to be connected via the router. Do you happen to know if just a broadband connection would be needed to make and receive phone calls or would an internet connection also be required?

[#3]

At a cursory glance, I can't see anything untoward with any of that output, and the nslookup commands in particular show that DNS resolution is perfectly fine both direct to the server and via the hub's DNS forwarder.

Any VoIP telephony service will require an active Internet/IP session. The physical data link would not be sufficient.

[#4]

@bobpullen 

"Any VoIP telephony service will require an active Internet/IP session. The physical data link would not be sufficient."

Do mobile phone connections rely on an active Internet/IP session? Or do they rely on stuff below the IP level? I'm thinking not, as my mobile doesn't "do" the internet. In case you're wondering, I only have a minibrick for two-factor authentication of financial stuff. Separating technologies makes things just that little more secure.

This is going to go off-topic, I suspect. I will note that banking institutions have previously abandoned VoIP. Which may explain why they like their customers to have a separate technology path for 2-factor authentications. They do prefer a mobile number, even if it is only used for text messaging services.

[#5]

@bobpullen and everyone else who tried to help, thanks.

It looks like one of these problems that isn't going to be solved so I'll leave it at that.

[#6]

@Harddrive - you may want to have a read of this .

[#7]

Thanks.