Configuring Wildcard Subdomains in cPanel

Table of Contents

1. Understanding Wildcard Subdomains
2. Benefits and Use Cases
3. Accessing cPanel
4. Configuring Wildcard Subdomains
5. WordPress Multisite Implementation
6. Catch-All Subdomain Setup
7. Advanced Configuration Options
8. Testing and Verification
9. Troubleshooting Common Issues
10. Security Considerations
11. Getting Support

Understanding Wildcard Subdomains

What is a Wildcard Subdomain?

A wildcard subdomain is a DNS and server configuration that allows any subdomain request for your domain to be automatically handled by a single configuration. Instead of creating individual subdomains for blog.example.com, shop.example.com, and support.example.com, a wildcard subdomain configuration uses *.example.com to catch all possible subdomain requests and route them to a designated location.

When a wildcard subdomain is configured, any request to a subdomain that doesn't have a specific configuration will be handled by the wildcard rule. This means that anything.yourdomain.com, test123.yourdomain.com, or even completely-random-text.yourdomain.com will all resolve and can be processed by your application.

How Wildcard Subdomains Function

The wildcard subdomain system operates at both the DNS and web server levels:

DNS Level: The DNS record *.yourdomain.com is configured to point to your server's IP address, ensuring that all subdomain requests reach your hosting server.

Server Level: Your web server (Apache/nginx) is configured to handle these wildcard requests and route them to a specific directory or application that can process the subdomain dynamically.

Application Level: Your website application can then examine the requested subdomain and respond accordingly, whether by serving different content, redirecting to appropriate pages, or displaying custom error messages.

Benefits and Use Cases

Business and Technical Advantages

Simplified Management: Instead of manually creating dozens of individual subdomains, you can handle unlimited subdomains with a single configuration, significantly reducing administrative overhead.

Dynamic Content Delivery: Enable applications to create subdomains on-demand without requiring manual server configuration, perfect for user-generated content platforms or multi-tenant applications.

Brand Protection: Automatically catch and handle attempts to access misspelled or unauthorized subdomains, preventing competitors from capitalizing on typos or protecting your brand reputation.

Development Efficiency: Streamline development and testing processes by automatically handling staging environments, feature branches, or client-specific versions without manual configuration.

Common Implementation Scenarios

WordPress Multisite Networks: Enable unlimited WordPress sites under your domain, allowing users to create username.yourdomain.com sites automatically without manual intervention.

Customer Portals: Provide personalized subdomains for customers like clientname.yourdomain.com that automatically route to their dedicated portal areas.

Geographic or Language Targeting: Implement location-specific subdomains such as london.yourdomain.com or paris.yourdomain.com that dynamically serve localized content.

API Versioning: Handle API version management through subdomains like v1.api.yourdomain.com or v2.api.yourdomain.com with automatic routing.

Error Prevention: Catch common misspellings of popular subdomains (like ww.yourdomain.com instead of www.yourdomain.com) and redirect users to the correct location.

Marketing Campaigns: Create campaign-specific subdomains for tracking purposes without pre-configuration, enabling rapid deployment of marketing initiatives.

Accessing cPanel

Before configuring wildcard subdomains, you need to access your cPanel hosting control panel. iFastNet provides multiple methods to ensure convenient access to your hosting management tools.

Method 1: iFastNet Client Portal Access

1. Navigate to Client Portal: Open your web browser and visit https://ifastnet.com/portal/clientarea.php
2. Account Authentication: Enter your iFastNet account credentials (username and password) in the login form
3. Service Management: After successful login, you'll be presented with your account dashboard showing all associated hosting services
4. cPanel Access: Locate your hosting service in the services list and click the "Login to cPanel" button or equivalent link
5. Automatic Login: You'll be automatically authenticated into cPanel without requiring additional credential entry

Method 2: Direct cPanel Access

