Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Help about MediaWiki
FUTO
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Introduction to a Self Managed Life: a 13 hour & 28 minute presentation by FUTO software
(section)
Main Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== Setting Up FreeDNS == <span id="step-1-register-on-freedns"></span> === Step 1: Register on FreeDNS === We’re going to use a service called '''FreeDNS'''. It’s free, easy to use, and even has some fun domain options. <gallery mode="packed-hover" heights=250 widths=400 perrow=2> File:lu55028jxaty_tmp_4729b2e6.png File:lu55028jxaty_tmp_45e15cd2.png File:lu55028jxaty_tmp_7c63c31c.png File:lu55028jxaty_tmp_9cd59f27.png File:lu55028jxaty_tmp_684ec372.png </gallery> <span id="create-a-freedns-account"></span> ==== 1.1 Create a FreeDNS account ==== # '''Visit FreeDNS:''' Go to [http://freedns.afraid.org/ freedns.afraid.org]. # '''Register:''' Click on “Sign up Free” in the lower center of the page. # '''Fill out form:''' Fill in the required fields (username, password, and email) and click “Create Account”. # '''Verify your account''' by clicking the link in the confirmation email. <span id="log-into-freedns-create-subdomain"></span> ==== 1.2 Log into FreeDNS & create subdomain ==== Continue with the steps to set up your subdomain as needed. This is going to be the “website name” we associate with our home server internet connection. When you visit <code>rossmanngroup.com</code>, this actually means <code>208.113.140.53</code>. When you type ''[http://rossmanngroup.com/ http://rossmanngroup.com]'' in your browser, you’re asking your browser to go to <code>208.113.140.53</code> and knock on port 80 to serve us a website. When you type <code>https://rossmanngroup.com</code> in your browser, you’re saying we’re going to <code>208.113.140.53</code> and knocking on port 443 to be served a website with https/ssl. The '''subdomain''' enclosed in red in the screenshot above is the '''first part''' of the website name, and the '''domain''' enclosed in green is the '''second part''' of the website name. The '''destination''' enclosed in blue is where our combined website name leads us. So, <code>louishomeserver.chickenkiller.com</code> in the configuration above, would lead us to <code>8.8.8.8</code> # After clicking the activation link from the FreeDNS email, you should be immediately logged in. You should save the username & password they gave you in a password manager. # '''Add a New Subdomain:''' Once logged in, click on “Add a subdomain” in the middle of the screen from the main menu. Or, click Subdomains on the left side menu. # Fill out the fields: ## '''Subdomain:''' Choose a custom name (e.g., “louishomeserver”). That’s the part I circled in red in my screenshot above. ## '''Domain:''' Select one of the available free domains (e.g., <code>chickenkiller.com</code>). This is the green field in my screenshot above. '''You can get your own pretty, custom named .com address, but you’ll have to pay for it.''' ## '''Destination:''' Here’s the trick - put in a WRONG IP address on purpose (e.g., <code>8.8.8.8</code>). This will help us confirm if our setup is working later. # The entire point of this is for our router to constantly ''update'' FreeDNS by telling it what our IP address is. If we put what our IP address is ''RIGHT NOW'' in this field, we won’t know for sure if '''pfSense''' is working properly with FreeDNS. We’d have to debug it through log files. Ew. # Click “Save” to create your hostname. <blockquote>'''NOTE:''' Setting an incorrect initial IP address lets us test that pfSense is correctly updating the dynamic DNS entry. This diagnostic step is an important one; screw things up & make sure that the system you put into place to auto-fix-it fixes it. This is far less dangerous than the alternative, which is “assuming that it works.” </blockquote> <span id="get-the-update-url-from-freedns"></span> ==== 1.3 Get the update URL from FreeDNS ==== The update URL is the URL '''pfSense''' will access to tell FreeDNS that your domain name’s IP address has changed & should change to the IP that your router is accessing that FreeDNS URL from. # After saving, click “Dynamic DNS” from the upper left menu of choices. # You’ll see your new subdomain at the bottom. # Right-click on the “Direct URL” link next to your hostname and copy the link address. # This URL is how we will update our IP address automatically. '''DO NOT SHARE THIS WITH ANYONE OR THEY WILL BE ABLE TO MESS WITH YOU ENDLESSLY BY CHANGING THE IP THAT YOUR NEW WEBSITE NAME ATTACHES TO AWAY FROM YOUR SERVER!!''' <blockquote>'''NOTE:''' The Direct URL contains what is like a “password” necessary for updating your dynamic DNS record. Keep this URL secure and don’t share it publicly unless you want your dynamic dns domain name redirecting to goatse </blockquote> <span id="leave-freedns-page-open-make-sure-it-has-the-wrong-ip-for-you."></span> ==== 1.4 Leave FreeDNS page open & make sure it has the WRONG IP for you. ==== # Either the ''[https://freedns.afraid.org/dynamic/ dynamic DNS page on FreeDNS]'' OR the ''[https://freedns.afraid.org/subdomain/ subdomains page on FreeDNS]''. Make sure the IP address is as we entered before, which is <code>8.8.8.8</code>. # '''IT IS IMPORTANT THAT THIS IP ADDRESS NOT BE YOUR IP ADDRESS! WE WANT IT TO BE WRONG!''' # Make sure it is still set to the <code>8.8.8.8</code> I told you to set it to before. # If it is not, set it to <code>8.8.8.8</code>. # Reload both pages. Still <code>8.8.8.8</code>? Good. # We want this to be wrong – it changing from “wrong” to “not wrong” when we finish our work will mean that our setup works. '''Why are we doing things this way?''' It takes an insignificant amount of extra time to do things like this, as a check against everything; from software glitches to my own carelessness and absent-mindedness. Starting with the assumption that nothing works properly allows us to figure out at the very beginning if everything has been configured properly. Starting with the assumption that nothing works will allow us to figure out if our system ACTUALLY works BEFORE WE NEED IT TO WORK!! You’ll see when we are testing certain features and functionalities and software like syncthing later that this comes in very handy. In the video, a connection will work & have a green checkbox the first time, but local discovery will not work the second time, even though the server & client IPs remain unchanged. NEVER ASSUME A FIX WORKS WITHOUT BREAKING THE THING IT IS SUPPOSED TO FIX AND SEEING WHAT IT DOES. Assume that nothing works, especially your own brain, and you will create systems that guard against much more than your own human error! <span id="step-2-configuring-pfsense-for-dynamic-dns"></span>
Summary:
Please note that all contributions to FUTO may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
FUTO:Copyrights
for details).
Do not submit copyrighted work without permission!
To protect the wiki against automated edit spam, we kindly ask you to solve the following hCaptcha:
Cancel
Editing help
(opens in new window)