-
|
There is already a record in "managed records" test A 192.168.10.34 I create a record ( not in the managed records) - TesT with the same IP This gets created successfully. Same thing happens if I create 2 differently cased records with same IP address in the Records : TeST A 192.168.10.34 These gets created successfully. How can I avoid this? netbox-plugin-dns 1.2.3 In - /opt/netbox/netbox/netbox/configuration.py |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
|
Hi @john, thanks for raising this topic, very good point! So far the plugin (naïvely) assumes that nobody ever has the idea of using anything but lowercase in DNS names :-) Turns out that this is a bug. I just opened #547 for it.
For the time being: Don't do that. As soon as #547 is fixed, the problem will be solved. |
Beta Was this translation helpful? Give feedback.
-
|
On second thought I changed the approach on this a bit. Instead of indiscriminately converting all names to lowercase this function has been made optional. Instead, all comparisons of zone and domain names (including name server names) has been made case insensitive, which makes more sense in terms of RFC compliance. Normalising all names to lowercae is still possible using the configuration variable |
Beta Was this translation helpful? Give feedback.
Hi @john2893, not quite.
If
convert_names_to_lowercaseis set to True, all names will be converted to lowercase, trivially enforcing uniqueness.If it's
False, names will be left as they are, but different casings of the same name still can't coexist as they are, in terms of the RFCs, the same name.This change will be in 1.2.5, due when NetBox 4.2.5 is released. There's a change coming with NetBox 4.2.5 that will make it possible to "Quick Add" name servers and views when adding a Zone without leaving the zone form, which is a nice enhancement that was previously not possible because of a NetBox bug.