Re: major DNS hiccup
- From: Andrew Haley <andrew29@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 11 Jul 2006 15:07:13 -0000
Mike Scott <usenet.10@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Chronos wrote:
After replacing Mike Scott with a small shell script on Tuesday 11 Jul
2006 09:06, the following appeared on stdout:
Thanks, but as it's only DNS that's not working
And then only if you're doing fully recursive lookups. Is your hints
file up to date?
Yes.
Have you tried an alternate root such as ORSN?
I have now. Same problem (sample of 2 failure, 1 working).
But thanks for the ideas. Somehow I get the most horrible feeling this
will all be down to something incredibly obvious that I've just been
missing totally.....
It's NTL. I'm an NTL customer too, in Cambridge.
At the end of last week my local named started to fail in precisely
the same way that you describe. I struggled with the local named
config for a while, and then did the thing I should have done at the
start: I pulled the NTL cable modem and plugged in a Demon ADSL modem.
Hey presto: no changes at all to my configuration, everything started
to work perfectly. The only thing changed was the ISP!
My guess is that NTL are doing something totally clueless.
Andrew.
.
- Follow-Ups:
- Re: major DNS hiccup
- From: Andrew Haley
- Re: major DNS hiccup
- References:
- major DNS hiccup
- From: Mike Scott
- Re: major DNS hiccup
- From: Speechless
- Re: major DNS hiccup
- From: Mike Scott
- Re: major DNS hiccup
- From: Chronos
- Re: major DNS hiccup
- From: Mike Scott
- major DNS hiccup
- Prev by Date: Re: KDE Trashes twm
- Next by Date: Re: major DNS hiccup
- Previous by thread: Re: major DNS hiccup
- Next by thread: Re: major DNS hiccup
- Index(es):
Relevant Pages
|