search

mydnshost / mydnshost-infra

mydnshost-infra
Other
1 stars 1 forks source link

Documentation #5

Open unplugged216 opened 2 years ago

unplugged216 commented 2 years ago

So, I stumbled upon this gem. I tried the demo and played around with dns zones and such. Decided id like to setup my own instance. Yeah, not so easy lol.

Using the instructions in the readme and attempting to apply them to Ubuntu 21.04 is not working. Seems a lot of configuration changes need to be made that aren't documented. Errors are packing the logs. I modified the configuration to what seems logical by replace hostnames.

If there was a starting point to a completely functional setup, I would be glad to help contribute to the codebase or even docs.

Can you help getting this going on Ubuntu 21.04?

ShaneMcC commented 2 years ago

Hi,

Yeah this is definitely somewhere that I'm lacking at the moment.

The README.md file was accurate at getting it up and running at one stage, but I'll admit I've not set it up from scratch in a while.

I'll have a quick pass over the (limited) docs this weekend on a fresh install and see how it goes, I've probably neglected them slightly as things have changed over time!

unplugged216 commented 2 years ago

No worries! I get it. I certainly appreciate it.

unplugged216 commented 2 years ago

Hi,

Yeah this is definitely somewhere that I'm lacking at the moment.

The README.md file was accurate at getting it up and running at one stage, but I'll admit I've not set it up from scratch in a while.

I'll have a quick pass over the (limited) docs this weekend on a fresh install and see how it goes, I've probably neglected them slightly as things have changed over time!

Any luck with this?

unplugged216 commented 2 years ago

@ShaneMcC ?

If not no major worries. Just eager to help out.

ShaneMcC commented 2 years ago

Hey, not had a chance yet, sorry.

What specific issues/errors are you actually seeing - might be quicker for me to respond to those.

ShaneMcC commented 2 years ago

Hi,

I've ran through and added more information/checked the process - this seems to have worked fine for me for a test install just now.

ShaneMcC commented 2 years ago

Hey @unplugged216 did the updated docs help? If not happy to help you try and get it working if you're having specific errors

unplugged216 commented 2 years ago

OMG! Apologies, I spaced it.

I am checking now.

unplugged216 commented 2 years ago

Hey @unplugged216 did the updated docs help? If not happy to help you try and get it working if you're having specific errors

Hey Shane,

I ran through the install and everything appeared to work well. However, I may be missing something with SSL cert. Ill be taking a look at this later. I didn't see anything in the readme about it but could be something simple. Its enough firefox and chrome wont allow the connection.

ShaneMcC commented 2 years ago

Hey,

Glad it seemed to work.

The SSL Certs are handled by Traefik so maybe check there or the logs for that container - see: https://doc.traefik.io/traefik/v1.7/configuration/acme/ for details.

The default configuration should handle this automatically with a http-based challenge (eg, there is no need to have a working instance of mydnshost to allow for a dns-based challenge) and shouldn't need any changes.

unplugged216 commented 2 years ago

Hey,

Glad it seemed to work.

The SSL Certs are handled by Traefik so maybe check there or the logs for that container - see: https://doc.traefik.io/traefik/v1.7/configuration/acme/ for details.

The default configuration should handle this automatically with a http-based challenge (eg, there is no need to have a working instance of mydnshost to allow for a dns-based challenge) and shouldn't need any changes.

Gotcha.

Yep. Seems to be Traefik. However, trying to stumble through the logs. Of course multiple domains, so one error but duplicated for each domain. Also, this one about the backend.

time="2021-12-31T22:58:46Z" level=error msg="Error when creating error page \"network\" for frontend \"frontend-Host-sub-domain-com-1\": the backend \"backend-static\" doesn't exist."

And for ssl

time="2021-12-31T22:59:03Z" level=error msg="Unable to obtain ACME certificate for domains \"sub.domain.com\" detected thanks to rule \"Host:sub.domain.com\" : cannot get ACME client get directory at 'https://acme-v02.api.letsencrypt.org/directory': Get \"https://acme-v02.api.letsencrypt.org/directory\": dial tcp: lookup acme-v02.api.letsencrypt.org on 127.0.0.53:53: read udp 127.0.0.1:55271->127.0.0.53:53: read: connection refused"

However, the second error has to do with this freaking dnsmasq Ubuntu insists on lol.

unplugged216 commented 2 years ago

Oh.

It looks like every single domain used, which are quite a few, needs to be public. Is that intentional?

unplugged216 commented 2 years ago

Alrighty @ShaneMcC ,

I was able to get it all worked out. However, the one hiccup that kept me stumbled for a while was bind. Slaves must be defined. So, I attempted to use none; since it seemed they were fields that could handle it. Bind disagreed lol. So, I just used the public IP of the master. I may be able to find a work around. Im still testing it.