New answers tagged cname-record
What you probably want to do is create an NS record. Not a CNAME. NS subdomain.domain.com. ns1.nameserver.com. Then on your subdomains nameserver (could be the same nameserver): create a zonefile for subdomain.domain.com with the necessary and appropriate bindings. NS subdomain.domain.com. ns1.nameserver.com. A subdomain.domain.com. 220.127.116.11 MX ...
Of course it is possible to redirect, with the following trick: Create a new standard primary zone Name it same as the fictive URL that you want to redirect to Ensure that this fictive name is different than any AD DNS name Create A record with following entries: blank.......................A............................ip-addr-2 ...
One of the many many many reasons you don't use the same domain internally. If you can, create another site with the specific host example.com, and do a 301 redirect to www. 301 is cached so it won't always hit the server either.
Web redirection has nothing to do with email routing, so this part you can ignore. It is 100% sure that 301 redirect has no impact on email communication. It is for HTTP protocol, http://en.wikipedia.org/wiki/HTTP_301. The most important thing is proper DNS configuration. If you want mails addressed to yourdomain.pro domain to be accepted by ...
In my opinion MX DNS config is OK since you already got an answer from SMTP server: 450 4.1.8 <myEmail@example.pro>: Sender address rejected: Domain not found I would focus on SMTP configuration: Try allowing MTA to process messages from any domain.
Top 50 recent answers are included