1. Direct URL Navigation: Navigate to https://yourdomain.com/cpanel (substitute "yourdomain.com" with your actual registered domain name)
2. Credential Entry: Input your cPanel-specific username and password in the authentication form
3. Control Panel Access: Click "Log in" to access the cPanel management interface

Important: Your cPanel credentials are typically provided in your hosting welcome email or can be retrieved from the service details section within your iFastNet client portal.

Verifying Access

Once successfully logged in, you should see the cPanel main dashboard displaying various management sections including Domains, Email, Files, Databases, and other hosting tools. The interface will show your primary domain and account information in the header area.

Configuring Wildcard Subdomains

Step 1: Access Subdomain Management

1. Navigate to Domains Section: On the cPanel main dashboard, locate the "Domains" section, typically found in the upper portion of the interface
2. Select Subdomains: Click on "Subdomains" to access the subdomain management interface
3. Management Interface: This opens the comprehensive subdomain configuration panel where you can view existing subdomains and create new ones

Step 2: Create the Wildcard Subdomain

Subdomain Configuration:

1. Subdomain Field: In the "Subdomain" text field, enter an asterisk (*) as the subdomain name
2. Domain Selection: From the domain dropdown menu, select the domain for which you want to enable wildcard subdomain functionality
3. Document Root: Specify the directory path where wildcard subdomain requests should be directed

Document Root Options:

• Dedicated Directory: Create a specific folder like /public_html/wildcard/ for handling all wildcard requests
• Main Website: Point to /public_html/ to handle wildcard requests through your main website
• Application Directory: Direct to a specific application folder that can process subdomain requests dynamically

Example Configuration:

• Subdomain: *
• Domain: yourdomain.com
• Document Root: /public_html/wildcard/

Step 3: Configure Directory Structure

Create Directory Structure:

1. Access File Manager: Navigate to cPanel ? Files ? File Manager
2. Navigate to Root: Go to your /public_html/ directory
3. Create Wildcard Directory: Create a new folder named wildcard (or your chosen directory name)
4. Set Permissions: Ensure the directory has appropriate permissions (typically 755) for web access

Directory Organization:

/public_html/
??? wildcard/
?   ??? index.php (main handler)
?   ??? .htaccess (URL rewriting rules)
?   ??? assets/ (CSS, JS, images)
?   ??? includes/ (PHP includes/functions)

Step 4: Implement Subdomain Detection Logic

Create Main Handler File (/public_html/wildcard/index.php):

<?php
// Get the requested subdomain
$host = $_SERVER['HTTP_HOST'];
$subdomain = str_replace('.yourdomain.com', '', $host);

// Remove 'www' if present
if ($subdomain === 'www') {
    $subdomain = '';
}

// Handle different subdomain scenarios
if (empty($subdomain)) {
    // Main domain access
    header('Location: https://yourdomain.com');
    exit;
} else {
    // Process subdomain request
    handleSubdomain($subdomain);
}

function handleSubdomain($subdomain) {
    // Your subdomain handling logic here
    echo "<h1>Welcome to " . htmlspecialchars($subdomain) . ".yourdomain.com</h1>";
    echo "<p>This is a dynamically generated page for the '{$subdomain}' subdomain.</p>";
}
?>

Step 5: Configure URL Rewriting

Create .htaccess File (/public_html/wildcard/.htaccess):

RewriteEngine On

# Handle all requests through index.php
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php [QSA,L]

# Optional: Force HTTPS
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

Step 6: Complete Subdomain Creation

1. Review Configuration: Double-check all entered information including the asterisk symbol, domain selection, and document root path
2. Create Subdomain: Click the "Create" or "Add Subdomain" button to implement the wildcard configuration
3. Confirmation: Look for a success message confirming the wildcard subdomain has been created
4. Verification: The wildcard entry should appear in your subdomains list showing *.yourdomain.com

WordPress Multisite Implementation

Prerequisites for WordPress Multisite

WordPress Requirements:

