Skip to main content
Flexible Top Header

I’m attempting to do a POST to /api/v2/networks/{collection-id}/addresses to grab an IP address and put a DNS name on it. This is working find except when I attempt to add a wildcard DNS entry like the following:

{

    "name": "*.example.net",                             ← This puts a name on the IPv4 address object

    "type": "IPv4Address",

    "state": "STATIC",

    "userDefinedFields": {

        "mnemonic": "OCP"

    },

    "resourceRecords": 

        {

            "type": "HostRecord",

            "absoluteName": "*.example.net",               ← This should put a host record into the example.net zone

            "views": 

                {

                    "id": "93864"

                }

            ],

            "userDefinedFields": {

                "mnemonic": "OCP"

            }

        }

    ]

}

 

 

{

    "status": 400,

    "reason": "Bad Request",

    "code": "InvalidFullyQualifiedDomainName",

    "message": "The value for resource field 'resourceRecords0].absoluteName' is not a valid fully qualified domain name"

}

 

 

Any one done this and happen to know the right syntax? I’ve tried a number of ways to escape the wildcard in Postman with no luck.

You didn’t mention what version you’re trying this against.  I tested it against one of the beta builds of 25.1 (haven’t gotten around to installing the GA version yet) and it fails there.  I was however able to create the wildcard record by posting to /api/v2/zones/{collection}/resourceRecords and using “name”:”*” instead of “absoluteName” with an FQDN.  So it seems you can get the record in there, just not in a single call during address assignment.  I’d probably consider inability to use “*” in absoluteName a bug.


I’m running this against a physical appliance BAM on version 9.5.3. I think you’re probably right, but was hoping there was some way to properly escape the “*” to make this usable.


Reply