home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.bsd
- Path: sparky!uunet!usc!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!hamblin.math.byu.edu!news.byu.edu!ux1!fcom.cc.utah.edu!cs.weber.edu!terry
- From: terry@cs.weber.edu (A Wizard of Earth C)
- Subject: Re: ref.tfs.com frequently unrecognized by DNS
- Message-ID: <1992Nov23.212117.11709@fcom.cc.utah.edu>
- Sender: news@fcom.cc.utah.edu
- Organization: Weber State University (Ogden, UT)
- References: <ellis.722460485@nova>
- Date: Mon, 23 Nov 92 21:21:17 GMT
- Lines: 29
-
- In article <ellis.722460485@nova> ellis@nova.gmi.edu (Stew Ellis) writes:
- >All day today, but frequently in the past as well, DNS, including nslookup,
- >has been unable to find ref, either by name or IP address. Is this
- >scheduled or unscheduled ( :) ) downtime?
- >
- >What causes ref to disappear from the route maps? How long does it have to
- >be down before it is taken out? How long does it take for it to propagate
- >when it comes back up?
-
- I had this problem too.. what I did was set my name server upstream until
- it showed up. The problem is that one of my servers upstream (cc.weber.edu)
- is incorrectly configured to not pass on non-authoritative answers. This
- could be your problem, especially if you have a Multinet host upstream.
-
- This may be correctable via workaround from Julian's end by uping the time
- to live for his address responses.
-
-
- Terry Lambert
- terry@icarus.weber.edu
- terry_lambert@novell.com
- ---
- Any opinions in this posting are my own and not those of my present
- or previous employers.
- --
- -------------------------------------------------------------------------------
- "I have an 8 user poetic license" - me
- Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
- -------------------------------------------------------------------------------
-