Re: FQDN via DHCP, then used in exim4
Stan, Thank you for the teaching. Indeed, there are many books I should
have read already, alas, there are a great many subjects about which
important books are written. So, I go along and learn when things don't
work as expected. Like now.
The story about using DHCP to assign fixed addresses doesn't seem to be
as clear cut as might appear from your tone, either:
http://serverfault.com/questions/199104/dhcp-addressing-vs-static-addressing-for-servers
I do take your point about the developer's perspective, and if that's the
way things work, then I have no problem editing config files on
the server for IP, host name and domain name. Indeed, as I described
earlier, that's exactly what I'd done already.
It's just curious that some services seem to acknowledge the DHCP
assigned domain name, while others don't. And _that_ question is still
open.
Klaus
On 16/05/13 15:01, Stan Hoeppner wrote:
On 5/16/2013 3:02 AM, Klaus Doering wrote:
...
Sorry long post. Can anybody shine light on this, and maybe even know
how to make use of the DHCP provided
domain name in exim?
First, using a DHCP server, in a consumer broadband router or otherwise,
to assign -sticky static- addresses and hostnames is counterproductive
and counter intuitive. You're doing this because you've never been
taught not to. I'm teaching you now: Don't do this. Now you will ask
me why, and I will direct you to Google as I don't have time to write
you the many books you should already have read on the subject.
DHCP is for assigning resources to -client- computers, not -server-
computers. You will not find a server application (mail) developer who
codes for your DHCP situation. They all code assuming addresses and
hostnames are assigned within local UNIX files, or assuming you will
manually configure such things.
To answer your EXIM question, read this thread:
http://serverfault.com/questions/46545/how-do-i-change-exim4s-primary-hostname-on-a-debian-box
Reply to: