DNS Misconfiguration

Posted by: Paul Pampolino Date Posted: June 25, 2026
Back to Case Studies

Issue

After the architect upgraded to the DNS version of the RCFX pixel, the client’s Contact Us form stopped pulling into LeadManagerFX. The architect tried updating the CSS selector to the form ID — no improvement. They escalated as in-progress because this was the only form tracked for the client and their primary lead driver.

The DNS URL was configured as https://www.mclfx.mccreathlabs.com/ — with a www subdomain prefix. DNS pixel URLs typically don’t use www, so the pixel was attempting to load from an incorrect origin and silently failing. The RCFX pixel was present in the source code, but never actually executing.

Solution

Changed the DNS URL from https://www.mclfx.mccreathlabs.com/ to https://mclfx.mccreathlabs.com/ — removing the www prefix. Also reverted the CSS selector for the Contact Us form to its original value. After the update, form data was confirmed passing through LMFX.

Achievement

Form tracking restored by a single-character DNS URL correction. A subtle misconfiguration introduced during the DNS pixel upgrade — easy to miss, high impact on the client’s only tracked lead source.

Snippet/Screenshot/Link