I've been starting to play with IPv6 recently and I wanted to see if Webmin supported IPv6 AAAA records.
It appears as though when I try and create a forward lookup record that has an IPv6 address, I get the error "Failed to save record : '2001:db8::3' is not a valid IP address".
I can create a reverse lookup zone 2001::0 and I can add a reverse entry to it for 2001:db8::3.
I then go back to the forward lookup zone and it's not in the list.
However if I look in the /var/named/test.local.hosts file I can see the entry has been created when the reverse entry was created.
test6.test.local. IN AAAA 2001:db8::3
I've skimmed through the code and I can see there are bits of code dedicated to IPv6, so I'm not sure if the current issue with AAAA records is intentional. I did read this documentation:
However it does not list AAAA records as being supported.
Is what I am experiencing a bug, or it is intended that AAAA records are not fully supported ?
System hostname centosxx.box293.local
Operating system CentOS Linux 6.7
Webmin version 1.791
Time on system Wed Apr 27 17:35:46 2016
Kernel and CPU Linux 2.6.32-573.el6.x86_64 on x86_64
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK so I looked at this again today with a fresh set of eyes and I noticed that when I was on the "Edit Master Zone" page, when I hovered my mouse over the Address icon I saw the following:
Ahhhh so I can see that the Addresses screen is just Type A addresses, which makes sense.
Then I realised there was another icon "IPv6 Addresses" which was not so obvious (see attached image). When I clicked this, those test addresses I created from the reverse zone were here, yay!
It might be worthwhile making it so that the "Addresses" and "IPv6 Addresses" icons are side by side.
I've been starting to play with IPv6 recently and I wanted to see if Webmin supported IPv6 AAAA records.
It appears as though when I try and create a forward lookup record that has an IPv6 address, I get the error "Failed to save record : '2001:db8::3' is not a valid IP address".
I can create a reverse lookup zone 2001::0 and I can add a reverse entry to it for 2001:db8::3.
I then go back to the forward lookup zone and it's not in the list.
However if I look in the /var/named/test.local.hosts file I can see the entry has been created when the reverse entry was created.
test6.test.local. IN AAAA 2001:db8::3
I've skimmed through the code and I can see there are bits of code dedicated to IPv6, so I'm not sure if the current issue with AAAA records is intentional. I did read this documentation:
http://doxfer.webmin.com/Webmin/BIND_DNS_Server#Record_types
However it does not list AAAA records as being supported.
Is what I am experiencing a bug, or it is intended that AAAA records are not fully supported ?
System hostname centosxx.box293.local
Operating system CentOS Linux 6.7
Webmin version 1.791
Time on system Wed Apr 27 17:35:46 2016
Kernel and CPU Linux 2.6.32-573.el6.x86_64 on x86_64
OK so I looked at this again today with a fresh set of eyes and I noticed that when I was on the "Edit Master Zone" page, when I hovered my mouse over the Address icon I saw the following:
https://10.25.254.251:10000/bind8/edit_recs.cgi?zone=test.local&view=any&type=A
Ahhhh so I can see that the Addresses screen is just Type A addresses, which makes sense.
Then I realised there was another icon "IPv6 Addresses" which was not so obvious (see attached image). When I clicked this, those test addresses I created from the reverse zone were here, yay!
It might be worthwhile making it so that the "Addresses" and "IPv6 Addresses" icons are side by side.
With this in mind, it might be worthwhile updating the documentation on Recored Types:
http://doxfer.webmin.com/Webmin/BIND_DNS_Server#Record_types