Re: major DNS hiccup
- From: noone@xxxxxxxxxxx (Speechless)
- Date: Tue, 11 Jul 2006 00:40:44 GMT
On Thu, 06 Jul 2006 18:09:50 GMT, Mike Scott
<usenet.10@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
This was all working fine until this afternoon - when I did nothing and
it just decided to malfunction.
Software doesn't just "break" on its own so, I suspect a hardware
problem.
You seem to have looked at everything except your cables.
COMMUNICATION CABLES: Visually inspect for physical damage.
From the utility poll to your building: Tree branches rubbing againstservice cables.
In the building: Squirrels, mice, other vermin gnawing/chewing on
cables.
In the room: physical damage from being stepped on, damage by floor
cleaning equipment, etc.
Purchase a new cable of known good quality and swap it in and out with
existing cables connecting wall jack to modem, modem to computer, etc.
SURGE PROTECTORS: Partially fried.
Partially fried surge protectors will have you going nuts chasing
intermittent problems, especially those that are used on the phone
lines. Many high-end power bars and UPSs have phone line surge
protectors built in -- you see those two phone jacks on these devices.
If you are using any phone line surge protectors, try disconnecting
them and see if your problem clears up.
PHONE JACKS: Misconnected equipment.
If your premises are wired with a dual phone jack system where you
have dial tone on both jacks but, one is labelled "Voice" and the
other is labelled "Data", make sure your phones, answering machines,
fax machines, etc., are plugged into the one labelled "Voice" and only
your modem is plugged into the one labelled "Data". (People make the
mistake of plugging in the Fax machine into the "Data" jack. It
should be plugged into the "Voice" jack.)
FAULTY TELECOM EQUIPMENT:
Disconnect all your telephones, fax machines, answering machines,
leaving just your modem connected to see if the problem disappears.
If the problem disappears, plug the other devices back in, one at a
time, until the problem reappears. The last device plugged in when
the problem reappears is the culprit.
NOISY LINES:
Pick up your telephone, dial a single digit, any digit, to make the
dial tone disappear, then LISTEN. What do you hear? If you hear
anything other than total silence, such as pops, clicks, static, have
your phone company fix the problem.
MISINSTALLED ALARM MONITORING SYSTEMS/
ENTERPHONE SYSTEMS:
The goofballs that install these things tend to hook them up to the
first pair of wires they find that give dial tone, and not necessarily
to the pair of wires supplying service to the owner of the alarm
system.
If you have one of these systems, you may have it hooked up on your
"Data" side of the service instead of on the "Voice" side of the
service where it should be.
If there are other tenants in the same building, you may have one of
your neighbor's systems hooked on to your phone service.
You should have the service circuit traced from your utility poll
right to your modem to make sure nothing else is hooked on to it.
OTHER HUMANS:
Those cables connecting the wall jack to modem and modem to computer,
etc., are they the cables that were there, or are they the cables
that were swapped by someone whose cables didn't work?
I'm quite certain that there are a whole bunch other things that
skipped my mind at the moment but, this should give you some clues
where else you should look.
Running 6.1, with named, which also acts as master for a private TLD
behind a firewall. Configuration files untouched for a year or more,
been working fine since the upgrade to 6.1 a month or two back.
Today, I suddenly found that DNS responses from the net often look
wrong. Using ethereal, I see that returned DNS answer packets often come
back with success, but no result records, which isn't good news.
Sometimes ethereal flags a 'format error', whatever that is; such
packets still have no results, and also no question either. The private
TLD works fine - it's only stuff from the net that's affected, but /not/
everything.
sockstat reports named is running with port 53 open on various
addresses. I've restarted named and even rebooted to no avail.
If I remove 127.0.0.1 from resolv.conf, and replace with my ISP's name
servers, DNS from the net at large works just fine (although obviously
my private TLD now fails).
On the offchance the problem was the NIC to the cable modem, I've
changed that; no joy though. Anyway, if there were a bad fault there,
I'd expect to see other problems as well.
This one seems to fall heavily into the "can't happen" category, and I'm
stuck for ideas: would /very/ much appreciate pointers about where to look.
Thanks in advance.
--
Please use the corrected version of the address below for replies.
Replies to the header address will be junked, as will mail from
various domains listed at www.scottsonline.org.uk
Mike Scott Harlow Essex England.(unet -a-t- scottsonline.org.uk)
.
- Follow-Ups:
- Re: major DNS hiccup
- From: Mike Scott
- Re: major DNS hiccup
- References:
- major DNS hiccup
- From: Mike Scott
- major DNS hiccup
- Prev by Date: use 'dd' as remote system duplication tool.
- Next by Date: Re: use 'dd' as remote system duplication tool.
- Previous by thread: Re: major DNS hiccup
- Next by thread: Re: major DNS hiccup
- Index(es):
Relevant Pages
|
