On 29/09/2015 22:00, Tanstaafl wrote: > Hi all, > > I am not a web (or SEO) guy, but I manage our DNS and have for a long time. > > The boss has contracted with a web development company to do a full > redesign of our website. > > Our website has hundreds of thousands of pages, and years of SEO behind > it. The guys who was her until recently was adamant that we must be very > carefl with the redesign so as not to totally break SEO, and possibly > getting blacklisted by Google. > > The web developers are insisting that they need full access to our DNS > (hosted by DNSMadeEasy), and the only reason I can think of for this is > they plan on setting up HTTP redirects (DNSMadeEasy equivalent of a 301 > redirect) for these pages - but hundreds of thousands of them?
I've been thinking about this some more. We all assumed "full access" means "so we can change stuff". Maybe it really means they want to see what's in "dig axfr" (a zone transfer) which they normally can't see. There are TXT records in DNS that they might be interested in. It would be wise to clarify with the devs exactly what it is they are looking for. 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. > > Wouldn't this be better done at the web server level? Or am I just ignorant? > > Would love to hear experiences (good and bad), and a recommendation for > what I should do. > > thanks > -- Alan McKinnon alan.mckin...@gmail.com
