Re: lpr: unable to get official name for local machine (fwd) fixed.
Name resolving works again on my machines! Still don't know what exactly happened though. It seems that the reason for bind not working out of the 1.3-box for me, is that I answered 'cr' where I should have answered 'nonecr' to bindconfig (at least that is the only difference that I can think of.) Looking at the files, the big difference was a missing '@' in front of the line for localhost. When I placed the '@' back in the configuration file on the machine that had a working named before the 1.3 upgrade, it worked again as well. Joost -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: lpr: unable to get official name for local machine (fwd)
On Thu, 5 Jun 1997, Nathan E Norman wrote: For what it's worth, I upgraded from 1.2 to 1.3 about a week ago on a server that is authoritative for a few zones ... no problems at all. I forgot to mention the following: I let the install script change my existing setup, did you do this too? I realise this doesn't assist you in solving your immediate problem, but I'm not so sure that the Debian package is to blame.. Well, I'm not really authoritative on bind matters, but I thought that on previous ( 1.3 ) installations, you could issue nslookup localhost and it would work then. Now I get: calypso# nslookup localhost *** Can't find server name for address 127.0.0.1: Non-existent host/domain *** Default servers are not available -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: lpr: unable to get official name for local machine (fwd)
On Fri, 6 Jun 1997, J.P.D. Kooij wrote: : :On Thu, 5 Jun 1997, Nathan E Norman wrote: : : For what it's worth, I upgraded from 1.2 to 1.3 about a week ago on a : server that is authoritative for a few zones ... no problems at all. : :I forgot to mention the following: I let the install script change my :existing setup, did you do this too? I believe I did - it certainly has the new style named.boot, etc. : : I realise this doesn't assist you in solving your immediate problem, but : I'm not so sure that the Debian package is to blame.. : :Well, I'm not really authoritative on bind matters, but I thought that on :previous ( 1.3 ) installations, you could issue nslookup localhost :and it would work then. Now I get: : : calypso# nslookup localhost : *** Can't find server name for address 127.0.0.1: Non-existent host/domain : *** Default servers are not available : Here's what I get when I execute 'nslookup localhost': Server: endor Address: 0.0.0.0 Name:localhost.cfni.com Address: 127.0.0.1 Notice that I did defy the package default of specifying the local IP address as a nameserver in resolv.conf and instead left it as 0.0.0.0, as the first edition BIND book suggests. I have no idea if this matters :) (I also would not call myself a BIND guru). I also see that I have a localhost entry in my primary SOA zone file ... and I don't have a named.local file, which named.options seems to expect to exist. It looks like I may have gotten lucky :) If you like I can send snippets of my zone files. etc. if that would somehow be helpful. -- Nathan Norman:Hostmaster CFNI:[EMAIL PROTECTED] finger [EMAIL PROTECTED] for PGP public key and other stuff Key fingerprint = CE 03 10 AF 32 81 18 58 9D 32 C2 AB 93 6D C4 72 -- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: lpr: unable to get official name for local machine (fwd)
Brian K Servis [EMAIL PROTECTED] writes: [snip] WAIT A MINUTE..I just discovered something as I was checking the log files. ifconfig is making kerneld try to load some net-pf-4 and net-pf-5 module? What is this? I can't find any reference to it in the kernel-source. %root% date ; ifconfig lo 127.0.0.1 Wed Jun 4 12:49:12 CDT 1997 [snippet of /var/log/daemon] Jun 4 12:49:12 servis modprobe: can't locate module net-pf-4 Jun 4 12:49:12 servis modprobe: can't locate module net-pf-5 This must be the root of the problem! Any pointers. Unfortunately this is unlikely. net-pf-4 and net-pf-5 are things like Appletalk and IPX, which you probably haven't compiled into your kernel. See `/etc/conf.modules'. I can't see what other problems there would be. Maybe someone else has experienced this and solved it? -- Carey Evans * [EMAIL PROTECTED] Lies, damn lies, and computer documentation. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: lpr: unable to get official name for local machine (fwd)
To me it looks like nameserving doesn't quite work out-of-the-box in upcoming debian 1.3. I've upgraded a box to frozen and that broke a working bind configuration, I don't know how badly because I haven't really had the time to look into it. On fresh installations, nslookup can't find even localhost. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: lpr: unable to get official name for local machine (fwd)
For what it's worth, I upgraded from 1.2 to 1.3 about a week ago on a server that is authoritative for a few zones ... no problems at all. I realise this doesn't assist you in solving your immediate problem, but I'm not so sure that the Debian package is to blame.. -- Nathan Norman:Hostmaster CFNI:[EMAIL PROTECTED] finger [EMAIL PROTECTED] for PGP public key and other stuff Key fingerprint = CE 03 10 AF 32 81 18 58 9D 32 C2 AB 93 6D C4 72 -- On Thu, 5 Jun 1997, J.P.D. Kooij wrote: : :To me it looks like nameserving doesn't quite work out-of-the-box in :upcoming debian 1.3. : :I've upgraded a box to frozen and that broke a working bind :configuration, I don't know how badly because I haven't really had the :time to look into it. :On fresh installations, nslookup can't find even localhost. : : : :-- :TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to :[EMAIL PROTECTED] . :Trouble? e-mail to [EMAIL PROTECTED] . : -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: lpr: unable to get official name for local machine (fwd)
Carey Evans writes: Brian K Servis [EMAIL PROTECTED] writes: [snip] /etc/hosts: 127.0.0.1 localhost loopback widget-servis.ecn.purdue.edu widget-servis #(plus a bunch of other frequenctly used hosts at ecn.purdue.edu) [snip] /etc/init.d/network: ifconfig lo 127.0.0.1 route add -net 127.0.0.0 dev lo I have found that having anything other that localhost after 127.0.0.1 caused me problems in the past. I use the dummy driver to create a fake network: --- /etc/hosts --- 127.0.0.1 localhost 192.168.117.2 psyche.evansnet psyche www.evansnet news.evansnet [ 192.168.*.* are available for provate use; see RFC 1918. ] --- /etc/hostname --- psyche --- /etc/init.d/network #! /bin/sh ifconfig lo localhost route add -net 127.0.0.0 ifconfig dummy0 psyche route add -net 192.168.117.0 [ dummy if it's in the kernel, dummy0 if it's a module. ] There still seem to be things that expect _one_, _permanently_ connected interface and hostname. :-( Ok, I think we are getting closer to figuring this out. I tried your suggestions(changed my machine name to servis.snet) and rebooted. /etc/hosts 127.0.0.1 localhost 192.168.1.1 servis.snet www.servis.snet ftp.servis.snet servis /etc/resolv.conf domain snet search snet ecn.purdue.edu nameserver 128.46.131.20 nameserver 128.46.131.20 nameserver 128.46.131.20 /etc/hostname servis /etc/init.d/network #ifconfig lo localhost ifconfig lo 127.0.0.1 route add -net 127.0.0.0 # create the dummy network ifconfig dummy 192.168.1.1 route add -net 192.168.1.0 However, when /etc/init.d/boot called /etc/init.d/network ifconfig complained about host name lookup failure of localhost! This is run before rc2.d parts are run. This is really starting to make me mad. I have read almost all the network related howto's, man pages on all the conf files, etc.(each giving slightly different methods of setup by the way) Even if I use the IP address in /etc/init.d/network it still doesn't fix the problem. WAIT A MINUTE..I just discovered something as I was checking the log files. ifconfig is making kerneld try to load some net-pf-4 and net-pf-5 module? What is this? I can't find any reference to it in the kernel-source. %root% date ; ifconfig lo 127.0.0.1 Wed Jun 4 12:49:12 CDT 1997 [snippet of /var/log/daemon] Jun 4 12:49:12 servis modprobe: can't locate module net-pf-4 Jun 4 12:49:12 servis modprobe: can't locate module net-pf-5 This must be the root of the problem! Any pointers. Sorry for the length of this but I am trying to give as much info as possible up front. Thanks, Brian -- Mechanical Engineering [EMAIL PROTECTED] Purdue University http://widget.ecn.purdue.edu/~servis -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
