Using Dynamic DNS service to host local host names
-
I purchased a domain name from Dyndns and although I know that I can create A and CNAME on the Dyndns portal, I was wondering if I could just create my my domain name and a A record (for instance, my domain foo.com, and I create an A record called home) and on the pfsense box, I create host names (for instance, www or mail) so that when someone connects to www.home.foo.com it finds me host on my local LAN.
Now assume that I have a host named mail.local.lan. Can I create a CNAME email.home.foo.com just on the pfsense box or would I also have to create a CNAME on the dyndns portal as well? Or can only create an CNAME only on the dyndns portal and then do some magic on the pfsense box to point to my mail server?
-
@kcallis said in Using Dynamic DNS service to host local host names:
Now assume that I have a host named mail.local.lan. Can I create a CNAME email.home.foo.com just on the pfsense box or would I also have to create a CNAME on the dyndns portal as well? Or can only create an CNAME only on the dyndns portal and then do some magic on the pfsense box to point to my mail server?
Do you need to access "email.home.foo.com" only from your LAN(s) : if so, make a host override on the DNS (Resolver)page and that's it.
If you want to use "email.home.foo.com" visible from on Internet, being your MS, that have it point to your WAN IP, have it "DNS updated" and add a NAT rule etc. -
@Gertjan Thanks for the rapid response. I am looking to the latter, which is make mail.home.foo.com visible from the Internet. So with that said, can you expand on that I need to do to make this work.
-
@kcallis said in Using Dynamic DNS service to host local host names:
expand ...
You should consult documentation @Dyndns - because it's over there that you to create a A or CNAME.
-
I already have an A record in place on Dyndns. There are a couple of thing I am not clear on. I am assuming that I need to do a incoming NAT for both port 443 and 80. I also assume that I create a rule for the appropriate VLAN that the host resides in. So no need to make use of split DNS or messing around with BIND on the pfsense side of things. But with going with NAT, what happens if I need to make use of 443 to the (for instance) mail host and 443 for my web server which is another host?
-
@kcallis said in Using Dynamic DNS service to host local host names:
NAT for both port 443 and 80
On NAT rule for NATting incoming connection on WAN - port 80 (VLAN, whatever - at this point VLAN is just a LAN) device - web server.
And another NAT rule for port 443
Both TCP-only, probably.@kcallis said in Using Dynamic DNS service to host local host names:
if I need to make use of 443 to the (for instance) mail host and 443 for my web server which is another host?
Ah, welcome the the club !
A NAT rule includes a port - and taht port will get Network Address translated to another device, some where on LAN.
But, guess what, NAT is PAT most of the time, so, PAT port 444 on WAN to port 443 on LAN (your web mail server).
Inform users that they should use http://your-dyndns.tld:444 and they see the login screen of the web mail web server.
