{"id":2335,"date":"2021-08-22T22:42:29","date_gmt":"2021-08-23T05:42:29","guid":{"rendered":"https:\/\/www.spiffynasty.com\/?p=2335"},"modified":"2021-10-01T13:45:49","modified_gmt":"2021-10-01T20:45:49","slug":"spiffynasty-com-the-state-of-the-ddns-address","status":"publish","type":"post","link":"https:\/\/spiffynasty.com\/blahblahblah\/spiffynasty-com-the-state-of-the-ddns-address\/","title":{"rendered":"spiffynasty.com | the state of the ddns address"},"content":{"rendered":"
NAS - DNS ISSUES<\/span>Tab name<\/span>ERROR<\/span>ASUSTOR USER RIGHTS<\/span><\/div>
\n
\n

\"image-20210822120349134\"<\/a><\/p>\n

\"image-20210822120028417\"<\/a><\/p>\n

\"image-20210822115708516\"<\/a><\/p>\n

\"image-20210822115118063\"<\/a><\/p>\n

\"image-20210822114659356\"<\/a><\/p>\n

\"\"<\/a><\/p>\n

\"\"<\/a><\/p>\n

\"\"<\/a><\/p>\n

\"\"<\/a><\/p>\n

<!--\n+++++\n\"\"\n\n\n\n \"\"\n\n\n\n\"\"\n\n\n\n\"\" \n--><\/p>\n<\/div>

Show more<\/span><\/a><\/div>
Show less<\/span><\/a><\/div><\/div>\n

 <\/p>\n

Port Forwarding<\/h2>\n

Spiffy-Nas-Ty-XXX<\/h3>\n

Reserved IP Address: <\/strong>XX.X.X.XXX <\/p>\n

Port Forwards<\/p>\n

Port Number XXXX ProtocolTCP\/UDP<\/p>\n

Spiffy-Nas-Ty-XXX<\/h3>\n

Reserved IP Address:XX.X.X.XXX<\/strong><\/p>\n

Port Forwards<\/p>\n

Port Number XXXX ProtocolTCP\/UDP<\/p>\n

Port Number XXXX ProtocolTCP\/UDP<\/p>\n

\n

Afraid – DDNS<\/h2>\n

Type: A – Point subdomain.domain.com to a hard coded IP Address. Most direct and straight forward option, also note any change you make in the FreeDNS program is reflected on the internet and made live immediately. The only way you will not see immediate results is if you have cached a query on your computer by looking it up PRIOR to configuring it in the FreeDNS program.<\/p>\n

Type: MX – Point subdomain.domain.com to a mail server. These type of records are special for just mail servers, they can co-exist with A records, and their only use is for routing mail to a different location. All mail implementations check for this record first before attempting to route an e-mail message. If a MX record does not exist for a host, an e-mail delivery would be attempted directly to the IP that the hostname resolves to.<\/p>\n

Type: AAAA – Point subdomain.domain.com to a IPv6 address. Useful for those who are using IPv6 on their personal networks or those who are using a IPv4 to IPv6 tunnel at home.<\/p>\n

Type: CNAME – Point subdomain.domain.com to another hostname. Good for those who are using other dynamic DNS services. You can create a CNAME record to another host and whatever subdomain.domain.com you choose here will go to whatever IP address the CNAMEd host has.<\/p>\n

Type: NS – Point subdomain.domain.com to another NAMESERVER. If you choose this option, then whatever subdomain.domain.com address you choose using FreeDNS will have to be configured and setup on the destination ADDRESS (nameserver) that you choose. This option basically means you are delegating a FreeDNS host to another DNS server all together, so when you choose this option you are telling every computer on the internet to ask the 'address' where subdomain.domain.com is located at. If the host you point an NS record to is not configured to answer for the subdomain.domain.com that you are using in FreeDNS then the subdomain.domain.com host will not resolve.<\/p>\n

Type: TXT – Lets you create TXT records, used for a number of different things, most commonly for DKIM records (for combatting spam) so other receiving mail servers can verify email was sent from you by verifying your publically published crypto-signature. Wrap your TXT "destination" in quotes (don't worry, the system will remind you if you forget).<\/p>\n

Type: SPF – A anti-spam record, good to have on any domain you're sending email with. See https:\/\/www.spfwizard.net\/<\/a> for more details.<\/p>\n

Type: LOC – A means for Expressing Location Information in the Domain Name System.<\/p>\n

RFC1876 has the complete explanation.<\/p>\n

To find your latitude\/longitude location, you may find Map-O-Rama of use.<\/p>\n

Type: RP – The Responsible Person RR.<\/p>\n

RP has the following format:<\/p>\n

RP <\/p>\n

Both RDATA fields are required in all RP RRs.<\/p>\n

The first field, , is a domain name that specifies the mailbox for the responsible person.<\/p>\n

The second field, , is a domain name for which TXT RR's exist. A subsequent query can be performed to retrieve the associated TXT resource records at .<\/p>\n

RFC1183 has the complete explanation.<\/p>\n

Type: SRV – A 'service' record, used by Session Initiation Protocol (SIP), and the Extensible Messaging and Presence Protocol (XMPP). Also used by Minecraft.<\/p>\n

Some examples:<\/p>\n

Type: SRV<\/p>\n

Subdomain: service.<\/em>protocol.subdomain<\/p>\n

Destination: 4 fields, separated by a space (Priority Weight Port Target)<\/p>\n

Some more random examples:<\/p>\n

Type: SRV<\/p>\n

Subdomain: minecraft.<\/em>tcp.mc<\/p>\n

Domain: yourdomain.com<\/p>\n

Destination: 0 0 25676 dns.yourdomain.com<\/p>\n

Type: SRV<\/p>\n

Subdomain: jabber.<\/em>tcp<\/p>\n

Domain: yourdomain.com<\/p>\n

Destination: 10 0 5269 jabber.yourdomain.com<\/p>\n

Type: SRV<\/p>\n

Subdomain: jabber.<\/em>tcp<\/p>\n

Domain: yourdomain.com<\/p>\n

Destination: 20 0 5269 xmpp-server1.l.google.com<\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

Subdomains<\/h4>\n

\"image-20210822114659356\"<\/p>\n

 <\/p>\n

 <\/p>\n

Web Forwards<\/h4>\n

 <\/p>\n

\"image-20210822115118063\"<\/p>\n

Dynamic DNS<\/h4>\n

 <\/p>\n

\"image-20210822115708516\"<\/p>\n

 <\/p>\n

\n

DNS BROKER<\/h2>\n

System Default<\/h4>\n

\"image-20210822120028417\"<\/p>\n

 <\/p>\n

Ethernet<\/h4>\n

 <\/p>\n

\"image-20210822120349134\"<\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

\n

 <\/p>\n

NAS SETTINGS<\/h2>\n

\"image-20210822113257146\"<\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

\"image-20210822113937783\"<\/p>\n

 <\/p>\n

 <\/p>\n

Note about enabling EZ-Connect port forward – <\/h3>\n