Topic: Hostnames panel - Error: IP cannot be server IP or Gateway IP.

[DanB35]

My SME Server sits behind a pfSense router, which I'm trying to configure to send email notifications.  I want the notifications to come from admin@pfsense.mydomain, but when I configure pfSense that way, my SME server refuses the emails because it can't resolve the hostname.  If I configure pfsense to send the emails from admin@mydomain, they work, but then the from address doesn't reflect the system they're actually coming from.

The pfSense box acts as the DNS server for my network, but of course SME wants to do its own thing for DNS, and it won't resolve pfsense.mydomain.  So I figure, no problem, that's what the Hostnames and Addresses panel is for, right?

Maybe not.  I go to that panel and try to enter a hostname for pfsense.mydomain, and it gives the error message above.  Why?  Why should SME refuse to (internally) assign a hostname to the IP address of its default gateway?

Note:  Yes, I'm sure I could make this work if I told SME to use the pfSense box as a DNS server.  I may yet do that.  But this seems like a completely arbitrary restriction.  I can kind of understand locking out the SME Server's own OP (though a smart panel would recognize that and just set the hostname to "Self" rather than "Local" in that case), but I don't understand at all why there's such a restriction in place for the gateway IP.

[Stefano]

AFAIR there's a bug for it
I'd like to give an hostname to my router/GW too

[DanB35]

Ah, yes, right you are.  It's been open for 12 years.  https://bugs.koozali.org/show_bug.cgi?id=369

[ReetP]

Anyone tested the suggested patches on the bug?

[martijn]

This is an old post, but this is what works for me.

Edit the database directly (it may help if you first create some LOCAL dns entries (reservations) with MAC and IP from the /server-manager as an example):
nano -w /home/e-smith/db/hosts

Tell the system what you just did (or reboot+reconfigure):
signal-event host-create

[mmccarn]

I set discrete alert sender emails using the built-in hyphen aliases on a sme server.

In this case I would set the pfsense email "from" address to "admin-pfsense@mydomain.com"