diff --git a/REFDB_FORMAT.txt b/REFDB_FORMAT.txt
index 9f7d64f..b105e53 100644
--- a/REFDB_FORMAT.txt
+++ b/REFDB_FORMAT.txt
@@ -325,11 +325,19 @@ staggered_timing:
 
 wp-config_modification:
   function: disable_wpcron_in_config()
-  location: Line 2 after <?php tag
+  location: Before "/* That's all, stop editing! */" comment (proper WordPress convention)
+  fallback: After <?php tag if "stop editing" not found
   adds: define('DISABLE_WP_CRON', true);
-  safety: Backup created, verification, rollback on failure
+  safety: Removes existing entries first, backup created, verification, rollback on failure
   format: User crontabs (crontab -u $user) not system crontab
 
+domain_lookup_method:
+  # Fixed 2025-11-10 - Two-step lookup process
+  method_1: Check main_domain in /var/cpanel/userdata/*/main files (YAML: main_domain:)
+  method_2: Fallback to search domain-specific files for servername (YAML: servername:)
+  skip_files: "*.cache, */main, */cache, */cache.json"
+  rationale: cPanel stores main_domain in main files, servername in domain-specific files
+
 cron_job_format: |
   0,15,30,45 * * * * cd /home/user/public_html && /usr/bin/php -q wp-cron.php >/dev/null 2>&1
 
@@ -345,6 +353,19 @@ options:
   0: Return to menu (cancel)
 
 [RECENT_COMMITS]
+# Latest changes (2025-11-10)
+
+commit: 172a115
+  date: 2025-11-10
+  title: Fix domain lookup in WordPress Cron Manager
+  files: modules/website/wordpress/wordpress-cron-manager.sh
+  changes:
+    - Fixed broken domain lookup (was only searching /var/cpanel/userdata/*/main for servername:)
+    - Added two-step lookup: main_domain in main files, then servername in domain files
+    - Applied fix to options 2, 5, 6 (all domain lookup locations)
+    - Skip cache files during search
+  testing: Verified with pickledperil.com - lookup now works correctly
+
 # Latest changes (2025-11-07)
 
 commit: 56776a1