Friday, 2021-02-26

*** ianychoi__ is now known as ianychoi00:34
*** hamalq has quit IRC01:10
*** icey_ is now known as icey07:43
openstackgerritMerged openstack/designate stable/stein: Adding distributed locking to central  https://review.opendev.org/c/openstack/designate/+/77628810:00
*** mugsie_ is now known as mugsie10:16
*** zigo has joined #openstack-dns13:21
openstackgerritNicolas Bock proposed openstack/designate stable/stein: Update zones masters using pool target masters.  https://review.opendev.org/c/openstack/designate/+/74479613:44
openstackgerritNicolas Bock proposed openstack/designate stable/ussuri: Update zones masters using pool target masters.  https://review.opendev.org/c/openstack/designate/+/74361013:47
nicolasbockjohnsom: I am working on getting the series https://review.opendev.org/q/I9dddd4130a0cbb29311eeb52e077e216c8c03f3a green so we can merge them. If I remember correctly this change was one you wanted to see in Stein before we might cut another release.16:05
johnsomCool, that is a good bug to get fixed16:27
*** icey has quit IRC16:33
*** icey has joined #openstack-dns16:34
*** hamalq has joined #openstack-dns17:16
hamalqhi can i get +1 on https://review.opendev.org/c/openstack/designate/+/754226/17:17
nicolasbockSorry for the delays hamalq17:43
nicolasbockI left you some comments17:43
hamalqam doing the changes :)17:47
openstackgerrithamza proposed openstack/designate master: Adding split horizon documentation  https://review.opendev.org/c/openstack/designate/+/75422617:52
hamalqdonee17:52
hamalq@nicolasbock thanks for the review17:53
nicolasbockThanks hamalq . I'll have another look soon.18:01
*** spatel has joined #openstack-dns18:36
hamalqthanks18:43
eanderssonIs Designate meant to allow for ns records to be created for child zones? e.g. should office.home.com be allowed to create an NS record for the sub-domain dev? dev.office.home.com NS 192.168.0.120:48
eanderssonI don't think we allow that todayu20:48
*** spatel has quit IRC21:10
nicolasbockHmm, how would you define one in the zone file? Would you need to create another SOA entry eandersson ?21:22
eanderssonI don't belive so. This would be in place to allow recursive lookups.21:24
nicolasbockYou can do `openstack recordset create --records 1.1.1.1 --type A example.com. host1.subdomain` right now21:25
nicolasbockBut that's not maybe what you want21:25
eanderssonYea - the problem is that you might have child zones21:25
eanderssone.g.21:25
eanderssonopenstack zone create home.com21:26
eanderssonopenstack zone create office.home.com21:26
eanderssonopenstack zone create dev.home.com21:26
eanderssonopenstack zone create prod.home.com21:26
nicolasbockI don't think we can do that as a child zone. They would be independent zones.21:27
eanderssonI think I need to do some light reading on how this is meant to work.21:28
eanderssonMaybe johnsom has some insight into the RFCs :D21:28
nicolasbockHaha21:28
nicolasbockI found this: https://nnc3.com/mags/Networking2/dns/ch09_04.htm21:29
johnsomWhat is the question you summoned me for???? Hi21:29
eanderssonThe idea is that other DNS servers not controlled by designate might only be aware of home.com, and to allow recursive lookups you would add NS records for the sub domains21:30
eanderssonSo home.com would have a NS pointing at office.home, office.com would have NS records for dev and prod21:30
eanderssonCurrently in designate adding a NS for DEV in office.home.com would result in a RecordSet belongs in a child zone dev.home.com21:31
eanderssonjohnsom basically asking if you know if this is WAI :D ^21:32
eanderssonbrb food21:32
johnsomhahaha, summons me, then runs21:32
johnsomI guess I'm not following the scenario here well.21:33
nicolasbockThere appear to be different ways of managing a subdomain johnsom . Unfortunately that's all I can say at this point. I am still reading how this is supposed to work :)21:34
johnsomThe original question, can you add delegation from a Designate "owned" zone, sure, it should be possible. I.e. adding NS records in example.com for eandersson-food.example.com.21:34
nicolasbockThere we go :)21:35
nicolasbockBy the way, https://review.opendev.org/c/openstack/designate/+/743610 is green now. johnsom, eandersson, could you have a look?21:35
nicolasbockThis one is green too, but we need the Ussuri patch first. https://review.opendev.org/c/openstack/designate/+/74361121:36
johnsomnicolasbock Cool, thanks. Technically I am on vacation today and Monday, so I haven't been following too closely21:36
nicolasbockThe backport to Stein keeps timing out for some reaons21:36
nicolasbockOh sorry21:36
johnsomNo, no worries21:36
nicolasbockDidn't mean to rope you in here on your vacation21:36
nicolasbockBut that was eandersson 's fault ;)21:36
johnsomExactly21:37
johnsomgrin21:37
johnsomIt's a distraction from doing my taxes21:40
johnsomThere is a check like: https://github.com/openstack/designate/blob/master/designate/api/v2/controllers/zones/recordsets.py#L11621:43
johnsomYou can't hack the zones that are owned by Designate.21:44
eanderssonhttps://opendev.org/openstack/designate/src/branch/master/designate/central/service.py#L32221:46
eanderssonThis is the one I saw as well preventing the NS record from being created in the parent.21:46
eanderssonAlso taxes -_- I haven't even started mine21:46
johnsomToday was an opportunity, so...21:47
johnsomI'm not sure I answered your question or not.21:47
eanderssonYea you did21:47
johnsomCool, I hope I was right. grin21:47
eanderssonI wonder if it is as simple just excluding NS records from that check21:48
johnsomWhy? That check is valid.21:49
johnsomA delegation for eandersson-food.example.com must be under example.com. You can't create a delegation for eandersson-food.tacos.com from an example.com zone.21:50
eanderssonoh yea https://opendev.org/openstack/designate/src/branch/master/designate/central/service.py#L37121:50
eanderssonWrong function21:50
eanderssonLine 378 is what actually throws the error21:51
eanderssonLet me reproduce the error21:51
johnsomI vaguely remember a bug or someone talking about this check.21:54
johnsomI think the intent is if you are adding a record burger.eandersson-food.example.com to the example.com zone, should there be a eandersson-food.example.com zone, deny it and make them create burger in the eandersson-food.example.com zone instead.21:56
eanderssonFrom what I understand the issue is that there is a root server that only knows of example.com, and the "local" dns server is meant to recursively lookup records from e.g. eandersson-food.example.com21:56
eanderssonbut without a NS record in example.com pointing at eandersson-food the local DNS server wouldn't allow recursive lookups21:56
johnsomWell, you can delegate eandersson-food to designate authoritative servers from the example.com zone. That way it is globally resolvable.21:57
eanderssonRight22:00
eanderssonopenstack recordset create example.com. eandersson-food --type NS --record '192.168.0.1' --record '192.168.0.2'22:03
eanderssonThis is one way of doing that right?22:03
eanderssonIn this case designate owns both example.com and eandersson-food.example.com22:03
johnsomI'm confused, if Designate owns (by own I think has a zone defined and manages the authoritative zone in bind/pdns), there  are zone records for both example.com and eandersson-food.example.com in Designate. In which case, you cannot touch the NS records.22:06
johnsomIf Designate just has a zone for example.com, then yeah, you would add a NS record (which BTW, are FQDN "records") for each authoritative server that hosts the eandersson-food zone. You need glue records for the NS FQDNs22:08
eanderssonDon't worry I am confused too.22:08
johnsomI guess I should say, you may need glue records22:08
johnsomI can take one more pass at describing delegation if that would help.22:13
johnsomTo delegate eandersson-food.example.com to an outside DNS server (i.e. not a zone owned by Designate) you would end up with the following in the example.com zone file (owned by Designate in this example):22:14
johnsom eandersson-food.example.com IN NS ns1.eandersson-food.example.com22:15
johnsomand a glue record:22:15
johnsomns1.eandersson-food.example.com IN A 192.0.2.9922:16
johnsomWhere 192.0.2.99 is the authoritative DNS server that will host  eandersson-food.example.com22:16
johnsomThis topic is actually one michchap and I have been talking about recently in our "upstream docs needed" series. The designate docs don't have cookbooks for how to integrate Designate into an existing DNS infrastructure. It's on our TODO list.22:21
eanderssonAwesome! Yea I think that is it22:45
eanderssonjohnsom when you are off vacation https://bugs.launchpad.net/designate/+bug/191709923:35
openstackLaunchpad bug 1917099 in Designate "NS records for child zones should be allowed to exist in parent zones" [Undecided,New]23:35
*** hamalq has quit IRC23:40

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!