• WordPress installation in your main domain directory
• Administrative access to WordPress dashboard
• Database with sufficient permissions for creating additional tables
• Understanding of WordPress multisite architecture and limitations

Server Requirements:

• Wildcard subdomain configuration (completed in previous section)
• Adequate storage space for multiple WordPress installations
• Sufficient bandwidth allocation for increased traffic
• PHP memory limits appropriate for multisite operations

Step 1: Enable WordPress Multisite Network

Access WordPress Configuration:

1. File Manager Access: Navigate to cPanel ? Files ? File Manager
2. WordPress Directory: Go to your WordPress installation directory (typically /public_html/)
3. Edit wp-config.php: Locate and edit the wp-config.php file

Add Multisite Configuration: Insert the following code before the "That's all, stop editing!" line in wp-config.php:

/* Multisite Configuration */
define('WP_ALLOW_MULTISITE', true);
define('MULTISITE', true);
define('SUBDOMAIN_INSTALL', true);
define('DOMAIN_CURRENT_SITE', 'yourdomain.com');
define('PATH_CURRENT_SITE', '/');
define('SITE_ID_CURRENT_SITE', 1);
define('BLOG_ID_CURRENT_SITE', 1);

Step 2: Configure WordPress Network Settings

WordPress Dashboard Configuration:

1. Access Dashboard: Log into your WordPress admin dashboard
2. Network Setup: Navigate to Tools ? Network Setup
3. Subdomain Configuration: Select "Sub-domains" option for network sites
4. Network Details: Enter your network title and admin email address
5. Install Network: Click "Install" to create the multisite network

Additional Configuration Files: WordPress will provide additional code snippets to add to your wp-config.php and .htaccess files. Copy and implement these exactly as provided.

Step 3: Configure Multisite .htaccess Rules

Update Main .htaccess (/public_html/.htaccess):

RewriteEngine On
RewriteBase /

# WordPress Multisite Rules
RewriteRule ^index\.php$ - [L]

# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
RewriteRule . index.php [L]

Step 4: Create New Multisite Installations

Network Admin Access:

1. Network Dashboard: Access the Network Admin dashboard (My Sites ? Network Admin)
2. Add New Site: Navigate to Sites ? Add New
3. Site Configuration: Enter the subdomain name, site title, and admin details
4. Create Site: The new WordPress site will be automatically created at sitename.yourdomain.com

User Management:

• Super Admin: Maintain network-wide administrative control
• Site Admins: Assign individual site administrative privileges
• User Roles: Configure appropriate user roles and capabilities for each site

Catch-All Subdomain Setup

Implementing Misspelling Protection

Common Misspelling Scenarios:

• ww.yourdomain.com instead of www.yourdomain.com
• wwww.yourdomain.com (extra 'w')
• mail.yourdomain.com when users mean webmail.yourdomain.com
• Transposed letters in legitimate subdomains

Detection and Redirection Logic:

Create an enhanced handler (/public_html/wildcard/index.php):

<?php
// Get subdomain from request
$host = $_SERVER['HTTP_HOST'];
$subdomain = str_replace('.yourdomain.com', '', $host);

// Define legitimate subdomains
$validSubdomains = [
    'www' => 'https://yourdomain.com',
    'blog' => 'https://yourdomain.com/blog/',
    'shop' => 'https://yourdomain.com/store/',
    'support' => 'https://yourdomain.com/contact/',
    'mail' => 'https://yourdomain.com/webmail/'
];

// Define common misspellings and their corrections
$misspellings = [
    'ww' => 'www',
    'wwww' => 'www',
    'www2' => 'www',
    'blog' => 'blog',
    'blgo' => 'blog',
    'suport' => 'support',
    'supprt' => 'support'
];

// Check for exact matches
if (isset($validSubdomains[$subdomain])) {
    header('Location: ' . $validSubdomains[$subdomain], true, 301);
    exit;
}

