Thanks Alan (and everyone else), One important follow-up below...
On 9/29/2015 8:28 PM, Alan McKinnon <alan.mckin...@gmail.com> wrote: > It would be wise to clarify with the devs exactly what it is they are > looking for. That is the purpose of my upcoming phone call with him. > And overall, in your shoes I would be firm, adamant and above all polite > and say that infrastructure changes go through you and you alone, and > must be vetted by you with full transparency. That is what I've been doing so far, but I think the boss is getting close to just saying 'give it to them'... But - no one has addressed my main question... I understand that 301 redirects are performed by web servers only, you can't really do these in DNS. However, some Managed DNS providers - DNSMadeEasy included - offer this ability as a service. DNSMadeEasy calls them 'http redirects', and the actual redirect is accomplished by one of their own web servers they have set up to handle these. Is it 'normal' to do these 301 redirects at the DNS level like that? I would think they should be using the current web server hosting the current site to start doing the redirects as they get the new landing pages done? Apache does this using a .htaccess file (if I'm interpreting my googling responses correctly). And now that I worded it that way - how would they do that exactly? Would the proper method be to redirect it to a new test domain, ie: www.example.com/page1.htm >> www.new-example.com/newpage1.htm ? Or save the new page on the old server, then do: www.example.com/page1.htm >> www.example.com/newpage1.htm ? Now I'm confusing myself...
