Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 22 Mar 2018 18:08:00 +0100
From:      Polytropon <freebsd@edvax.de>
To:        Anton Shterenlikht <as@cmplx.uk>
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>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
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, ...



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?20180322180800.58d61e9c.freebsd>