Steve21 Posted June 29, 2015 Posted June 29, 2015 The following error was encountered while trying to retrieve the URL: Google Unable to determine IP address from host name ‘http://www.google.co.uk’ The DNS server returned: No DNS records This means that the cache was not able to resolve the hostname presented in the URL. Check if the address is correct. Your cache administrator is [email protected]. >.< Admit it, who turned the DNS servers off?! Steve 2
kennysarmy Posted June 29, 2015 Posted June 29, 2015 Took me 5 minutes to get this page to load to post this!!!
Steve21 Posted June 29, 2015 Author Posted June 29, 2015 Haha Man, I think I need to config Googles 8.8.8.8 DNS as a backup on our DCs when I get a spare minute (Assuming they'd work for DCs as well as clients). Seems this is happening more frequently recently... Steve
localzuk Posted June 29, 2015 Posted June 29, 2015 From SWGfL Investigating We are aware of an issue affecting connectivity in SWGfL. Our engineers are investigating this now. Further updates will be posted within the next 60 minutes Jun 29, 14:07 BST [TABLE=width: 100%] New Incident Status: Monitoring This incident is the result of a DDoS attack, our engineers have blocked the traffic and we are seeing services return to normal. We will continue to monitor the situation closely. Jun 29, 14:15 BST
Michael Posted June 29, 2015 Posted June 29, 2015 Interesting - but surely even the likes of RM must have many DNS servers deployed?
Steve21 Posted June 29, 2015 Author Posted June 29, 2015 They changed their minds though An Incident Update Has Been Posted We are experiencing a secondary incident that is also affecting customer browsing performance. Our engineers are currently investigating this. We will post further updates within the next 60 minutes Seems to always be DDOS oh wait no it's not kinda replies Steve
fairm010 Posted June 29, 2015 Posted June 29, 2015 Interesting - but surely even the likes of RM must have many DNS servers deployed? I imagine RM have one sat in a garage behind a house belonging to a chap named Neil collecting cobwebs whilst being powered by coal shovelled by a big bloke called Bob. 2
aleach2 Posted June 29, 2015 Posted June 29, 2015 We had it last week and the week before that down here in the SEGfL. Good old RM
newpersn Posted June 29, 2015 Posted June 29, 2015 An Incident Update Has Been Posted The secondary is now also resolved and our engineers are working to understand the route cause. User are reporting that service have returned to normal and we will continue to monitor the situation closely. This is starting to take the ****
aleach2 Posted June 29, 2015 Posted June 29, 2015 Wait till they give this ago. Last time they tried to do something with JANET we couldn't get the Internet for an entire morning:
Edu-IT Posted June 29, 2015 Posted June 29, 2015 At risk during the maintenance window, and, at any other time too?
sonofsanta Posted June 29, 2015 Posted June 29, 2015 Haha Man, I think I need to config Googles 8.8.8.8 DNS as a backup on our DCs when I get a spare minute (Assuming they'd work for DCs as well as clients). Seems this is happening more frequently recently... Steve Don't set Google DNS on clients anywhere, they need your domain DNS so they can resolve domain devices. On your DC, set the usual DNS on the network adapter (i.e. your DCs), then in DNS Management, right click on the DNS server, go to Properties, go to the Forwarders tab and add 8.8.8.8 and 8.8.4.4 in there. Works a treat there any time my ISP (thankfully no longer RM) has DNS issues, I reorder the list there so Google are at the top. Most of the time I forget to reorder it back. Works a charm.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now