Hello,
I’m having some interesting behavior happening when creating a network zone and trying to attach it to a network. The zone will not show up as transferable when I add it to the network, but when I remove it I can actually see the zone that’s created with none of my instances inside of it.
Here we go!
My Network Zones
+--------------------------------------+------------------------------------+---------+
| NAME | DESCRIPTION | USED BY |
+--------------------------------------+------------------------------------+---------+
| 50.168.192.in-addr.arpa | Reverse Zone for Internal-Services | 0 |
+--------------------------------------+------------------------------------+---------+
| lxd.internal-services.thelabs.online | Forward zone for internal-services | 0 |
+--------------------------------------+------------------------------------+---------+
Me using dig to see if I can see the zone
dig @192.168.20.51 -p 8853 axfr lxd.internal-services.thelabs.online
; <<>> DiG 9.18.1-1ubuntu1.1-Ubuntu <<>> @192.168.20.51 -p 8853 axfr lxd.internal-services.thelabs.online
; (1 server found)
;; global options: +cmd
lxd.internal-services.thelabs.online. 3600 IN SOA lxd.internal-services.thelabs.online. ns1.lxd.internal-services.thelabs.online. 1662441484 120 60 86400 30
lxd.internal-services.thelabs.online. 300 IN NS ns1.lxd.internal-services.thelabs.online.
lxd.internal-services.thelabs.online. 3600 IN SOA lxd.internal-services.thelabs.online. ns1.lxd.internal-services.thelabs.online. 1662441484 120 60 86400 30
;; Query time: 4 msec
;; SERVER: 192.168.20.51#8853(192.168.20.51) (TCP)
;; WHEN: Tue Sep 06 05:18:09 UTC 2022
;; XFR size: 3 records (messages 1, bytes 440)
My Network
config:
bridge.mtu: "1442"
ipv4.address: 192.168.50.1/24
ipv4.nat: "false"
ipv6.address: fd42:a80d:8b07:c1cc::1/64
ipv6.nat: "true"
network: UPLINK
volatile.network.ipv4.address: 192.168.20.34
volatile.network.ipv6.address: 2600:8802:b00:1602:216:3eff:fea5:1bd1
description: ""
name: internal-services
type: ovn
My network with the zone
config:
bridge.mtu: "1442"
dns.zone.forward: lxd.internal-services.thelabs.online
ipv4.address: 192.168.50.1/24
ipv4.nat: "false"
ipv6.address: fd42:a80d:8b07:c1cc::1/64
ipv6.nat: "true"
network: UPLINK
volatile.network.ipv4.address: 192.168.20.34
volatile.network.ipv6.address: 2600:8802:b00:1602:216:3eff:fea5:1bd1
description: ""
name: internal-services
type: ovn
Me trying dig again
dig @192.168.20.51 -p 8853 axfr lxd.internal-services.thelabs.online
; <<>> DiG 9.18.1-1ubuntu1.1-Ubuntu <<>> @192.168.20.51 -p 8853 axfr lxd.internal-services.thelabs.online
; (1 server found)
;; global options: +cmd
; Transfer failed.
I have tried re-creating… creating new zones and it still has this weird behavior.
I do already have another zone in another project on another network working as it’s supposed to.
Thanks for your help.