PHPINIDir directive error in httpd.conf

I'm not sure when this started, or even if I've tried to fix it before. ITs getting pretty annoying, so I guess its time for an attempt.

In my httpf.conf file, there are two entries for each domain. One for the SSL version, one for the 'regular' one.
I dont know if thats normal, but everything on my server is working fine, and has been for a while now.

However, for one domain, both of its entries contain a line declaring the PHPINIDir. Now, if I try to start or restart the httpd service, I get an error stating that only one PHPINIDir may be declared, causing the service not to start.
To work around this, I have to edit the httpd.conf file and comment out one of the PHPINIDirs. After that, the htppd service starts fine again.
The problem is that, whenever I do something in DA resulting in a change in the httpd.conf file, like adding a new domain, the issue returns. The PHPINIDir lines will return and cause the same issue.

Any insights into this issue, where it might have come from and how I might fix it would be welcome!

Hello,

Directadmin does not set PHPINIDir. So it must be your customization. Did you add it under VirtualHost? Or where?

Thanks @zEitEr, that pointed me in the right direction. I found it under the affected domain in DA under custom HTTPD Configurations.
The line declaring the PHPINIdir is present there.
I must have added this myself, I guess I needed a different PHP.ini just for that domain, dont recall why.
This is the correct method to add a different PHPINIDir for a domain though, right? If so, I dont understand why its adding two of them, causing httpd to not start.

It might be added twice: once for HTTP and another on for HTTPS.

Getting rid of the line in custom httpd config got rid of the issue. Now I still dont know if this is a DA bug or expected behavior because I tried to do something the wrong way.. I'll leave it alone for now, as I don't need a custom php.ini for that domain to start with.