add records for new server rtm-hazel #2
@ -1 +1,42 @@
|
||||
[{"name": "sootie", "type": "A", "value": "100.64.0.3"}, {"name": "sootie.resisttechmonopolies.online", "type": "A", "value": "100.64.0.3"}, {"name": "mango", "type": "A", "value": "100.64.0.5"}, {"name": "mango.resisttechmonopolies.online", "type": "A", "value": "100.64.0.5"}, {"name": "layltta", "type": "A", "value": "100.64.0.7"}, {"name": "laylotta.resisttechmonopolies.online", "type": "A", "value": "100.64.0.7"}]
|
||||
[
|
||||
{
|
||||
"name": "sootie",
|
||||
"type": "A",
|
||||
"value": "100.64.0.3"
|
||||
},
|
||||
{
|
||||
"name": "sootie.resisttechmonopolies.online",
|
||||
"type": "A",
|
||||
"value": "100.64.0.3"
|
||||
},
|
||||
{
|
||||
"name": "mango",
|
||||
"type": "A",
|
||||
"value": "100.64.0.5"
|
||||
},
|
||||
{
|
||||
"name": "mango.resisttechmonopolies.online",
|
||||
"type": "A",
|
||||
"value": "100.64.0.5"
|
||||
},
|
||||
{
|
||||
"name": "layltta",
|
||||
|
|
||||
"type": "A",
|
||||
"value": "100.64.0.7"
|
||||
},
|
||||
{
|
||||
"name": "laylotta.resisttechmonopolies.online",
|
||||
"type": "A",
|
||||
"value": "100.64.0.7"
|
||||
},
|
||||
{
|
||||
"name": "hazel",
|
||||
"type": "A",
|
||||
"value": "100.64.0.16"
|
||||
},
|
||||
{
|
||||
"name": "hazel.resisttechmonopolies.online",
|
||||
"type": "A",
|
||||
"value": "100.64.0.16"
|
||||
}
|
||||
]
|
||||
@ -15,7 +15,8 @@ class Host:
|
||||
sootie = Host("sootie", "100.64.0.3", ["sootie.resisttechmonopolies.online"])
|
||||
mango = Host("mango", "100.64.0.5", ["mango.resisttechmonopolies.online"])
|
||||
laylotta = Host("layltta", "100.64.0.7", ["laylotta.resisttechmonopolies.online"])
|
||||
hosts = [sootie, mango, laylotta]
|
||||
hazel = Host("rtm-hazel", "100.64.0.16", ["hazel.resisttechmonopolies.online"])
|
||||
hosts = [sootie, mango, laylotta, rtm-hazel]
|
||||
linnealovespie
commented
rtm-hazel or hazel? rtm-hazel or hazel?
ammaratef45
commented
is this the same code generated the headscale-records.json with it? the generated host name is hazel but the code says rtm-hazel huh is this the same code generated the headscale-records.json with it? the generated host name is hazel but the code says rtm-hazel huh
jmakdah2
commented
The name of my vm is rtm-hazel (you will see that if looking on headscale connected devices). Oops, I need to change the variable name to rtm-hazel too. but im not sure what you are referring to by generated code, i made these changes manually... is there somewhere i should be pulling this from headscale instead? The name of my vm is rtm-hazel (you will see that if looking on headscale connected devices). Oops, I need to change the variable name to rtm-hazel too.
but im not sure what you are referring to by generated code, i made these changes manually... is there somewhere i should be pulling this from headscale instead?
ammaratef45
commented
So, that is the host name your vm is advertising for itself, head-scale automatically created a record for that that points to the right ip, here we can use different names and they would map to the correct ip. since your dns is hazel.xxxxx then the record here should also be hazel.xxxx The goal is to have records that match what we have in cloudflare and eventually have deployments to this package automatically update cloudflare Speaking of the readme:
https://git.coopcloud.tech/RTM/sootie-dynamic-dns/src/branch/main#headscale-records The headscale-records.json is intended for be generated by running the headscale.py -- in the future this should be autogenerated on merge of a new commit and uploaded as a release artifact rather than a source tracked file(everytime I ask you to edit the same thing in multiple places ask me why; if the answer is not that we just didn't get the time to fix that then challenge me on it; having multiple places to change the same thing is a recipe for inconsistent records and impossibility of identifying the truth) @jmakdah2
> The name of my vm is rtm-hazel
So, that is the host name your vm is advertising for itself, head-scale automatically created a record for that that points to the right ip, here we can use different names and they would map to the correct ip. since your dns is hazel.xxxxx then the record here should also be hazel.xxxx
The goal is to have records that match what we have in cloudflare and eventually have deployments to this package automatically update cloudflare
note to slef: add a section in the readme to dictate that part
Speaking of the readme:
> but im not sure what you are referring to by generated code, i made these changes manually... is there somewhere i should be pulling this from headscale instead?
https://git.coopcloud.tech/RTM/sootie-dynamic-dns/src/branch/main#headscale-records
The headscale-records.json is intended for be generated by running the headscale.py -- in the future this should be autogenerated on merge of a new commit and uploaded as a release artifact rather than a source tracked file(everytime I ask you to edit the same thing in multiple places ask me why; if the answer is not that we just didn't get the time to fix that then challenge me on it; having multiple places to change the same thing is a recipe for inconsistent records and impossibility of identifying the truth)
another note to self to explain this further in the readme
|
||||
|
||||
if __name__ == '__main__':
|
||||
records = []
|
||||
|
||||
is this typo leftover from before? Should be laylotta
looks like it was there before, i will fix that