On 08/20/18 08:26, Jonathan Ryshpan wrote:
Thanks for your help Three responses follow.
To recap, here is:
$ cat /etc/resolv.conf
# Generated by NetworkManager search tew-818dru nameserver 192.168.10.1
On Sat, 2018-08-18 at 21:03 +0800, Ed Greshko wrote:
> What is the output of hostnamectl on your system
$ hostnamectl
Static hostname: amito
Icon name: computer-desktop
Chassis: desktop
Machine ID: 118d9c2c0a1e4b51ab25e3ce8fd57219
Boot ID: 21b543bfb22049e0905befaac3a5851d
Operating System: Fedora 28 (Twenty Eight)
CPE OS Name: cpe:/o:fedoraproject:fedora:28
Kernel: Linux 4.17.14-202.fc28.x86_64
Architecture: x86-64
On Sat, 2018-08-18 at 17:51 +0800, Ed Greshko wrote:
> This is a typical DHCP response.... As you can see, it tells the client the IP
> address, subnet mask, broadcast address, DNS server, and Default router.
>
> Frame 8505: 345 bytes on wire (2760 bits), 345 bytes captured (2760 bits) on
> interface 0
I don't have such a detailed record of the DHCP setup, but here is an extract from
the system log:
That info was from a wireshark capture to show what is on the wire. FWIW, a DHCP
server can provide many more things to client. See RFC 2132if you're ever
interested.
https://tools.ietf.org/html/rfc2132
$ journalctl --boot | grep -i dhcp
Aug 19 09:26:47 amito NetworkManager[989]: <info> [1534696007.7446] dhcp-init:
Using DHCP client 'dhclient'
Aug 19 09:26:56 amito NetworkManager[989]: <info> [1534696016.7255] dhcp4
(enp3s0): activation: beginning transaction (timeout in 45 seconds)
Aug 19 09:26:56 amito NetworkManager[989]: <info> [1534696016.9214] dhcp4
(enp3s0): dhclient started with pid 1396
Aug 19 09:26:57 amito dhclient[1396]: DHCPREQUEST on enp3s0 to 255.255.255.255 port
67 (xid=0x26730e55)
Aug 19 09:26:57 amito dhclient[1396]: DHCPACK from 192.168.10.1 (xid=0x26730e55)
Aug 19 09:26:57 amito NetworkManager[989]: <info> [1534696017.5542] dhcp4
(enp3s0): address 192.168.10.101
Aug 19 09:26:57 amito NetworkManager[989]: <info> [1534696017.5543] dhcp4
(enp3s0): plen 24 (255.255.255.0)
Aug 19 09:26:57 amito NetworkManager[989]: <info> [1534696017.5543] dhcp4
(enp3s0): gateway 192.168.10.1
Aug 19 09:26:57 amito NetworkManager[989]: <info> [1534696017.5543] dhcp4
(enp3s0): lease time 86400
Aug 19 09:26:57 amito NetworkManager[989]: <info> [1534696017.5543] dhcp4
(enp3s0): nameserver '192.168.10.1'
Aug 19 09:26:57 amito NetworkManager[989]: <info> [1534696017.5543] dhcp4
(enp3s0): domain name 'tew-818dru'
Aug 19 09:26:57 amito NetworkManager[989]: <info> [1534696017.5543] dhcp4
(enp3s0): state changed unknown -> bou
It looks like the DHCP setup message from the Trend server does request the client
(amito) to use search domain tew-818dru
Well, your router is supplying a "domain name" but isn't a valid
"domain name" as it
doesn't end with a valid TLD (top level domain) such as .com, .edu, .tv, etc.
Additionally, you don't have a domain name configured for your host amito. You
should run....
hostnamectl set-hostname
amito.validsomething.com
or what ever makes sense in your situation. Don't get confused
thinking that the command domainname is used to do that. That is for setting a
NIS/YP domain name.
Just as a matter of completeness.
f28k-b1 is a hostname
f28k-b1.greshko.com is known as a FQDN or Fully Qualified Domainname
FWIW, you probably shouldn't be combining comments by 2 posters into one reply. Kind
a messy. I'm not going to
answer what to what he has said.
--
Conjecture is just a conclusion based on incomplete information. It isn't a fact.