Hi everyone,
in former versions like MGA6, MGA7 it was possible to get the machine registered in the local DNS, e.g. the DNS of the internet router like AVM Fritzbox.
Every other device like HP or Brother printers, Debian based machines like Raspbian PC or Ubuntu workstations ist still found, i.e.
forward and reverse NSlookup works.
But not so my MGA9 machines, both 32 and 64 bit.
First I installed DNS "out of the box" with dhclient selected in the
network center, then I switched to dhcpcd. Each connected via LAN cable,
with no effect.
For instance, at this time on MGA9x64 there's the following command set automatically and active:
dhclient -1 -q -lf /var/lib/dhclient/dhclient--enp4s0.lease -pf /var/run/ dhclient-enp4s0.pid enp4s0
The MGA9 machines are only registered by IP in the form a-b-c-d, hence,
I cannot address those machines by their name:
https://www.dipl-ing-kessler.de/tmp/fritzbox.jpg
Any idea what to try next?
On Tue, 05 Mar 2024 17:03:50 -0500, Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
Hi everyone,
in former versions like MGA6, MGA7 it was possible to get the machine
registered in the local DNS, e.g. the DNS of the internet router like
AVM Fritzbox.
Every other device like HP or Brother printers, Debian based machines
like Raspbian PC or Ubuntu workstations ist still found, i.e.
forward and reverse NSlookup works.
But not so my MGA9 machines, both 32 and 64 bit.
First I installed DNS "out of the box" with dhclient selected in the
network center, then I switched to dhcpcd. Each connected via LAN
cable, with no effect.
For instance, at this time on MGA9x64 there's the following command set
automatically and active:
dhclient -1 -q -lf /var/lib/dhclient/dhclient--enp4s0.lease -pf
/var/run/ dhclient-enp4s0.pid enp4s0
The MGA9 machines are only registered by IP in the form a-b-c-d, hence,
I cannot address those machines by their name:
https://www.dipl-ing-kessler.de/tmp/fritzbox.jpg
Any idea what to try next?
Different programs and scripts look in different places for the
hostname.
[root@x3 ~]# cat /etc/hostname x3.hodgins.homeip.net [root@x3 ~]# cat /etc/sysconfig/network HOSTNAME=x3.hodgins.homeip.net NETWORKING=yes GATEWAY=192.168.10.11 NOZEROCONF=yes CRDA_DOMAIN=CA
Rather then looking into which one is used by which, I just make sure I
have them both set to the same name.
On Tue, 05 Mar 2024 18:27:57 -0500 David W. Hodgins wrote:
On Tue, 05 Mar 2024 17:03:50 -0500, Markus Robert Kessler
<no_reply@dipl-ing-kessler.de> wrote:
Hi everyone,
in former versions like MGA6, MGA7 it was possible to get the machine
registered in the local DNS, e.g. the DNS of the internet router like
AVM Fritzbox.
Every other device like HP or Brother printers, Debian based machines
like Raspbian PC or Ubuntu workstations ist still found, i.e.
forward and reverse NSlookup works.
But not so my MGA9 machines, both 32 and 64 bit.
First I installed DNS "out of the box" with dhclient selected in the
network center, then I switched to dhcpcd. Each connected via LAN
cable, with no effect.
For instance, at this time on MGA9x64 there's the following command
set automatically and active:
dhclient -1 -q -lf /var/lib/dhclient/dhclient--enp4s0.lease -pf
/var/run/ dhclient-enp4s0.pid enp4s0
The MGA9 machines are only registered by IP in the form a-b-c-d,
hence,
I cannot address those machines by their name:
https://www.dipl-ing-kessler.de/tmp/fritzbox.jpg
Any idea what to try next?
Different programs and scripts look in different places for the
hostname.
[root@x3 ~]# cat /etc/hostname x3.hodgins.homeip.net [root@x3 ~]# cat
/etc/sysconfig/network HOSTNAME=x3.hodgins.homeip.net NETWORKING=yes
GATEWAY=192.168.10.11 NOZEROCONF=yes CRDA_DOMAIN=CA
Rather then looking into which one is used by which, I just make sure I
have them both set to the same name.
Hi,
same here:
$ cat /etc/hostname mga9bc-lb1 $ cat /etc/sysconfig/network HOSTNAME=mga9-bc-lb1 NETWORKING=yes CRDA_DOMAIN=DE
So, I made a wireshark trace from the network segment where all these machines are connected to, and saw, that MGA9 did not even send a
hostname standard query record to the DNS. Of course, this would never
work.
Finally I found out, that the hostname has to be added as
'DHCP_HOSTNAME='
in /etc/sysconfig/network-scripts/ifcfg-... additionally. Or, set the hostname in mcc, netcenter, 'dhcp hostname', too.
This was not necessary in MGA <= 7.
There has been something messed up in draknetcenter module.
And, at least, hostnamectl command has to assist here, if this setting
is really necessary. That's not the case in any other OS I use / know
of.
After making and comparing the network traces, I have also compared what steps are necessary to change the hostname, locally and registered name in DNS.
MGA demands for changing the name in
/etc/hostname
/etc/sysconfig/network
as well as in the ifup-file for every interface like LAN, WIFI etc.
This is a high contrast to Raspbian, where it is sufficient to only
change /etc/hostname and reboot. But, maybe there's a way to have a kind
of script to automatically change the hostname at every location needed,
and which is integrated in MCC? -- That would be a big step forward!
Unfortunately, I do not have any contact info, or package name to place a
bug report / suggestion against.
Can you perhaps please help here
(since you have the most experience and knowing MGA best)?
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 49:30:46 |
Calls: | 6,711 |
Calls today: | 4 |
Files: | 12,243 |
Messages: | 5,354,781 |
Posted today: | 1 |