Infoblox’s global team of threat hunters uncovers a DNS operation with the ability to bypass traditional security measures and control the Great Firewall of China. Read about “Muddling Meerkat” and the many other threat actors discovered by Infoblox Threat Intel here.

API & Integration, DevOps,NetOps,SecOps

Reply

The action is not allowed. A parent was not found

New Member
Posts: 1
931     0

Hi,

 

We have a domain to which we are adding a SAN from a validated Sectigo integration.We have several domains in the SAN that are not in the same domain as the Common Name but has worked fine up until now. We are using the repo:
GitHub - svalgaard/certbot-dns-infoblox: Infoblox DNS Authenticator plugin for Certbot

 

We are seeing issues when the routine is executed to validate the domain by inserting a text record into the zone in question. The SAN domain being added is a sub domain. The routine in question is https://github.com/svalgaard/certbot-dns-infoblox/blob/main/certbot_dns_infoblox/dns_infoblox.py and specifically:

def _perform(self, domain, validation_name, validation):
        txt = infoblox_client.objects.TXTRecord.create(
            **self._get_infoblox_record(validation_name, validation, True)
        )
        self.infotxts.append(txt)

The error generated is:

infoblox_client.exceptions.InfobloxCannotCreateObject: Cannot create 'record:txt' object(s): b'{ "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:The action is not allowed. A parent was not found.)", \n  "code": "Client.Ibap.Data.Conflict", \n  "text": "The action is not allowed. A parent was not found."\n}' [code 400]

The zone and subzone definitely exist and can be queried using excerpts from the above script , and the request is in FQDN format under the name variable.

 

Anyone experienced this before?

Showing results for 
Search instead for 
Did you mean: 

Recommended for You