Xref: utzoo comp.unix.internals:1612 comp.protocols.tcp-ip.domains:545 Path: utzoo!utgpu!watserv1!watmath!att!bu.edu!rpi!zaphod.mps.ohio-state.edu!samsung!cs.utexas.edu!yale!ox.com!ox.com!emv From: emv@ox.com (Ed Vielmetti) Newsgroups: comp.unix.internals,comp.protocols.tcp-ip.domains Subject: Re: segmentation fault with long host names Message-ID: Date: 22 Dec 90 02:19:16 GMT References: <1990Dec20.203518.24899@cs.widener.edu> Sender: usenet@ox.com (Usenet News Administrator) Organization: OTA Limited Partnership, Ann Arbor MI. Lines: 25 In-Reply-To: brendan@cs.widener.edu's message of 20 Dec 90 20:35:18 GMT In article <1990Dec20.203518.24899@cs.widener.edu> brendan@cs.widener.edu (Brendan Kehoe) writes: Whenever I try to do any operation on the name kfps-roble6-dynamic.stanford.edu with ping, telnet, ftp, etc, I get "Segmentation fault". It's segmentation faulting in the dn_expand routine under ultrix 4.1. I used to sit in front of an Apollo called "starbarlounge.cc.umich.edu", but that long name was still only 13 characters per part. kfps-roble6-dynamic is 19 characters. the way I read RFC 1123 it requires it be able to handle 63 character host names. the way I read rfc 952 it says any part can be up to 24 characters. allegedly there was a machine called "car-crash-set-to-music.lcs.mit.edu", which should still be legal. nothing in the multi-homed hosts discussion suggests that there is a limit on the number of A records per host, but I might have missed something. kfps...6 has at least 26. there's a kfps...7 for which things seem to work, nice test case. --Ed emv@ox.com (note short snappy domain name) (at least until namedroppers or the bind list mangles it)