1 |
On 29/09/2015 22:00, Tanstaafl wrote: |
2 |
> Hi all, |
3 |
> |
4 |
> I am not a web (or SEO) guy, but I manage our DNS and have for a long time. |
5 |
> |
6 |
> The boss has contracted with a web development company to do a full |
7 |
> redesign of our website. |
8 |
> |
9 |
> Our website has hundreds of thousands of pages, and years of SEO behind |
10 |
> it. The guys who was her until recently was adamant that we must be very |
11 |
> carefl with the redesign so as not to totally break SEO, and possibly |
12 |
> getting blacklisted by Google. |
13 |
> |
14 |
> The web developers are insisting that they need full access to our DNS |
15 |
> (hosted by DNSMadeEasy), and the only reason I can think of for this is |
16 |
> they plan on setting up HTTP redirects (DNSMadeEasy equivalent of a 301 |
17 |
> redirect) for these pages - but hundreds of thousands of them? |
18 |
|
19 |
I've been thinking about this some more. |
20 |
|
21 |
We all assumed "full access" means "so we can change stuff". Maybe it |
22 |
really means they want to see what's in "dig axfr" (a zone transfer) |
23 |
which they normally can't see. There are TXT records in DNS that they |
24 |
might be interested in. |
25 |
|
26 |
It would be wise to clarify with the devs exactly what it is they are |
27 |
looking for. |
28 |
|
29 |
And overall, in your shoes I would be firm, adamant and above all polite |
30 |
and say that infrastructure changes go through you and you alone, and |
31 |
must be vetted by you with full transparency. |
32 |
|
33 |
|
34 |
|
35 |
> |
36 |
> Wouldn't this be better done at the web server level? Or am I just ignorant? |
37 |
> |
38 |
> Would love to hear experiences (good and bad), and a recommendation for |
39 |
> what I should do. |
40 |
> |
41 |
> thanks |
42 |
> |
43 |
|
44 |
|
45 |
-- |
46 |
Alan McKinnon |
47 |
alan.mckinnon@×××××.com |