home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.hp
- Path: sparky!uunet!utcsri!helios.physics.utoronto.ca!alchemy.chem.utoronto.ca!system
- From: system@alchemy.chem.utoronto.ca (System Admin (Mike Peterson))
- Subject: Re: Problems with 'named'
- Message-ID: <1992Dec15.174038.10842@alchemy.chem.utoronto.ca>
- Keywords: named gated network TCP/IP problem trouble red alert
- Organization: University of Toronto Chemistry Department
- References: <1992Dec15.154406.2988@news.arc.nasa.gov>
- Date: Tue, 15 Dec 1992 17:40:38 GMT
- Lines: 42
-
- In article <1992Dec15.154406.2988@news.arc.nasa.gov> okuyama@pioneer.arc.nasa.gov (Darin Okuyama YR) writes:
- >I have an HP 9000/730 and I am running HP-UX 8.07. I have
- >'named' installed but it doesn't work to well, here are
- >the symptoms:
- >
- > -- only the 'root' seems to be served by 'named',
- > most things don't work for normal users (ftp,
- > telnet, nslookup, etc.). Here is the output
- > from an 'nslookup' session:
- >
- >*** Can't find address for server daxam: Non-existent domain
- >*** Warning - the local domain is not set.
- >*** Either hostname should be a domain name,
- >*** the domain should be specified in /etc/resolv.conf,
- >*** or the shell variable LOCALDOMAIN should be set.
- >
- > -- 'hostname' is returning a non-fully-qualified IP
- > name.
- > -- nobody (not even the root) can get the name server
- > to resolve address outside the domain (arc.nasa.gov).
-
- Unless your /etc/resolv.conf file contains nonsense, or you are
- resolving names by NIS instead of DNS, you may have fallen on the
- $INCLUDE bug in HP-UX named --- if you use $INCLUDE, it will destroy
- your named data, since things like SOA records in the included file
- are not seen, and IP address, etc, are garbled (many of ours got 255
- inserted into one of the fields, which were easy to spot from a database
- dump).
-
- This problem is not fixed in 9.0.
-
- We have compiled our own named from BSD source, and it works better
- but not perfectly (the $INCLUDE does work properly however). We still
- have timeouts resolving names that should be resolved quickly,
- and are resolved properly if nslookup is asked to find the name again
- immediately after the failure. Nslookup also complains about a lot
- of FORMAT ERRORS, with success upon a retry. This causes telnet, ping,
- mail to fail when there is nothing wrong.
- --
- core error - bus dumped -*- Mike Peterson, SysAdmin, U/Toronto Chemistry
- ******* As usual, I speak only for me, myself and I; nobody else *******
- E-mail: system@alchemy.chem.utoronto.ca Tel: (416)978-7094 Fax: (416)978-8775
-