DNS problems again ?
Any particular reason why DNS has gone all cranky again as of fairly recently ... or is it just me ? because there's no service.status or other complaints that I can see.
However, 212.159.13.49 doesn't appear to be responding at all to any DNS queries but it does respond to a tracert and so on. I'm just getting a timeout on any DNS query. 212.159.13.50 does still appear to be working largely as it should be but it's unbelievably slow needless to say no doubt due to being grossly overworked and all that. Everything's slowly grinding to an almost complete halt via pte-ag1
I saw a few intermittent occasions over the weekend when something similar seemed to be happening but it's definitely looking a bit permanent now. Maybe someone could wander over and threaten it with a big stick or otherwise give it a good kick or something ?
However, 212.159.13.49 doesn't appear to be responding at all to any DNS queries but it does respond to a tracert and so on. I'm just getting a timeout on any DNS query. 212.159.13.50 does still appear to be working largely as it should be but it's unbelievably slow needless to say no doubt due to being grossly overworked and all that. Everything's slowly grinding to an almost complete halt via pte-ag1
I saw a few intermittent occasions over the weekend when something similar seemed to be happening but it's definitely looking a bit permanent now. Maybe someone could wander over and threaten it with a big stick or otherwise give it a good kick or something ?
Yeah, and it's working here again as well now 
Pity that no one was apparently able to give any official response over the last 9+ hours as to if/why it was AWOL earlier today (as indeed it also appears to have been on various other occasions particularly over recent days) because I can't see any service.status which appears that relevant to DNS stylee issues like this. Several second delays on each/every look-up when using the secondary server doesn't exactly give the best of browsing experience to say the least ! But then again it did lead to me pulling the plug and wandering off to do something sort of useful (for a change) rather than struggling along, getting annoyed or wasting my time/effort trying to work out was was (or wasn't) going on so not all bad news 
I also find it more than a bit strange that the DNS monitoring help/status page showing response times doesn't even hint at there being any problems either ! And neither has it done so in the past when there clearly has been some issue or other with at least some of the servers or when trying to access them via some gateways.
Is the DNS monitoring page currently showing an incomplete set of data or is it perhaps more a case of any monitoring that is being done is not really in any way representative of what a customer is actually experiencing in the Real World TM ? It seems very strange to me that there obviously was something more than a bit odd going on once again today but firstly, no one else seems particularly bothered about it and secondly, there's no problem at all according to the PN system monitoring and service.status pages. I can see a recent service.status relating to authoritative DNS servers but it's not really relevant to this by all accounts.
Pity that no one was apparently able to give any official response over the last 9+ hours as to if/why it was AWOL earlier today (as indeed it also appears to have been on various other occasions particularly over recent days) because I can't see any service.status which appears that relevant to DNS stylee issues like this. Several second delays on each/every look-up when using the secondary server doesn't exactly give the best of browsing experience to say the least ! But then again it did lead to me pulling the plug and wandering off to do something sort of useful (for a change) rather than struggling along, getting annoyed or wasting my time/effort trying to work out was was (or wasn't) going on so not all bad news I also find it more than a bit strange that the DNS monitoring help/status page showing response times doesn't even hint at there being any problems either ! And neither has it done so in the past when there clearly has been some issue or other with at least some of the servers or when trying to access them via some gateways.
Is the DNS monitoring page currently showing an incomplete set of data or is it perhaps more a case of any monitoring that is being done is not really in any way representative of what a customer is actually experiencing in the Real World TM ? It seems very strange to me that there obviously was something more than a bit odd going on once again today but firstly, no one else seems particularly bothered about it and secondly, there's no problem at all according to the PN system monitoring and service.status pages. I can see a recent service.status relating to authoritative DNS servers but it's not really relevant to this by all accounts.
F9, PN and BT authoritative name servers various - ns1.force9.net and so on. Not the servers [generally] used directly by customers for random queries.
The recommended DNS servers are 212.159.13.49/50 according to the help pages ... although my connection generally seems to obtain 212.159.6.9/10 when connecting and always has done. Dunno why but I seem to remember reading somewhere that all roads lead to the same bunch of actual servers via load-balancers anyway so it quite possibly doesn't matter which IP is actually specified. I always override the obtained IPs.
There's a whole bunch of others (such as 212.159.13.150) that are ns2.[whatever] as well of course which I would guess will be getting the same treatment at some later point in time if they haven't already had it.
The recommended DNS servers are 212.159.13.49/50 according to the help pages ... although my connection generally seems to obtain 212.159.6.9/10 when connecting and always has done. Dunno why but I seem to remember reading somewhere that all roads lead to the same bunch of actual servers via load-balancers anyway so it quite possibly doesn't matter which IP is actually specified. I always override the obtained IPs.
There's a whole bunch of others (such as 212.159.13.150) that are ns2.[whatever] as well of course which I would guess will be getting the same treatment at some later point in time if they haven't already had it.