Google Domain URL with NAS

yamahahornist

Distinguished
Feb 1, 2012
317
0
18,810
Hey so I own a domain through google domains and in the past I had it forwarded to my public ip address on port 5000 where my NAS was. So when I put in my url nas.mydomain.com it would come up the the url would be my domain. Well recently whenever I put in that name the url shows my ip address; 1.1.1.1:5000 (not my real ip haha). The domain name isn't sticking anymore?? Anyone know why?
 
Solution
MERGED QUESTION
Question from yamahahornist : "How to configure D-Link Dynamic DNS with Google DNS"



First and foremost you must setup your Google Domain...


Has your external IP changed? Unless you've specifically paid to have a static one, this can happen at long intervals. Do you have your router updating the DNS?

You may wish to make use of a dedicated DynDns, such as No-IP (free). That will make sure your external IP is always accessible, and then it's just a matter of putting in the port number which can't be that hard to remember.
 

yamahahornist

Distinguished
Feb 1, 2012
317
0
18,810


I can't for the life of my figure out how to set it up with my router though! It's asking for my server address for the ddns? But I don't even know what that is for google?? I set up the dynamic dns through my google domain dna page and have the username and password??


Here is a pic of what I am working with... I am rdp right now because I am at work haha
https://www.dropbox.com/s/qqws4axtgedy9da/Untitled.jpg?dl=0
 
MERGED QUESTION
Question from yamahahornist : "How to configure D-Link Dynamic DNS with Google DNS"



First and foremost you must setup your Google Domain for DDNS: https://support.google.com/domains/answer/6147083?hl=en

Secondly:
Server Address: www.ddnscompanyurl.com
Hostmane: yoursubdomain.ddnscompanyurl.com

D-link firmware may or may not support completely customized DDNS address that is not in its drop-down list, so you may just need a better router (or at least better firmware).

Third: Many ISPs block port 80 (HTTP), port 53 (DNS), and port 443 (HTTPS) for inbound connection on resedential grade internet plans. Thus trying to use a residential plan to host a webserver is not going to work (at least not wihtout requiring people to manually input custom port numbers).
 
Solution