On 12/14/2019 7:49 PM, Jape Person wrote: > On 12/14/19 1:24 AM, john doe wrote: >> >> Assuming that you are using the router from your ISP, it is possible >> that the firmware has been upgraded without your nolage. >> >> One way to prevent this could be (1), that is, use your own >> router/server/gateway so you control everything on your LAN. >> >> I use an EMTA modem only from my ISP which is plugged into a perimiter >> firewall. >> >> If you can't have an modem from your ISP, look at 'bridgemode'. >> >> If your not comfortable building your server from scratch, you can >> simply buy a router that is accepted by your ISP . >> >> In other words, you need to choose one or the other if you go this way: >> - Modem connected to router (most flexible of all) >> - Combo modem/router in one box (les flexible but is more compact) >> >> >> If you use DHCP static lease, you should look at what the DHCP server is >> providing as hostname and 'TLD', and also in the dhcp client (dhclient' >> to see what you get from the DHCP server. >> >> The file '/etc/resolv.conf' should let you know what TLD is sent from >> the DHCP server. >> >> Debian shouldn't modify your configuration files '/etc' without your >> nolage. >> >> Note that the TLD '.lan' is sometime used. >> >> 1) >> https://www.xfinity.com/support/articles/list-of-approved-cable-modems >> >> -- >> John Doe >> > > Hi, John Doe. > > I'm using my own router behind the modem provided by the ISP. I've never > used a router provided by an ISP for controlling my network. > > I'm using a Luxul XWR-1750 which has been kept on the latest firmware > available. Last upgrade was done early this year, long before the noted > change in names. > > The router is set to provide static IP addresses and has the names of > each of the systems associated with their MAC Addresses and IP Addresses. >
You can set a hostname per IP/MAC, but that is not the domain name: try.example.com In the above example 'try' is the hostname while 'example.com' is the domainname. From other e-mail, it looks like your DHCP server was sending as 'local' as domainname. Look at the lease of your DHCP client (/var/lib/dhcp/*). As other as pointed out, why are you using the 'host' file if your are using DHCP? What domain name is your DHCP server dishing out to your clients? In anycase, using '.home.arpa' as domainname is the way to go for a private LAN. -- John Doe
