Facebook
Twitter
U
uscomputergroup
Guest
Ok, here's the scenario;
• Our website (uscomputergroup.com) is accessible from the internet via the FQDN or the IP of 71.98.254.108 and is properly registered with our registrar with ns1.uscomputergroup.com and ns2.uscomputergroup.com as the name servers.
• The name servers are registered as 71.98.254.108 and there are proper DNS A record entries for ns1 and ns2 at the domain.
• We have a SonicFirewall handling traffic on this IP address (71.98.254.108) and all neccessary web traffic is being forwarded to a DMZ (10.X.X.X) where the Plesk server resides.
• The network interface of the Plesk server has an IP address of 10.X.X.X
• uscomputergroup.com is being physically hosted by Plesk on this IP but all DNS entries resolve to the public IP address (71.98.254.108) as required to be accessible from the internet.
• checkdns.net successfully resolves all connection attempts including e-mail for uscomputergroup.com.
• All of the POP e-mail boxes are working properly and we can send/receive e-mail to and from anywhere.
Here's the problem;
1. When running the mail() function in PHP, sending an e-mail to info@uscomputergroup.com results in the following error;
Is this because DNS resolves the domain (uscomputergroup.com) to the public IP address (71.98.254.108) and therefore assumes that it is "not local" since the physical IP address of the server is actually 10.X.X.X?
2. When creating a domain in Plesk, the default DNS entries are created using the physical IP on which it is hosted (10.X.X.X). However, these entries must resolve to the public IP address (71.98.254.108) in order to be accessible from the internet. Therefore, we must either;
A. Manually input each DNS entry with the correct public IP address for the domain.
B. Change the server default DNS entries to the public static IP address.
Solution A. is not ideal for clients as this forces clients to manually edit thier DNS entries! Solution B. is not ideal as this forces all sites to use the same public IP address and does not allow a domain to have a dedicated IP address!
If anyone has any ideas as how to resolve these issues, please respond and/or contact me. Thanks for your time and help!
• Our website (uscomputergroup.com) is accessible from the internet via the FQDN or the IP of 71.98.254.108 and is properly registered with our registrar with ns1.uscomputergroup.com and ns2.uscomputergroup.com as the name servers.
• The name servers are registered as 71.98.254.108 and there are proper DNS A record entries for ns1 and ns2 at the domain.
• We have a SonicFirewall handling traffic on this IP address (71.98.254.108) and all neccessary web traffic is being forwarded to a DMZ (10.X.X.X) where the Plesk server resides.
• The network interface of the Plesk server has an IP address of 10.X.X.X
• uscomputergroup.com is being physically hosted by Plesk on this IP but all DNS entries resolve to the public IP address (71.98.254.108) as required to be accessible from the internet.
• checkdns.net successfully resolves all connection attempts including e-mail for uscomputergroup.com.
• All of the POP e-mail boxes are working properly and we can send/receive e-mail to and from anywhere.
Here's the problem;
1. When running the mail() function in PHP, sending an e-mail to info@uscomputergroup.com results in the following error;
Is this because DNS resolves the domain (uscomputergroup.com) to the public IP address (71.98.254.108) and therefore assumes that it is "not local" since the physical IP address of the server is actually 10.X.X.X?
2. When creating a domain in Plesk, the default DNS entries are created using the physical IP on which it is hosted (10.X.X.X). However, these entries must resolve to the public IP address (71.98.254.108) in order to be accessible from the internet. Therefore, we must either;
A. Manually input each DNS entry with the correct public IP address for the domain.
B. Change the server default DNS entries to the public static IP address.
Solution A. is not ideal for clients as this forces clients to manually edit thier DNS entries! Solution B. is not ideal as this forces all sites to use the same public IP address and does not allow a domain to have a dedicated IP address!
If anyone has any ideas as how to resolve these issues, please respond and/or contact me. Thanks for your time and help!
I don't blame you!
