web site maintenance personnel structure? Best practice?
I'm trying to get a feel for how things are handled these days when dealing with your company domain(s).
-Registrations .
-DNS entries/updates/changes from Control Mgmt Consoles like cpanel and perske.
In particular changes to A or MX records.
IP changes, possibly to combat an issue you get/request a dedicated different IP.
DNS entries on your server in DNS mgr to update IPS or add subdomains(our clients).
Scenario
Our company domain is companydomain.com
Our email exchange is name@companydomain.com
We provide eCommerce sites to customer and it's cust1.companydomian.com and cust2.companydomian.com.
So how does the IT vs Web Master/Person split the tasks. Who is driving which thing. Is the webmaster limited to not have access to hosted cpanels, which they need to update client DNS entries for new sites, but where they can potentially change or forget to do a(our company) MX record change that causes IT internal issue.
Not sure did a great job describing concerns/what I'm trying to get feedback on best practice on but, well see based on relies...
Thx
-Registrations .
-DNS entries/updates/changes from Control Mgmt Consoles like cpanel and perske.
In particular changes to A or MX records.
IP changes, possibly to combat an issue you get/request a dedicated different IP.
DNS entries on your server in DNS mgr to update IPS or add subdomains(our clients).
Scenario
Our company domain is companydomain.com
Our email exchange is name@companydomain.com
We provide eCommerce sites to customer and it's cust1.companydomian.com and cust2.companydomian.com.
So how does the IT vs Web Master/Person split the tasks. Who is driving which thing. Is the webmaster limited to not have access to hosted cpanels, which they need to update client DNS entries for new sites, but where they can potentially change or forget to do a(our company) MX record change that causes IT internal issue.
Not sure did a great job describing concerns/what I'm trying to get feedback on best practice on but, well see based on relies...
Thx
ASKER
it's a webmaster(lightly termed) that does the company and customer sites.
makes mistakes int he external DNS of sites that causes IT issues when company things stop working like email.
So trying to figure out how to revamp the procedure and get insight on how others deal with this type of setup. ie outside employee that has does webstuff has access to external DNS managers that has to but half the time doesn't get DNS and causing company sites and email to stop working when something is changed incorrectly or without warning.
Thx
makes mistakes int he external DNS of sites that causes IT issues when company things stop working like email.
So trying to figure out how to revamp the procedure and get insight on how others deal with this type of setup. ie outside employee that has does webstuff has access to external DNS managers that has to but half the time doesn't get DNS and causing company sites and email to stop working when something is changed incorrectly or without warning.
Thx
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
>but where they can potentially change or forget
This sounds like something that could be automated. When a new client comes on, what tasks can be automated as far as a script that will take care of the dns, subdomains etc. ?
Do you have a policy now of who does what? or is it just who has the time?