I'm trying your solution Remington. Fyi, I am also prevented from using the domainname to ssh when on local wifi (when on a remote ip I can use the domainname I setup with
noip.com to ssh). Rather to ssh I must do
ssh username@192.168.1.7
.
When I add
192.168.1.7 domainname.ddns.net
to
/etc/hosts on my personal computer (not on the server), then I can at least ssh with
ssh username@domainname.ddns.net
locally. But then I am restricted from sshing into the server when on a remote ip; so that doesn't work. Also, adding that line to
/etc/hosts (on my personal macbook or on the BSD server) does not seem to help with the Apache problem I mentioned in my previous post. Additionally, when typing
domainname.com
into my browser, it sends me directly to my router — which is identical behaviour to if I type
192.168.1.1
into the browser. So it seems that when on local wifi,
[URL='http://domainname.com/']domainname.com[/URL]
is the router not the server.
I might need to attempt the dreaded split DNS solution suggested by kpa...
My
/etc/rc.conf looks like the following:
Code:
hostname="domainname"
ifconfig_ue0="inet 192.168.1.7 netmask 255.255.255.0"
defaultrouter="192.168.1.1"
keymap="swissgerman.macbook.acc.kbd"
sshd_enable="YES"
moused_enable="YES"
ntpd_enable="YES"
ntpd_sync_on_start="YES"
pf_enable="YES"
pflog_enable="YES"
syslogd_enable="YES"
powerd_enable="YES"
dumpdev="AUTO"
zfs_enable="YES"
noip_enable="YES"
sshguard_enable="YES"
sshguard_safety_thresh="30"
sshguard_pardon_min_interval="600"
sshguard_prescribe_interval="7200"
apache24_enable="yes"