We lost the ability to browse web sites about 16:00 today via ourPlusNet is (still) working here.
Plusnet FTTC connection. Their DNS servers 212.159.6.9 and 212.159.13.49
are not responding to pings, nor is the gateway address 172.16.13.210.
I can still ping sites by IP address, and if I set my router to hand out OpenDNS's DNS server (207.67.222.222) as well as 192.168.1.1 (router)
when a PC does a DHCP request, normal service is resumed because the PC
now has a way of looking up address-to-IP.
I was hoping I could set the OpenDNS address at WAN level, but it looks
as if my router needs it to be per-PC (via DHCP).
I've tried all the normal things such as rebooting router and PCs.
On 05/01/2026 16:30, NY wrote:
We lost the ability to browse web sites about 16:00 today via ourPlusNet is (still) working here.
Plusnet FTTC connection. Their DNS servers 212.159.6.9 and 212.159.13.49
are not responding to pings, nor is the gateway address 172.16.13.210.
I can still ping sites by IP address, and if I set my router to hand out
OpenDNS's DNS server (207.67.222.222) as well as 192.168.1.1 (router)
when a PC does a DHCP request, normal service is resumed because the PC
now has a way of looking up address-to-IP.
I was hoping I could set the OpenDNS address at WAN level, but it looks
as if my router needs it to be per-PC (via DHCP).
I've tried all the normal things such as rebooting router and PCs.
What does the fault-reporter bot say about your connection?
On 05/01/2026 16:30, NY wrote:
We lost the ability to browse web sites about 16:00 today via our Plusnet >> FTTC connection. Their DNS servers 212.159.6.9 and 212.159.13.49 are notPlusNet is (still) working here.
responding to pings, nor is the gateway address 172.16.13.210.
I can still ping sites by IP address, and if I set my router to hand out
OpenDNS's DNS server (207.67.222.222) as well as 192.168.1.1 (router)
when a PC does a DHCP request, normal service is resumed because the PC
now has a way of looking up address-to-IP.
I was hoping I could set the OpenDNS address at WAN level, but it looks
as if my router needs it to be per-PC (via DHCP).
I've tried all the normal things such as rebooting router and PCs.
What does the fault-reporter bot say about your connection?
"BrightonRock" <harrymandispose-news@yahoo.com> wrote in message news:10jgpl2$30onu$1@nntp.eternal-september.org...Are you back now? I wouldn't assume that PlusNet do know about the
On 05/01/2026 16:30, NY wrote:
We lost the ability to browse web sites about 16:00 today via ourPlusNet is (still) working here.
Plusnet FTTC connection. Their DNS servers 212.159.6.9 and
212.159.13.49 are not responding to pings, nor is the gateway address
172.16.13.210.
I can still ping sites by IP address, and if I set my router to hand
out OpenDNS's DNS server (207.67.222.222) as well as 192.168.1.1
(router) when a PC does a DHCP request, normal service is resumed
because the PC now has a way of looking up address-to-IP.
I was hoping I could set the OpenDNS address at WAN level, but it
looks as if my router needs it to be per-PC (via DHCP).
I've tried all the normal things such as rebooting router and PCs.
What does the fault-reporter bot say about your connection?
The one on Plusnet's website www.plus.net? I've not tried that because
I've seen that downdetector.com is reporting a HUGE spike in problems
since about 15:45 today so I imagine PN are aware of the problem.
I'm running with opendns.com's DNS server - finally managed to find the hidden menu on my router which overrides the default DNS servers (PN's)
on the *WAN* connection so I can use my own. So I don't need to add this
DNS at LAN (client PC level).
On 05/01/2026 17:19, NY wrote:
"BrightonRock" <harrymandispose-news@yahoo.com> wrote in message
news:10jgpl2$30onu$1@nntp.eternal-september.org...
On 05/01/2026 16:30, NY wrote:
We lost the ability to browse web sites about 16:00 today via ourPlusNet is (still) working here.
Plusnet FTTC connection. Their DNS servers 212.159.6.9 and
212.159.13.49 are not responding to pings, nor is the gateway
address 172.16.13.210.
I can still ping sites by IP address, and if I set my router to hand
out OpenDNS's DNS server (207.67.222.222) as well as 192.168.1.1
(router) when a PC does a DHCP request, normal service is resumed
because the PC now has a way of looking up address-to-IP.
I was hoping I could set the OpenDNS address at WAN level, but it
looks as if my router needs it to be per-PC (via DHCP).
I've tried all the normal things such as rebooting router and PCs.
Are you back now? I wouldn't assume that PlusNet do know about the
reports on Downdetector. Or rather that they really are aware of the
problem that is causing those reports. They may know, they may not.
The bot I was thinking of is the one triggered from your mobile phone
that reports a possible fault and starts line tests. But that may be irrelevant today. For future reference: text Help to 07800008121
We lost the ability to browse web sites about 16:00 today via our
Plusnet FTTC connection. Their DNS servers 212.159.6.9 and 212.159.13.49
are not responding to pings, nor is the gateway address 172.16.13.210.
I can still ping sites by IP address, and if I set my router to hand out OpenDNS's DNS server (207.67.222.222) as well as 192.168.1.1 (router)
when a PC does a DHCP request, normal service is resumed because the PC
now has a way of looking up address-to-IP.
I was hoping I could set the OpenDNS address at WAN level, but it looks
as if my router needs it to be per-PC (via DHCP).
I've tried all the normal things such as rebooting router and PCs.
"BrightonRock" <harrymandispose-news@yahoo.com> wrote in message news:10jgpl2$30onu$1@nntp.eternal-september.org...
On 05/01/2026 16:30, NY wrote:
We lost the ability to browse web sites about 16:00 today via our Plusnet >>> FTTC connection. Their DNS servers 212.159.6.9 and 212.159.13.49 are not >>> responding to pings, nor is the gateway address 172.16.13.210.PlusNet is (still) working here.
I can still ping sites by IP address, and if I set my router to hand out >>> OpenDNS's DNS server (207.67.222.222) as well as 192.168.1.1 (router)
when a PC does a DHCP request, normal service is resumed because the PC >>> now has a way of looking up address-to-IP.
I was hoping I could set the OpenDNS address at WAN level, but it looks >>> as if my router needs it to be per-PC (via DHCP).
I've tried all the normal things such as rebooting router and PCs.
What does the fault-reporter bot say about your connection?
The one on Plusnet's website www.plus.net? I've not tried that because I've seen that downdetector.com is reporting a HUGE spike in problems since about 15:45 today so I imagine PN are aware of the problem.
I'm running with opendns.com's DNS server - finally managed to find the hidden menu on my router which overrides the default DNS servers (PN's) on the *WAN* connection so I can use my own. So I don't need to add this DNS at LAN (client PC level).
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 54 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 14:24:38 |
| Calls: | 742 |
| Files: | 1,218 |
| D/L today: |
3 files (2,681K bytes) |
| Messages: | 183,842 |
| Posted today: | 1 |