Closed francislavoie closed 1 year ago
I'm testing myself right now, trying to figure out one thing...
I'm pretty sure the panic is fixed, but checking something else
Okay yeah, the joining of domain and zone is kinda messed up. I need to fix that. Domain manipulation is annoyingly complicated.
Well, it doesn't seem to crash, and also got a finished message now:
May 10 23:59:23 server2 caddy[1452948]: {"level":"info","ts":1683755963.0720408,"logger":"dynamic_dns","msg":"domain not found in DNS","domain":"~~~"}
May 10 23:59:23 server2 caddy[1452948]: {"level":"info","ts":1683755963.0720797,"logger":"dynamic_dns","msg":"domain not found in DNS","domain":"~~~"}
May 10 23:59:24 server2 caddy[1452948]: {"level":"info","ts":1683755964.5031276,"logger":"dynamic_dns","msg":"updating DNS record","zone":"~~~","type":"A","name":"~~~","value":"~~~","ttl":0}
May 10 23:59:24 server2 caddy[1452948]: {"level":"info","ts":1683755964.503158,"logger":"dynamic_dns","msg":"updating DNS record","zone":"~~~","type":"AAAA","name":"~~~","value":"~~~","ttl":0}
May 10 23:59:27 server2 caddy[1452948]: {"level":"info","ts":1683755967.7643762,"logger":"dynamic_dns","msg":"finished updating DNS","current_ips":["~~~","~~~"]}
The "domain not found in DNS" is a problem though. Trying to figure that part out.
Okay this should be good to merge @mholt (I don't have permissions on this repo)
I think this should be it?
Fix #43