[Solved] dhcpleases: Other suffix in DHCP lease for [fqdn]
-
Solution: do not use .local tld, changed to .lan.
My system is run over by messages:
Jan 30 20:54:38 dhcpleases: Other suffix in DHCP lease for some.host.local Jan 30 20:54:38 dhcpleases: Other suffix in DHCP lease for some.host.local Jan 30 20:51:21 dhcpleases: Other suffix in DHCP lease for some.host.local Jan 30 20:51:21 dhcpleases: Other suffix in DHCP lease for some.host.local Jan 30 20:50:21 dhcpleases: Other suffix in DHCP lease for some.host.local Jan 30 20:45:18 dhcpleases: Other suffix in DHCP lease for some.host.local Jan 30 20:43:56 dhcpleases: Other suffix in DHCP lease for some.host.local Jan 30 20:43:56 dhcpleases: Other suffix in DHCP lease for some.host.localI've searched the web and forums but can't find anything about this. Why is it appearing and how can I stop these messages? I tried changing my clients' hostname and using another DHCP client (switched from dhclient to the default systemd dhcpcd; using Arch Linux) but it doesn't seem to make a difference.
Any ideas please?
Thanks.
-
are you using .local as your domain/tld? That is never a good idea - apple ruined that for everyone ;)
What is your domain in pfsense, what have you setup on dhcpd in pfsense for domain? What is on your machines for their domain?
-
My domain is athome.local. So the FQDN for a laptop would be laptop1.athome.local. The pfsense box has hostname pfsense with that same domain, athome.local, so its full name as you can guess would be pfsense.athome.local. This is configured under System/General Setup.
The domain name in the DHCP server on PfSense is empty because the description says
The default is to use the domain name of this system as the default domain name provided by DHCP. You may specify an alternate domain name here.
The machine in question (workstation.athome.local) currently has no domain suffix configured. In /etc/hostname there's only the short name, workstation. In /etc/hosts there are only entries for localhost.
/etc/resolv.conf is generated through resolvconf using info from the dhcp client. It currently contains:
user1@workstation / $ cat /etc/resolv.conf # Generated by resolvconf search athome.local nameserver 192.168.1.1 user1@workstation / $user1@workstation / $ hostname workstation.athome.local user1@workstation / $ $ hostname -s workstation user1@workstation / $ $ hostnamectl Static hostname: workstation Transient hostname: workstation.athome.local Icon name: computer-desktop Chassis: desktop Machine ID: 5e33d2ec34ca48afadbc4f4db55f3079 Boot ID: 93a946ce43da4c8e8d7140f6d20ff51c Operating System: Arch Linux Kernel: Linux 4.3.3-3-ARCH Architecture: x86-64 user1@workstation / $ $I can easily change the .local if that is a problem, I would only ask why that would be a problem? Or is it only a problem if you're only using .local and not athome.local?
Point is, my laptop runs the same archlinux version, configured pretty much the same way and does not show up on my system logs on pfsense. The workstation is the only one that shows up like that.
-
"My domain is athome.local."
Not a good idea… I wold suggest you change that to a better tld.. if you have any apple products on your network. Or anything that uses mdns
https://en.wikipedia.org/wiki/.local
If your still having a issue once you use something like athome.lan or if you own a public domain use a subdomain of that say athome.yourpublicdomain.tld
-
Never knew that about .local. Learned something cool today! 8). Figured it was like any other internal tld.
Anyway, it's all the same to me so I changed everything to .lan. Rebooted everything and those annoying messages are a goner.
Awesome stuff. Thanks for the help!
-
Yeah I use local.lan myself, glad you got all sorted!
I don't see anyone grabbing up .lan anytime soon - but you never know now that pretty much anyone with some cash can setup their own .tld ;)