// Check for misspellings
if (isset($misspellings[$subdomain])) {
    $corrected = $misspellings[$subdomain];
    if (isset($validSubdomains[$corrected])) {
        header('Location: ' . $validSubdomains[$corrected], true, 301);
        exit;
    }
}

// Handle unrecognized subdomains
handleUnknownSubdomain($subdomain);

function handleUnknownSubdomain($subdomain) {
    http_response_code(404);
    include 'error-page.php';
}
?>

Custom Error Page Implementation

Create Error Page (/public_html/wildcard/error-page.php):

<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>Subdomain Not Found - <?php echo htmlspecialchars($_SERVER['HTTP_HOST']); ?></title>
    <style>
        body { font-family: Arial, sans-serif; margin: 40px; text-align: center; }
        .container { max-width: 600px; margin: 0 auto; }
        .error-code { font-size: 72px; color: #e74c3c; margin-bottom: 20px; }
        .suggestions { text-align: left; margin: 30px 0; }
        .suggestion-link { display: block; margin: 10px 0; color: #3498db; }
    </style>
</head>
<body>
    <div class="container">
        <div class="error-code">404</div>
        <h1>Subdomain Not Found</h1>
        <p>The subdomain <strong><?php echo htmlspecialchars($subdomain); ?>.yourdomain.com</strong> does not exist.</p>
        
        <div class="suggestions">
            <h3>Did you mean:</h3>
            <a href="https://yourdomain.com" class="suggestion-link">yourdomain.com (Main Site)</a>
            <a href="https://www.yourdomain.com" class="suggestion-link">www.yourdomain.com</a>
            <a href="https://yourdomain.com/blog/" class="suggestion-link">Blog</a>
            <a href="https://yourdomain.com/contact/" class="suggestion-link">Contact Us</a>
        </div>
        
        <p><a href="https://yourdomain.com">Return to Main Site</a></p>
    </div>
</body>
</html>

Analytics and Logging

Track Subdomain Requests:

// Add to your main handler
function logSubdomainRequest($subdomain, $action) {
    $logFile = '/path/to/logs/subdomain-requests.log';
    $timestamp = date('Y-m-d H:i:s');
    $userAgent = $_SERVER['HTTP_USER_AGENT'] ?? 'Unknown';
    $ip = $_SERVER['REMOTE_ADDR'] ?? 'Unknown';
    
    $logEntry = "[{$timestamp}] {$subdomain} - {$action} - IP: {$ip} - UA: {$userAgent}\n";
    file_put_contents($logFile, $logEntry, FILE_APPEND | LOCK_EX);
}

Advanced Configuration Options

SSL Certificate Configuration

Wildcard SSL Requirements: To properly secure all subdomains, you'll need a wildcard SSL certificate that covers *.yourdomain.com. Standard SSL certificates only cover specific subdomains and won't work with wildcard configurations.

SSL Implementation Steps:

1. Certificate Purchase: Obtain a wildcard SSL certificate from a certificate authority
2. Installation: Install the certificate through cPanel ? SSL/TLS ? Manage SSL Sites
3. Force HTTPS: Configure automatic redirection from HTTP to HTTPS for all subdomains
4. Verification: Test SSL functionality across multiple subdomain examples

Database Integration

Dynamic Content from Database:

// Database connection for subdomain content
function getSubdomainContent($subdomain) {
    $pdo = new PDO('mysql:host=localhost;dbname=your_database', $username, $password);
    
    $stmt = $pdo->prepare("SELECT title, content, template FROM subdomains WHERE name = ?");
    $stmt->execute([$subdomain]);
    $result = $stmt->fetch(PDO::FETCH_ASSOC);
    
    if ($result) {
        return $result;
    }
    
    return false;
}

// Usage in main handler
$content = getSubdomainContent($subdomain);
if ($content) {
    renderTemplate($content['template'], $content);
} else {
    handleUnknownSubdomain($subdomain);
}

Caching Implementation

Performance Optimization:

// Simple file-based caching
function getCachedContent($subdomain) {
    $cacheFile = "/tmp/subdomain_cache_{$subdomain}.html";
    $cacheTime = 3600; // 1 hour
    
    if (file_exists($cacheFile) && (time() - filemtime($cacheFile)) < $cacheTime) {
        return file_get_contents($cacheFile);
    }
    
    return false;
}

function setCachedContent($subdomain, $content) {
    $cacheFile = "/tmp/subdomain_cache_{$subdomain}.html";
    file_put_contents($cacheFile, $content);
}

Testing and Verification

Basic Functionality Testing

Test Subdomain Resolution:

1. Browser Testing: Visit multiple test subdomains like test.yourdomain.com, example.yourdomain.com, random123.yourdomain.com
2. Verify Response: Confirm each subdomain request is handled by your wildcard configuration
3. Check Headers: Use browser developer tools to verify proper HTTP response codes and headers

Command Line Testing: Use tools like curl or dig to test subdomain resolution:

# Test subdomain resolution
curl -I http://test.yourdomain.com

# Check DNS resolution
dig test.yourdomain.com

WordPress Multisite Testing

Site Creation Verification:

1. Create Test Site: Use the WordPress Network Admin to create a test subdomain site
2. Access Verification: Visit the new subdomain to confirm it loads the WordPress installation
3. Admin Access: Log into the subdomain's WordPress admin to verify full functionality
4. Theme and Plugin Testing: Ensure themes and plugins work correctly on subdomain sites

Error Handling Testing

Misspelling Redirection:

1. Test Common Misspellings: Visit URLs like ww.yourdomain.com, wwww.yourdomain.com
2. Verify Redirections: Confirm these redirect properly to intended destinations
3. Unknown Subdomain Handling: Test completely random subdomains to verify custom error page display

Performance Testing

Load Testing:

1. Multiple Simultaneous Requests: Test how the system handles multiple subdomain requests simultaneously
2. Database Performance: Monitor database query performance for subdomain lookups
3. Cache Effectiveness: Verify caching systems improve response times for repeated requests

Troubleshooting Common Issues

DNS Resolution Problems

Subdomain Not Resolving:

• DNS Propagation: Allow 24-48 hours for DNS changes to propagate globally
• DNS Records: Verify the wildcard DNS record (*.yourdomain.com) exists and points to correct IP
• TTL Settings: Check DNS TTL (Time To Live) settings and wait for expiration of old records

Incorrect IP Resolution:

• A Record Configuration: Confirm the wildcard A record points to your iFastNet server IP
• CNAME Conflicts: Ensure there are no conflicting CNAME records for specific subdomains
• DNS Cache: Clear local DNS cache on your computer and try again

Server Configuration Issues

404 Errors on All Subdomains:

• Document Root: Verify the wildcard subdomain document root path is correct
• File Permissions: Check that the wildcard directory and files have appropriate permissions (755 for directories, 644 for files)
• Index File: Ensure an index.php or index.html file exists in the wildcard directory

Infinite Redirect Loops:

• htaccess Rules: Review .htaccess files for conflicting redirect rules
• PHP Logic: Check subdomain detection logic for infinite redirect conditions
• SSL Configuration: Verify HTTPS redirection rules don't conflict with subdomain logic

WordPress Multisite Issues

Sites Not Creating Properly:

• Database Permissions: Verify WordPress has sufficient database permissions to create new tables
• wp-config.php Configuration: Double-check all multisite configuration constants
• Network Variables: Ensure DOMAIN_CURRENT_SITE and related variables are correctly set

Subdomain Sites Showing Main Site:

• htaccess Rules: Verify WordPress multisite .htaccess rules are properly configured
• Sunrise.php: Check if sunrise.php file is needed and properly configured
• WordPress Constants: Confirm SUBDOMAIN_INSTALL is set to true

SSL Certificate Problems

SSL Warnings on Subdomains:

• Wildcard Certificate: Verify you have a wildcard SSL certificate that covers *.yourdomain.com
• Certificate Installation: Ensure the wildcard certificate is properly installed in cPanel
• Mixed Content: Check for HTTP resources being loaded on HTTPS subdomain pages

Certificate Not Found Errors:

• Certificate Scope: Confirm your SSL certificate specifically includes wildcard coverage
• Installation Verification: Use SSL checking tools to verify certificate installation
• Certificate Chain: Ensure the complete certificate chain is properly installed

Performance and Resource Issues

Slow Subdomain Response:

• Database Queries: Optimize subdomain lookup queries and implement proper indexing
• File System Access: Minimize file system operations in subdomain detection logic
• Caching Implementation: Implement appropriate caching mechanisms for frequently accessed subdomains

Server Resource Consumption:

• Memory Usage: Monitor PHP memory usage for subdomain processing scripts
• CPU Load: Check for inefficient code that causes high CPU usage
• Disk Space: Ensure adequate disk space for subdomain content and logging

Security Considerations

Access Control and Validation

Input Sanitization: Always sanitize subdomain input to prevent security vulnerabilities:

function sanitizeSubdomain($subdomain) {
    // Remove potentially dangerous characters
    $subdomain = preg_replace('/[^a-zA-Z0-9\-]/', '', $subdomain);
    
    // Limit length to prevent abuse
    $subdomain = substr($subdomain, 0, 63);
    
    // Convert to lowercase for consistency
    $subdomain = strtolower($subdomain);
    
    return $subdomain;
}

Path Traversal Prevention: Prevent directory traversal attacks when handling subdomain-based file access:

function securePathHandling($subdomain, $requestedFile) {
    // Sanitize subdomain
    $subdomain = sanitizeSubdomain($subdomain);
    
    // Validate file path
    $allowedPath = '/public_html/wildcard/content/' . $subdomain . '/';
    $fullPath = realpath($allowedPath . $requestedFile);
    
    // Ensure path is within allowed directory
    if (strpos($fullPath, $allowedPath) !== 0) {
        return false;
    }
    
    return $fullPath;
}

Abuse Prevention

Rate Limiting: Implement rate limiting to prevent subdomain abuse:

function checkRateLimit($ip, $subdomain) {
    $cacheKey = "rate_limit_{$ip}_{$subdomain}";
    $requests = apcu_fetch($cacheKey) ?: 0;
    
    if ($requests > 100) { // 100 requests per hour
        http_response_code(429);
        echo "Rate limit exceeded";
        exit;
    }
    
    apcu_store($cacheKey, $requests + 1, 3600);
}

Subdomain Blacklisting: Maintain a blacklist of prohibited subdomains:

$blacklistedSubdomains = [
    'admin', 'administrator', 'root', 'api', 'ftp', 
    'mail', 'email', 'webmail', 'secure', 'ssl',
    'dev', 'test', 'staging', 'beta'
];

if (in_array($subdomain, $blacklistedSubdomains)) {
    http_response_code(403);
    echo "Subdomain access denied";
    exit;
}

Monitoring and Logging

Security Event Logging:

function logSecurityEvent($event, $subdomain, $ip, $details = '') {
    $logFile = '/path/to/security/wildcard-security.log';
    $timestamp = date('Y-m-d H:i:s');
    
    $logEntry = "[{$timestamp}] {$event} - Subdomain: {$subdomain} - IP: {$ip} - Details: {$details}\n";
    file_put_contents($logFile, $logEntry, FILE_APPEND | LOCK_EX);
}

// Usage examples
logSecurityEvent('BLOCKED_SUBDOMAIN', $subdomain, $_SERVER['REMOTE_ADDR'], 'Blacklisted subdomain attempt');
logSecurityEvent('RATE_LIMIT_EXCEEDED', $subdomain, $_SERVER['REMOTE_ADDR'], 'Too many requests');

Getting Support

Accessing iFastNet Support Services

Primary Support Portal:

1. Support Portal Access: Navigate to https://support.ifastnet.com/login.php
2. New User Registration: First-time support users must register for a support account by clicking the registration link and completing the required information
3. Returning User Login: Existing support users can log in directly with their established credentials
4. Support Dashboard: Access your support tickets, browse knowledge base articles, and submit new requests

Alternative Support Access:

1. Client Portal Integration: Access support through your main iFastNet client portal at https://ifastnet.com/portal/clientarea.php
2. Integrated Support: Navigate to the support section after logging into your client account
3. Unified Experience: Manage both billing and technical support from a single interface

Creating Effective Support Tickets

Wildcard Subdomain Support Categories:

• DNS and Domain Configuration: For issues with DNS records, domain settings, or subdomain resolution
• Server Configuration: For web server, Apache, or nginx configuration problems
• SSL Certificate Issues: For wildcard SSL certificate installation or configuration problems
• WordPress Multisite Support: For WordPress-specific multisite and subdomain functionality

Essential Information to Include:

Domain and Configuration Details:

• Your specific domain name and current DNS configuration
• Wildcard subdomain configuration details and document root settings
• Any custom .htaccess rules or server configuration modifications
• SSL certificate type and installation status

Problem Description:

• Specific subdomains that are not working correctly
• Complete error messages, including HTTP status codes
• Screenshots of error pages or configuration screens
• Timeline of when the issue started and any recent changes

Testing Information:

• Results of subdomain testing from different locations or devices
• DNS lookup results using tools like dig or nslookup
• Browser developer console errors or network tab information
• Curl command results showing server responses

Ticket Management Best Practices

Ticket Creation Guidelines:

1. Descriptive Titles: Use clear, specific titles like "Wildcard subdomain returning 404 errors" rather than generic titles
2. Detailed Descriptions: Provide comprehensive information about your configuration, the problem, and troubleshooting steps already attempted
3. Priority Classification: Accurately assess ticket priority based on business impact
4. Contact Preferences: Specify preferred communication methods and response time expectations

Follow-up and Communication:

• Response Monitoring: Check for support responses regularly and respond promptly to requests for additional information
• Information Updates: Provide updates if the situation changes or if you discover additional relevant information
• Resolution Confirmation: Confirm when issues are resolved and test thoroughly before closing tickets

Self-Service Resources

Documentation and Knowledge Base:

• Search Function: Use the iFastNet knowledge base search to find existing articles about subdomain configuration and troubleshooting
• Related Articles: Review related documentation about DNS management, SSL certificates, and WordPress hosting
• Video Tutorials: Look for visual guides and step-by-step video tutorials

Community and Forum Resources:

• User Communities: Participate in hosting community forums and user groups
• Best Practice Sharing: Learn from other users' experiences with wildcard subdomain implementations
• Update Notifications: Stay informed about new features, security updates, and system changes

Advanced Support Options

Professional Services: For complex wildcard subdomain implementations or custom configurations that require extensive server-level modifications, consider requesting information about iFastNet's professional services or managed configuration options.

Migration Assistance: If you're migrating existing subdomain configurations from another hosting provider, inquire about migration assistance services to ensure smooth transition of your wildcard subdomain setup.

Document Information

• Last Updated: Current as of latest cPanel subdomain management features
• Applies to: All iFastNet hosting accounts with subdomain and DNS management capabilities
• Prerequisites: Active hosting account with domain properly configured and pointing to iFastNet servers
• Related Topics: DNS management, SSL certificates, WordPress multisite, Apache configuration

This comprehensive guide provides detailed instructions for implementing wildcard subdomains on your iFastNet hosting account. For specialized requirements, advanced configurations, or enterprise-level implementations, please consult additional iFastNet documentation or contact support for personalized assistance.