Warnings related to the subdomain, such as issues with the serverĬonfiguration, web server software, or application code. Review the server logs: Check the server logs for any errors or.To see if the issue is related to DNS resolution or the server Test the connection to the subdomain's IP address directly: TryĪccessing the subdomain using its IP address ( ).Use a DNS propagation checker tool to verify if the A record for the.If you've verified these points and still encounter issues, you can try the following: Staging subdomain that might be preventing incoming traffic. Or network configuration issues on the Plesk server hosting the Firewall or network configuration: Check if there are any firewall.Ensure theĭomain is added to the Plesk server, and the document root isĬorrectly pointing to the subdomain's files. ![]() Properly configured to serve the staging subdomain. Check the Plesk server configuration: Make sure the Plesk server is.Settings for both the main domain and subdomain to ensure there are Verify the domain and subdomain DNS settings: Double-check the DNS I followed the Plesk instructions of creating new glue records / hostnames Originally I tried to do .uk -> IP.Seconds or 12 hours), it may take longer for the changes to Record for the subdomain .uk is pointing to theĬorrect IP address (50.221.77.68) and has a reasonable TTL value Double-check the A record on the parent domain DNS: Ensure the A.If you've recently made changes, you may need to wait for Propagate, depending on the Time to Live (TTL) value set in your DNS It can take up to 24-48 hours for the changes to fully Propagation time: DNS changes may take time to propagate across the.However, there are a couple of things to double-check and consider: It appears that the DNS configuration is mostly correct. I have looked at this question as well as this Plesk article but I am unclear as to if this plesk article should be applied as we only need to do this for one single subdomain one one single domain.īut the address .uk does not reach the intended destination. Aside from the record added, they're all the "default" Plesk records when the domains were set up.Īdded record to the parent: .uk. This is the full set of records in Plesk. TXT v=DKIM1 p=DKIM1 p=DKIM1 p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKMQsEj2LT6DcNhGhqMG/q8Rv+aymZvUoMOJcAF6bYOMQSzzggDmBfwuINbLeF/iCWYXnZoXWcVf71kcY7B8cQsWc6VfiDNIGmKR9w/gxc7mz5MSliz4c/mjQIDAQAB ![]() TXT v=DMARC1 p=quarantine adkim=r aspf=r pct=100 sp=reject Subdomain DNS on seperate server ( 50.221.77.68 ) _.uk. The final line is the only line we have added to the parent DNS records. TXT v=DKIM1 p=DKIM1 p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiDmBfwuINbLeF/iCWYXnZoXWcVf71kcY7B8cQsWc6VfiDNIGmKR9w/gxc7mz5MSliz4c/mjQIDAQAB TXT v=DMARC1 p=quarantine adkim=r aspf=r pct=100 sp=reject ĭ.uk. I have done these subdomain redirections on WHM many times without fail and all works well, simply by adding the A record for the subdomain and entering the residing IP address, however for some reason the Plesk method is lacking. ![]() This is a different server on a different IP address. We have a new PlesK Obsidian server specifically for holding a specific subdomain of the main domain. We have a Plesk server with the parent Domain, the Plesk main domain runs fine.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |