From owner-freebsd-questions@freebsd.org Thu Mar 22 17:13:28 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4ACE9F57F81 for ; Thu, 22 Mar 2018 17:13:28 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9C64B800C6 for ; Thu, 22 Mar 2018 17:13:27 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.125.64]) by mrelayeu.kundenserver.de (mreue102 [212.227.15.183]) with ESMTPA (Nemesis) id 0LopTv-1eMirq0Z4N-00gn9T; Thu, 22 Mar 2018 18:08:01 +0100 Date: Thu, 22 Mar 2018 18:08:00 +0100 From: Polytropon To: Anton Shterenlikht Cc: freebsd-questions@freebsd.org Subject: Re: how to set hostname on a cable line? Message-Id: <20180322180800.58d61e9c.freebsd@edvax.de> In-Reply-To: <20180322121320.GA66012@jail0199.vps.exonetric.net> References: <201803211834.w2LIY9Jh059885@jail0199.vps.exonetric.net> <79cc198c-daa9-1cb2-020f-d11d7d3d396a@yandex.com> <20180321213005.GA73927@jail0199.vps.exonetric.net> <20180321232254.3a2dc696.freebsd@edvax.de> <20180322121320.GA66012@jail0199.vps.exonetric.net> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:kHq+KtqQ0/hK5ETfnzMND+rKXSz0JWO5NHZR+Tl+JlE0HGbd/Ev NXc8tKJQXkqFA/UMi7s2qaoTzw6uwsIR8LBUHTf1CQceQYVdZE+jEg+LK0t2ilNLaDMUWiL FoQnS05Xn3Hx+qx7nLYFWLbO6k5UoGdQcqzFBS7C/vE30gp1qrvXUMbC4c2Bic64VftT0kt miEap3z40dvE5gQiIRMng== X-UI-Out-Filterresults: notjunk:1;V01:K0:AxZXtM3pb34=:1uSdtYHW8zo8RSuNhc84R1 Bn5gsPLhH2SFCc6b7uH1/YLGOBo/TV8eNNWNbOrilGqMkC0o2YpDs01JTG0/uOiYRIRctEieL Oj08miZJ6CWrCLmPSnY41HGuFWFc0s6iZpAFREQmiUy2hS+4dtqejf/q8H5nP3Xwdp523sS+z a5gc2qwgu8meg/1cnBNAc8R/GFEKDVnIh+8HHsn2Bw1qhMn20kF5TWFMG8mppXL48is9WMCQZ Qcb7lRXp1PrpQ86pVqQc7DIvwmBd99QUeh6LSxneqs4QElUDLOlpxZs3RhJOQVAnCMY6ThabG U57vXEUNcuE2rnnOkjvPOSvzw9hL96dSqJ1SmW4OExWsLbyaCQYamodxFuID2mDCjSBohXk3B vaFH3VHc4POSokP3YHg6ugSNWbSWEow+YArry+NctWu31slkSw/CaRO9u2cvcgZ7/wolV9L3b duOM/cNE8BdjHwoBZOibCSU183W4k0y5KPWF9l810nQopf01Vk546xwQLnelDFcZkpOxrttAk BfTOFt6LGjx62ksTwY87HpPY6IH+cPC8MAP8FqSGGT+MpZNxH2Ij4AxojX29PdUFseCLlyXVf Ku+q465VrRFZKj8+xmzeE+hw7DatI7eXNZfUnlvXpW+WCfk1j0Ys7hU7KfwV51dwDCD5nSUHI kXbvNiDdFCJAaXxijmbpl2Cyc1HYi0HQ50dsHQLyE9LQxljLDt0acLvPgggqzoORBUUB6826Y Ji44gFUnpOwUMeeoBytpiW/8wi5NYjYlClqkMwaLP7AWwY05a0ExDSf/ugw= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2018 17:13:28 -0000 On Thu, 22 Mar 2018 12:13:20 +0000, Anton Shterenlikht wrote: > On Wed, Mar 21, 2018 at 11:22:54PM +0100, Polytropon wrote: > > > > > > > > Have you tried setting the hostname with 'bsdconfig networking' ? > > > > > > Maybe I didn't explain myself well. > > > > > > I need a fully qualified domain name (FQDM). > > > > > > Perhaps I just cannot have one from a wireless router > > > at home? > > > > Check the configuration of the device that hands out configuration > > data via DHCP to check if you can define the FQDN from within there. > > No, cannot find anything. > This is a basic router provided by Virgin media. > Everything is done by IP only. > > > If not, you can always manually set it using > > > > hostname="fqdn.example.com" > > > > in /etc/rc.conf (or using "bsdconfig networking" interactively). > > But what shall I choose? Whatever you want. For maximum consistency, don't hesitate to create the corresponding entries for your hostname in /etc/hosts, for example: 127.0.0.1 localhost 127.0.0.1 fqdn.example.com 123.45.678.90 fqdn.example.com Of course, a part of this can be donw with with DHCP. > No matter what I put there, > ssh `hostname` will not work, because > my randomly chosen hostname will not resolve to my IP! Okay, then you also have a DNS issue. ;-) > It seems I'm completely missing some piece here, > perhaps some DNS must be involved at some stage? Definitely, and probably the router won't let you configure those things at the level required. Maybe you can replace that unit with a more generic one, with more powerful tools for configuration? > But more likely, I just cannot have a FQDN > on a cable connection. Why not? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...