[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cobalt-users] Cobalt bug nameServers???
- Subject: RE: [cobalt-users] Cobalt bug nameServers???
- From: "Brian A. Chase" <support@xxxxxxxxxxxxx>
- Date: Sun Jul 14 18:07:01 2002
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
Has Cobalt/Sun ever addressed this issue?
http://www.infoworld.com/articles/hn/xml/02/06/05/020605hnbindflaw.xml
CERT warns of another BIND problem
-----Original Message-----
From: cobalt-users-admin@xxxxxxxxxxxxxxx
[mailto:cobalt-users-admin@xxxxxxxxxxxxxxx]On Behalf Of Brian A. Chase
Sent: Sunday, July 14, 2002 7:34 PM
To: cobalt-users@xxxxxxxxxxxxxxx
Subject: [cobalt-users] Cobalt bug nameServers???
We have seen this from UUnet Cache DNS Servers and several other networks.
We haven't tracked down is it is a communication problem with Cobalt Servers
running bind but it usually clears up in a day.
If you run dig, you will see that the root and cobalt name servers respond
correctly but the UUnet/Worldcom servers do not see the records. This has
the effect of domains dropping off the net for a day or more.
If anyone has solved this, please post. Worldcom's response was "Use
another DNS". This of course is not a valid solution for the other 50
million Worldcom customers.
_________________________
Andy Brown wrote:
> I *think* I've seen this behaviour in some of our Raqs here, but what I
> ended up trying seemed to cure it.
> Out of interest have the machines been rebooted recently, or simply not
> ever had bind/named restarted manually??
> For some reason after a reboot our machines will start the
> /usr/sbin/named process but it won't answer queries in the way that you
> explain.
> If I ssh in and call a
> /etc/rc.d/init.d/named restart
> Give it a minute to settle down, and hey presto it starts to answer
> again, and will continue to do so after that point.
None of what you did should have made a difference to Frderik.
His system isn't using the named daemon on the RaQ at all; the
resolver's going right out the box to uu.net. The problem is probably,
as he suggests, is time-out based on slow connectivity.
Jeff
_______________________________________________
cobalt-users mailing list
cobalt-users@xxxxxxxxxxxxxxx
To Subscribe or Unsubscribe, please go to:
http://list.cobalt.com/mailman/listinfo/cobalt-users