[14:23:55]
<FbIN> Hi All. I have searched high & low, and finally someone suggested to come here. With YunoHost, I need to have DNS done within home/server itself, and not with registrar. How is it possible?
[14:24:40]
<FbIN> I cannot locate Bind9 options via apt as it states not found as well. But even with that, how can I manage DNS within server itself?
[14:29:41]
<selfhoster1312> > I cannot locate Bind9 options via apt as it states not found as well. But even with that, how can I manage DNS within server itself?
hello, what do you mean bind9 is not found ?
[14:30:09]
<selfhoster1312> there is a bind9 package and you can install/configure it manually (yunohost if just debian with more things :))
[14:30:25]
<FbIN> YNH (afaics) in debian12 does not have Bind9 integrated (unlike HestiaCP).
[14:32:07]
<FbIN> > there is a bind9 package and you can install/configure it manually (yunohost if just debian with more things :))
True, and I understand that. But my point is, how come YNH has DNS outside of the server/installed system? DNS with registrar (at least for me) is more than a troublesome stuff.
[14:43:55]
<selfhoster1312> you can use any DNS primary NS, not necessarily with your registrar
[14:44:08]
<selfhoster1312> so the NS can be your own server, your ISP's server, or anyone else's
[14:44:24]
<selfhoster1312> but i don't understand what you mean with bind9 not being integrated
[14:44:25]
<FbIN> NS is fine, but I have to set each entry at registrar level, right?
[14:44:28]
<selfhoster1312> it's a package and you can configure it :)
[14:44:50]
<selfhoster1312> hmmm at the registrar level you only register your name servers (2 minimum)
[14:44:57]
<FbIN> crrct
[14:45:02]
<selfhoster1312> so the registrar will delegate the names to your own NS
[14:45:05]
<FbIN> that I already have
[14:45:16]
<selfhoster1312> ok so one of them is yunohost and the other is?
[14:45:17]
<FbIN> okay, maybe I am not asking it correctly
[14:45:24]
<FbIN> let me rephrase
[14:46:05]
<FbIN> > ok so one of them is yunohost and the other is?
registrar has my NS, and I want to have DNS setup within my server itself, say my VPS, or my dedicated server, at whatever IP/domain level I have, for example
[14:46:34]
<selfhoster1312> i think the word you're looking for is you want to host your own NS instead of using your registrar's
[14:46:43]
<selfhoster1312> this is not integrated in yunohost but is completely supported
[14:46:45]
<FbIN> exactly. thank you
[14:46:53]
<FbIN> sorry for confusing earlier
[14:47:06]
<selfhoster1312> you just need two NS on two different IPs and configure bind (or powerdns, or whatever)
[14:47:07]
<FbIN> > this is not integrated in yunohost but is completely supported
Okay, but I am so confused with how rto get this done
[14:47:40]
<FbIN> > you just need two NS on two different IPs and configure bind (or powerdns, or whatever)
I have only 1 IP, my NS is already set at NS1 & NS2 at registrar
[14:48:02]
<selfhoster1312> in yunohost admin -> domains -> YOURDOMAIN -> DNS
there is "Suggested DNS records for manual configuration" section
[14:48:08]
<selfhoster1312> it contains a zone file for use in bind/other
[14:48:16]
<FbIN> & I have been using HestiaCP, so that way everything is fine. But I wish to make use of the awesome apps setup available via YNH, which for a non-dev like me makes things easier.
[14:48:37]
<selfhoster1312> > I have only 1 IP, my NS is already set at NS1 & NS2 at registrar
i don't understand can you maybe say what your domain is?
[14:48:42]
<FbIN> > in yunohost admin -> domains -> YOURDOMAIN -> DNS
> there is "Suggested DNS records for manual configuration" section
true, so I can configure bind9 normally and it should work, right?
[14:48:43]
<selfhoster1312> you can't have 2 NS with just 1 IP
[14:49:16]
<FbIN> > you can't have 2 NS with just 1 IP
it works for me. IPV4 itself.
[14:49:29]
<selfhoster1312> who's the second NS then?
[14:49:38]
<FbIN> those are just records, directing to that one single IP
[14:49:40]
<selfhoster1312> do you have secondary NS services with some provider ? (maybe your registrar provides it for you)
[14:49:45]
<FbIN> but that is not an issue at all, that is all good
[14:49:51]
<selfhoster1312> so you have two glue records to the same IP ???? ok
[14:50:02]
<selfhoster1312> so then yes you can just configure bind9 normally and it will work
[14:50:06]
<FbIN> I am just confused with host my own DNS, and that is why I am struggling
[14:50:13]
<FbIN> > so you have two glue records to the same IP ???? ok
crrct
[14:50:38]
<selfhoster1312> (i should say this is strongly NOT recommended to not have redundant DNS, that's why the registrar's interface forces you to have two NS / glue records)
[14:51:07]
<selfhoster1312> (if it works it's good, but *when* it breaks, for example because your server is down, it will bring mayhem :) :))
[14:51:08]
<FbIN> > so then yes you can just configure bind9 normally and it will work
okay, one last thing. & maybe I am unable to find the apt repo list for it. Debian 12 minimal installed + YNH on top. When I apt search bind9, I get no installable package found
[14:51:27]
<selfhoster1312> `apt update && apt install bind9` ?
[14:51:34]
<FbIN> > (if it works it's good, but *when* it breaks, for example because your server is down, it will bring mayhem :) :))
agreed, completely, but I cannot afford that, so have to make do with whatever I have available :)
[14:52:04]
<FbIN> > (i should say this is strongly NOT recommended to not have redundant DNS, that's why the registrar's interface forces you to have two NS / glue records)
agreed to this as well. "money" is the only "honey" here 😛
[14:52:16]
<FbIN> > `apt update && apt install bind9` ?
gives no installable package found
[14:52:31]
<FbIN> so, probably due to minimal debian, the repo apt is not added
[14:52:45]
<selfhoster1312> `cat /etc/apt/sources.list` ?
[14:53:06]
<selfhoster1312> should i understand you installed yunohost over plain debian minimal? (what even is debian minimal?)
[14:53:23]
<FbIN> sorry, let me say. I had to switch to HestiaCP, cause I could not get it working, but I can retry on a fresh installation tomorrow and revert.
[14:53:36]
<selfhoster1312> is it a netinst?
[14:53:44]
<selfhoster1312> (if so it should add the repos)
[14:54:08]
<FbIN> > should i understand you installed yunohost over plain debian minimal? (what even is debian minimal?)
debian minimal as the netinst with just SSH, curl & wget installed, and then I install what I need
[14:54:28]
<FbIN> > (if so it should add the repos)
I thought so, but I was getting confused, and brain was probably not braining
[14:54:45]
<selfhoster1312> good luck for brainz :) :)
[14:55:14]
<FbIN> ++ https://doc.yunohost.org/en/admin/get_started/post_install/dns_config/ this confuses anyone, honestly.
"If you're using your own domain name (e.g. bought via a registrar), you should manually configure your domain on your registrar's interface."
[14:55:17]
<selfhoster1312> hmm actually let me see, maybe port 53 is already in use by some other daemon on hyunohost
[14:55:36]
<selfhoster1312> because we already have dnsmasq
[14:56:10]
<FbIN> > because we already have dnsmasq
this is just me, but I find Bind9 easier and user friendly compared to dnsmasq
[14:56:36]
<selfhoster1312> i agree :)
[14:57:05]
<selfhoster1312> yeah dnsmasq already uses all interfaces on port 53
[14:57:10]
<FbIN> I wanted to suggest and request bind9, and allowing it to be configuarable via UI/terminal, like hestiacp does. It actually auto runs bind9 during HCP installation. which makes life very simpler.
[14:57:19]
<FbIN> sorry not saying YNH is bad or anything
[14:57:44]
<selfhoster1312> so *technically* you can run bind9 on a different port and configure your router to redirect WAN port 53 to something like 5353
[14:57:47]
<FbIN> due to DNS issues, I have been unable to set it up, and several non-dev who wish to make YNH as their panel, struggle badly
[14:58:07]
<selfhoster1312> yep, there's so much that could be improved! contributions are welcome :)
[14:58:32]
<FbIN> > so *technically* you can run bind9 on a different port and configure your router to redirect WAN port 53 to something like 5353
true. again, not denying that, but when YNH states, why you no host, that should be: "user friendly", and for novice as well.
[14:59:23]
<selfhoster1312> well it is user-friendly to some extent, some DNS providers are integrated (but then you don't host your own NS), and we have a community helping people AFK :)
[14:59:29]
<FbIN> > yep, there's so much that could be improved! contributions are welcome :)
I have seen in forums few times, many have suggested bind9, but either there has been no response, or there has like big no. It was last year and sometime when I search things come up.
[15:00:21]
<FbIN> > well it is user-friendly to some extent, some DNS providers are integrated (but then you don't host your own NS), and we have a community helping people AFK :)
true, but not in DNS stuff. Very rare. I have scrolled the forum several times, but I do not find what a simpler answer would be. everything is DNSMASQ only,:(
[15:00:35]
<selfhoster1312> btw other people, when yunohost says « YunoHost could not automatically detect the registrar handling this domain. You should manually configure your DNS records following the documentation at https://yunohost.org/dns. » what is the list of supported providers? i can't find it in the docs
[15:02:09]
<FbIN> > btw other people, when yunohost says « YunoHost could not automatically detect the registrar handling this domain. You should manually configure your DNS records following the documentation at https://yunohost.org/dns. » what is the list of supported providers? i can't find it in the docs
https://doc.yunohost.org/en/category/providers these?
[15:02:30]
<selfhoster1312> hmmm yes thanks :)
[15:03:19]
<FbIN> wc :)
[15:03:34]
<selfhoster1312> i was hoping RFC2136 support or something like that ^^
[15:05:00]
<FbIN> BTW, even with providers, they ask to configure DNS outside of server to registrars. Example OVH one:
https://doc.yunohost.org/en/admin/get_started/providers/registrar/ovh/manualdns
"then erase everything below, and replace it with the configuration generated by YunoHost as explained in this page."
[15:05:57]
<selfhoster1312> that's the manual configuration when you don't do the API magic bits :)
[15:06:41]
<FbIN> crrct
[15:06:54]
<FbIN> I do not use any of those providers, so I am just citing the only working one in that list
[15:13:18]
<FbIN> > well it is user-friendly to some extent, some DNS providers are integrated (but then you don't host your own NS), and we have a community helping people AFK :)
I found this: https://forum.yunohost.org/t/use-bind-of-your-yunohost-instance-as-your-dns-resolver/530, & I have this: https://www.server-world.info/en/note?os=Debian_12&p=dns&f=1 (this is awesome btw)
[15:54:46]
<FbIN> Even for subdomains, YNH asks to go to registrar: "YunoHost allows the use of subdomains. If one owns a domain name mydomain.com, one first needs to create the subdomains in the DNS configuration (with one's registrar like Gandi)."
https://doc.yunohost.org/en/admin/tutorials/domains/dns_subdomains
[15:55:55]
<selfhoster1312> if you are your own NS then you have nothing special to do :) (just add it in the zone)
[15:56:18]
<FbIN> the zonefile you mean, right?
[15:57:35]
<FbIN> > I found this: https://forum.yunohost.org/t/use-bind-of-your-yunohost-instance-as-your-dns-resolver/530, & I have this: https://www.server-world.info/en/note?os=Debian_12&p=dns&f=1 (this is awesome btw)
I use this server world stuff, just that once I get bind9 done, I will be able to use it. I will write a tutorial once I am able to run it successfully
[16:10:58]
<selfhoster1312> yes the zone file
[16:12:13]
<FbIN> 👍