Is it just me or are the Orcon DNS servers (121.98.0.1, 121.98.0.2) offline at the moment?
I've change to 8.8.8.8 and everything is working fine again.
Cheers
|
|
|
The views expressed by me are not necessarily those of my employer
Regards FireEngine
FireEngine: Our systems team are aware of it, looks like a dos attack is going on.
The views expressed by me are not necessarily those of my employer
Michael Murphy | https://murfy.nz
Referral Links: Quic Broadband (use R122101E7CV7Q for free setup)
Are you happy with what you get from Geekzone? Please consider supporting us by subscribing.
Opinions are my own and not the views of my employer.
michaelmurfy: Who has Orcon annoyed lately for this to occur?
michaelmurfy: Who has Orcon annoyed lately for this to occur?
Regards FireEngine
BigGuy: Is it just me or are the Orcon DNS servers (121.98.0.1, 121.98.0.2) offline at the moment?
I've change to 8.8.8.8 and everything is working fine again.
Cheers
Screeb: Yeah, I had the same problem (and solution). I noticed the same thing not long ago as well. How do both the primary and secondary servers die at the same time? That's pretty poor design if that happens... Maybe I'll just put Google's as the secondary.
ptinson:Screeb: Yeah, I had the same problem (and solution). I noticed the same thing not long ago as well. How do both the primary and secondary servers die at the same time? That's pretty poor design if that happens... Maybe I'll just put Google's as the secondary.
They get attacked at the same time?
Screeb:ptinson:Screeb: Yeah, I had the same problem (and solution). I noticed the same thing not long ago as well. How do both the primary and secondary servers die at the same time? That's pretty poor design if that happens... Maybe I'll just put Google's as the secondary.
They get attacked at the same time?
That's fair enough to some extent - I hadn't considered an attack at the time. However, one would think such a vital part of the service would be better protected against DoS attacks.
|
|
|