AntiRelayd...Please Help!!!

[cpanelkenneth]

Let me rephrase my statement:

This feature is enabled by default.

Should be:

This feature is enabled by default in Tweak Settings.

Meaning: this feature is only enabled if you go into Tweak Settings after the upgrade to 11.23 and save the Tweak Settings without unticking the boxes for the Proxy access feature.

If no subdomain exists for a webmail A record (or cpanel, whm, etc) that record will be over-written.

[dwykofka]

Is this going to be addressed?

We have a dns cluster with thousands of named records. I would estimate that almost 20% of them have custom DNS entries. Losing all the custom entries would be devisating for our company and many others.

[jdlightsey]

The only A records that get changed are the cpanel/whm/webdisk/webmail subdomains for the primary domain of each account.

They are only changed when no subdomain of the same name has already been created in cPanel. The only way this might cause a problem is if you went in and manually added one of these same subdomains to the DNS zone instead of using cPanel to create it as a proper subdomain.

So....If you did some manual zone manipulation to add webmail/webdisk/whm/cpanel subdomains before this feature was available you can (a) allow the new proxydomains to overwrite those DNS entries and use the new system, (b) add those subdomains in cPanel so they won't get overwritten and add your custom redirects back on the new subdomains, or (c) go into TweakSettings make sure proxydomains are turned off and save.

[dwykofka]

Example:
I edited /var/named/domaina.com.db
I added an A Record called "Exchange"
I saved the file and reloaded named

When the proxydns script runs will exchange.domaina.com disapear?

[jdlightsey]

It should not disappear.

The only scenario where the A record might change would be...

Before cPanel 11.23:

- Add an account domain.com
- Go into DNS zone editor and add webmail.domain.com pointing to a different IP address than domain.com
- Upgrade to 11.23
- Turn on ProxyDomains in tweaksettings


In this scenario the IP address for webmail.domain.com will change to match domain.com's and if you go to http://webmail.domain.com you should get a login for the webmail interface.

If you find that the proxy domains changes are altering any subdomain A records other than cpanel/webmail/whm/webdisk, it probably indicates some other problem is at work.

[gegervision]

The WHM update fixed the /etc/alwaysrelay issue with the Release Build.

Thanks cPanel.

[hbouma]

Let me rephrase my statement:

This feature is enabled by default.

Should be:

This feature is enabled by default in Tweak Settings.

Meaning: this feature is only enabled if you go into Tweak Settings after the upgrade to 11.23 and save the Tweak Settings without unticking the boxes for the Proxy access feature.

If no subdomain exists for a webmail A record (or cpanel, whm, etc) that record will be over-written.

Why are we once again setting new features to enabled for existing installs? All this does is break expected behavior with your customers. New features should always be set to off by default and when the customer is ready for them, they can turn it on.

[added] More about what I mean is that the tweak settings page is getting pretty large these days with a ton of settings. Its no longer easy to tell when there is a new setting on the page and simply having a few tiny **'s on the line doesn't really catch one's eye expecially if someone is trying to make a quick change in tweak settings. If you're going to force new settings to be enabled by default on the user, you should do a much better job of conveying that once they save the page, this will have a major change on its configuration. If you were to color code the setting based on its impact (such as red for the proxy), or put up a notice saying there are new settings and what they do to make sure they're properly set before saving, that may help prevent people from making unintended changes to their settings.

I still think that the best solution is new settings should only be set to on when the user actually goes and turns it on though.

Hal

[SageBrian]

I can longer get AntiRelayd to restart and it will NOT write my alwaysrelay hosts file to relayhosts.

I just recently had this issue after upgrading to Current, but just on one of my servers.

For some reason, IPs were not being written to the relayhosts file anymore. Or relayhostsusers.

Even after resetting Exim Config using default ACLs, still had a problem. Authenticated users were not being logged.

Eventually, I went to Service Manager and though tailwatchd was enabled, I also turned on 'monitor' for it. Save, and poof, IPs are being logged again.

I'm not sure what fixed it, what caused the issue in the first place (besides updating), but all is good now.

Brian