• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

DNS template problem

R

renis

Guest
Hi all!

I have a problem with server dns template. After editing default template some of options are not working correctly:

This is my configuration:

<domain>. A <ip>
<domain>. MX (10) mail.<domain>.
<domain>. NS ns1.ar********ons.com.
<domain>. NS ns2.ar********ons.com.
ftp.<domain>. A <ip>
mail.<domain>. A 70.**.**.148
mssql.<domain>. A <ip>
sitebuilder.<domain>. A <ip>
stats.<domain>. A 70.**.**.147
webmail.<domain>. A 70.**.**.148
www.<domain>. A <ip>

Strangely webmail and mail subdomains does not point to IP defined, but to domain hosting IP.

Bug?

Thx!
 
you can check how your name server working using nslookup tool

c:\ nslookup webmail.<domain> localhost


If your local name server shows 70.**.**.148 then you need to check domain registration. Or wait till this changes will not be processed by root NS.
 
No, nslookup shows properly what is the current configuration for the domain. I'm using MS DNS, and also i checked the configuration there. The problem is that default configuration is not working properly with webmail and mail subdomains, but working for all the others.

I think i didn't explain very well:

At dns template i have this configuration:

mail.<domain>. A 70.**.**.148
stats.<domain>. A 70.**.**.147
webmail.<domain>. A 70.**.**.148

This works for stats but not for mail and webmail.
I don't know why, but mail and webmail continue to use old dns template configuration which was:

mail.<domain>. A <ip>
and not the new one
mail.<domain>. A 70.**.**.148

I tried removing and creating more then 3 times mail and webmail subdomains in dns template but no success.

Now for every domain created i must go to dns for that domain and fix manually webmail and mail subdomains :(
 
Can someone help me please.

Is frustating to open DNS manager for every domain and change IP of mail and webmail subdomains...
 
I too have this problem. Not only are the DNS entries not created according to the Plesk global template for newly added domains, the IP address Plesk places in the virtual root of the webmail site properties is that of the shared IP and not the webmail specific IP.

I've also noticed on several occasions the address in the webmail virtual root properties reverts to the shared ip for some domains, but I haven't been able to isolate when and /or why this happens.
 
Followup to my post above: The webmail host header is changed back to the default hosting IP address for a domain anytime a client alters the hosting options for that domain.

I take it by the lack of response there is no fix / work-around for this critical issue?

Is no one else using Horde webmail on a private IP in order to use SSL on the normal port (443)?
 
Back
Top