Dogma wrote: ↑
Thu Apr 25, 2019 11:56 pm
Oh last quick question where would I add additional synthetic logs. I.E if I wanted to add the www.dogmeat.net
or a forums.dogmeat.net?
as in will it check each login and pass on each domain or...?
Do you mean the Synthetic Records on Google Domains? I think that's what you are talking about.
I'm not sure here as I am not familiar with Google Domains. But, I think at this point in the Dynamic DNS area - you have configure the "@" record - which is what the DDClient is configured to update. My thinking would be that now in the regular DNS (not Dynamic DNS) configuration area you would want to add "cname" records that point to the "@" record - or to dogmeat.net. This would tell anyone resolving DNS names - like forums.dogmeat.net or www.dogmeat.net
or email.dogmeat.net and so on to point to your WAN IP address. Then you would have to have this RPi configured to respond to each of those cnames (aliases) - IF you are actually running all those things from that RPi. You could also configure other kinds of records, like MX records that would point to say email.dogmeat.net at a different IP address that is the mail server designated to handle your email for your domain. Or, you could add a cname record for shopping.dogmeat.net that would redirect the user to a shopping cart service that is handling a shopping cart for your domain.
Any cnames/MX records/etc... that you point to "@" or dogmeat.net are going to be directed your RPi and you will have to configure it/web server to handle what to do with requests coming in on those names - if you actually want to do something other than show your web page. Basically each subdomain you configure at Google - whether www, forums, email, etc... end up telling the requestor what IP address is assigned to each of those names. If its a web browser asking - it's gonna send a request on port 80 (or port 443 is https is used in the browser) to the address it received from Google DNS - asking for a web page matching www.dogmeat.net
, forums.dogmeat.net, email.dogmeat.net, etc... This process is mostly just creating an index of record type, name, and IP address to give to requestors asking for an address to one of those names. See?
It's more complex than this - this is overly simplified - but it is the jist of it. You forward port 80 on your router to point to your RPi's LAN address. You could point other ports to other machines. Like say you setup your own email server on another computer - you could forward the related ports to that computer and it would handle email server related traffic - (so long as Google DNS is configured with MX records pointing to "@" or dogmeat.net. It would work because the email systems are configure to use specific ports - so your router would know based on the port - which computer to forward that traffic to. You can configure you web server to direct them to a url like www.dogmeat.net/forums
when a browser request hits it looking for forums.dogmeat.net on port 80. There's a lot of flexibility here - and a lot to learn to use it all.