...
To create a record (for example, test.sampledomain.cybera.ca) using the command line tools:
AAAA record:
Code Block |
---|
openstack recordset create --records "2605:fd00:4:1000:abcd:ef12:3456:7890" --type AAAA --description "IPv6 AAAA Record" sampledomain.cybera.ca. test |
A record:
Code Block |
---|
openstack recordset create --records "127.0.0.1" --type A --description "IPv4 A Record" sampledomain.cybera.ca. test |
To update a record:
Code Block |
---|
openstack recordset set --records "2605:fd00:4:1000:aaaa:bbbb:cccc:dddd" --description "IPv6 AAAA Record" sampledomain.cybera.ca. test.sampledomain.cybera.ca |
If multiple records exist using the same record name, you will need to use the ID of the record instead, similar to what is required for other OpenStack services:
Code Block |
---|
openstack recordset set --records "2605:fd00:4:1000:aaaa:bbbb:cccc:dddd" --description "IPv6 AAAA Record" sampledomain.cybera.ca. 2eee8889-ae7b-4271-8c39-abce5d2144ec |
To delete a record:
Code Block |
---|
openstack recordset delete sampledomain.cybera.ca. test.sampledomain.cybera.ca |
If multiple records exist using the same record name, you will need to use the ID of the record instead, similar to what is required for other OpenStack services:
Code Block |
---|
openstack recordset delete sampledomain.cybera.ca. 2eee8889-ae7b-4271-8c39-abce5d2144ec |
Common Issues
The most common issue seen when using the new automated names occurs when a service is running on the instance but not listening on IPv6 when the user has IPv6 access. As IPv6 is the default path used when available it's important to ensure that your security groups and services on your instance can handle IPv6 traffic. See the Security Groups section in the Basic Guide for more information.
...