Last post Feb 26, 2009 11:31 PM by Mainship
Feb 25, 2009 10:03 AM|Mainship|LINK
I have a new customer, a small airline with agents with 4 remote offices. They use Exchange for their email. The website is next to useless, and I've been hired to develop a new one. The new site will accept reservations online.
The website is currently hosted by GoDaddy, in a shared hosting account controlled by their tech guy. This guy has full and total control over their network, and if you need him, it generally takes a while to get a response.
The plan was to move the website to a shared account with another host. As we implement new phases, we'll add band width and disk space, and eventually move to a virtual dedicated server. Since I would have control over this account, I could make the changes
as I need them like a new email address for email sent from ther site, and not wait for this guy. It would also give me remote access to the database which I don't have now.
I asked him to change the DNS servers and he flipped. In his words:
This will severely cripple the network and email functionality we have.
This is not a rinky dink network.
We are configured as an enterprise class network with many entities utilizing DNS.
If we move the DNS we will in essence lose email that goes into our Exchange server and our 4 remote offices will not be able to communicate with the corporate
So my question is, how necessary is exchange server for email? Is it really that much better than using regular email?
Feb 25, 2009 10:27 AM|rtpHarry|LINK
Hey, you dont have to change the entire dns over to you for you to host a website in a separate place than exchange
You need to find out how to add an external domain with your web host, this will get the domain name recognised in your hosting account.
Then you need to get the pc guy to change the "A record" to point to the ip of your webserver - the webhost will provide details for this when you setup the external domain.
He is correct that moving the dns away would destroy the functionality of his entire network!
As for setting up emails etc you will still have to do that through him or alternatively use a different mail server. Some of our clients websites use our mail server to send the email out.
As long as you have provided a username and a password to a mail server they dont usually care about what domain you set in the "from" field so you can pretend to send emails that look like @yourclientsdomain.co.uk
There is a small issue of spam in that you might have to get the dns admin to setup spf records etc but that is an advanced topic - one step at a time! :)
Feb 25, 2009 01:55 PM|Mainship|LINK
Hmmm... I don't fully follow you. I'm also not sure I was clear.
The domain is currently on a GoDaddy shared hosting account. The tech guy owns the account, and I don't have access. Godaddy requires a username and password in the web.config file to send email from the website. I've been waiting nearly a month for that
new email address, I'm not going to ask one of the staff to give me their credentials.
I don't have remote access to the database. I can't set up or modify tables except through code, and I can't easily go in to see the data when testing code. They want the work done by Friday!
I want to move the domain to a new host, where I can go in to add a new email address, have remote access to the database, and other things that will be coming up. As the project progrsses, we'll move to a virtual dedicated account.
He says he has other domains - he offered one to test with - can't he use one of those DNS's? I'm not trying to be cute, I'm trying to understand.
Or, are you saying we can move the website to the new host while keeping the DNS where it is? I can use the new host's email server to send emails, and I can use their database.
Feb 25, 2009 03:46 PM|rtpHarry|LINK
Why he cant move it
When you have an a domain like example.com you have DNS records for it. The DNS records are pulled up when a request comes in and depending on what they say you are forwarded on to a computer ip.
The DNS is split up into slices of different services.
The web server is pointed at one computer in the form of an A record.
The mail server is pointed at the ip of the exchange server in the form of an MX record.
Depending on the services such as SharePoint or if they have a MS SBS (Small Business Server) in the network there will be other records inside the DNS records.
If he was to assign another authority of the DNS records (ie when you asked him to change the DNS servers to your new webhost) then all this information would be lost.
Why he cant just use a different domains DNS
The various pieces of software that he has running across this network will have references to the domain such as mail.example.com or server.example.com etc etc it would be a big task for him to change them and then he wouldnt be able to collect mail from
firstname.lastname@example.org because the mx wouldnt be pointing at his mail server any more. Its not a reasonable request to make of him.
A possible solution
It is possible for him to point the A record for the web traffic at a different IP such as your own hosting. This means that the computer that you are redirected to when you ask for a webpage from example.com would be your hosting but the rest of the computers
you are redirected to when you ask for the small busines server or the mail server would still be in his control.
If you did this and the web (and ftp records) of the domain are now pointing at your web host then you will be able to act as though you hosted the site normally, it wouldnt matter that some of the other services were not being provided by your webhost.
The database server is usually provided with its own ip, or instance name, or domain name which isnt affected by the example.com. Its just the address of the database server, so you would be ok there.
Sending the email
Depending on your web host you should also be able to connect to their email server and send emails out using asp.net code. You are free to pretend you are sending email from email@example.com if you want as email is not a secure medium in that way. What
I am saying is that if you wanted to send your emails out as firstname.lastname@example.org then you will not have a problem doing this.
In fact you can use any email server you have an account on. If you had an email account for example email@example.com and you had the server address and the password you could connect to this mail server with these details in your .net and then just
set the from address as firstname.lastname@example.org and send it out as if email@example.com had sent it. This is what I meant when I mentioned email in my last post, I didnt mean you should ask for an employees details at the airline.
Hope this has cleared a few things up, if I can be of any help with the configuration I will give you a hand to set it up, just give me a shout!
Feb 25, 2009 08:10 PM|Danny117|LINK
Exchange is email.
Feb 26, 2009 11:31 PM|Mainship|LINK
Thank you. I spoke the the tech guy, and this is just what we did.