Ask Question Forum:
Model Library:2025-02-08:A.I. model is online auto reply
C
O
M
P
U
T
E
R
2
8
Show
#
ASK
RECENT
←
- Underline
- Bold
- Italic
- Indent
- Step
- Bullet
- Quote
- Cut
- Copy
- Paste
- Table
- Spelling
- Find & Replace
- Undo
- Redo
- Link
- Attach
- Clear
- Code
Below area will not be traslated by Google,you can input code or other languages
Hint:If find spelling error, You need to correct it,1 by 1 or ignore it (code area won't be checked).
X-position of the mouse cursor
Y-position of the mouse cursor
Y-position of the mouse cursor
Testcursor
caretPos
Attachment:===
Asked by pmitllc
at 2024-07-27 20:10:37
ModifyPoint:500 Replies:9 POST_ID:828620USER_ID:11478
Topic:
Domain Name Service (DNS);Miscellaneous Web Development;Email Servers
I want to verify the changes I plan to make and also see if there is anything else I should look out for.
Currently we have a domain hosted with company A with the nameservers pointing to our telecom company which is hosting our website.
Our MX records point to Google as we have Google Apps for Business.
We want to move off of the telecom's hosting and to another host.
We contacted the website designer who setup hosting with company B and created a copy of the website. He said "The server's IP address is xx.xx.xx.xx. I believe once that is updated in the site's A record, it will be live at the new host.".
This is what I was planning on doing:
Lookup the current MX records for our domain and replace the current MX records on the DNS settings page for Company B
Add the TXT record that Google Apps requires for verification to the DNS Settings page for Company B
Login to the domain registrar and change the name servers to Company B's nameservers.
Is that all?
Currently we have a domain hosted with company A with the nameservers pointing to our telecom company which is hosting our website.
Our MX records point to Google as we have Google Apps for Business.
We want to move off of the telecom's hosting and to another host.
We contacted the website designer who setup hosting with company B and created a copy of the website. He said "The server's IP address is xx.xx.xx.xx. I believe once that is updated in the site's A record, it will be live at the new host.".
This is what I was planning on doing:
Lookup the current MX records for our domain and replace the current MX records on the DNS settings page for Company B
Add the TXT record that Google Apps requires for verification to the DNS Settings page for Company B
Login to the domain registrar and change the name servers to Company B's nameservers.
Is that all?
Expert: Scott Fell (padas) replied at 2024-07-28 09:53:51
Friday is good. Friday late afternoon or evening is typically when I make my dns changes when email is involved. I see web traffic propagate almost instantly at least within the U.S. and email takes about an hour or 2 at the most. Of course there is always the little message in fine print when you do make changes that it can take up to 72hrs. I have not seen 72 hrs since 1999. And at least the last few years changing www traffic seems to work within minutes.
Author: pmitllc replied at 2024-07-28 09:47:47
I see your point of doing it that way and it will make sense in our case since our domain is registered for 10 years, and hosting is only 5 years. Duncanb7's solutions seems like it would also work and would be better if the terms were the other way around.
I'm going to wait until Friday when closed to make the changes.
I appreciate the help.
I'm going to wait until Friday when closed to make the changes.
I appreciate the help.
Accepted Solution
Expert: Scott Fell (padas) replied at 2024-07-28 08:39:53
325 points EXCELLENT
Sorry for the confusion.
>Currently we have a domain hosted with company A with the nameservers pointing to our telecom company which is hosting our website.
What I am suggesting is not to point your nameservers anywhere (parked"). Manage your DNS through your registrar.
Let's assume your registrar is godaddy. You have your current hosting at telecom1 and your new host is WebHostCompany2 and either way your mail will always be with Google.
When it is time to change, update godaddy so the nameservers are no longer pointing anywhere, they use the term, "parked".
Step 1) "park" your name server
Step 2) Point the "a" record to the IP of WebHostCompany2
Step 3) Point your "mx" records to Google along with their recommended spf and dkim text records.
Now your good. It is always better to manage your dns through your registrar. Larger organizations will go a step farther and manage DNS separately. For most small sites, what I have suggested is fine.
This way, if something happens to the website or WebHostCompany2, your email will always work via google (provided you are up to date on the domain name expiration date). Or, maybe in a few years you change your web host again, now all you need to do is change the "a" record and never touch your mx records.
>Currently we have a domain hosted with company A with the nameservers pointing to our telecom company which is hosting our website.
What I am suggesting is not to point your nameservers anywhere (parked"). Manage your DNS through your registrar.
Let's assume your registrar is godaddy. You have your current hosting at telecom1 and your new host is WebHostCompany2 and either way your mail will always be with Google.
When it is time to change, update godaddy so the nameservers are no longer pointing anywhere, they use the term, "parked".
Step 1) "park" your name server
Step 2) Point the "a" record to the IP of WebHostCompany2
Step 3) Point your "mx" records to Google along with their recommended spf and dkim text records.
Now your good. It is always better to manage your dns through your registrar. Larger organizations will go a step farther and manage DNS separately. For most small sites, what I have suggested is fine.
This way, if something happens to the website or WebHostCompany2, your email will always work via google (provided you are up to date on the domain name expiration date). Or, maybe in a few years you change your web host again, now all you need to do is change the "a" record and never touch your mx records.
Expert: duncanb7 replied at 2024-07-28 08:34:32
First,
you login name and password to login your domain registrar, right ?
Second,
You already have hosting service from hosting company B, Right?
what is nameserver for hosting company B they give you ,
ns1.hostingB.com and ns1.hostingB.com
Please tell us more besides(password and login)
you login name and password to login your domain registrar, right ?
Second,
You already have hosting service from hosting company B, Right?
what is nameserver for hosting company B they give you ,
ns1.hostingB.com and ns1.hostingB.com
Please tell us more besides(password and login)
Author: pmitllc replied at 2024-07-28 08:25:35
I'm confused as what I should do......duncanb7 told me to just change the nameservers and company B and it will take care of moving the rest of the records.
padas told me he agrees with duncanb7, then told me to do something different (Host the DNS with Company A and put all of the records there and change the "a" record ip).
So who should I follow? do I move the DNS to the new host (Company B) or move it to the current registrar (Company A)? or would both work and it is a matter of preference?
padas told me he agrees with duncanb7, then told me to do something different (Host the DNS with Company A and put all of the records there and change the "a" record ip).
So who should I follow? do I move the DNS to the new host (Company B) or move it to the current registrar (Company A)? or would both work and it is a matter of preference?
Expert: Scott Fell (padas) replied at 2024-07-28 00:21:58
I agree with duncanb7, as long as you are making a change, host the dns with your registrar (godaddy, networksolutions et el). Set your mx records, a, cname's all with the dns hosting at the registrar and the next time you make a move, you just need to change the "a" record ip.
Remember for google apps you also want to update your spf and dkim in addition to your mx records.
Remember for google apps you also want to update your spf and dkim in addition to your mx records.
Assisted Solution
Expert: duncanb7 replied at 2024-07-27 23:53:14
175 points EXCELLENT
Hosting company B will do that for you and they will
also transfter all your domain zone file to your new server so that
you don't need to involve any MX, CNAME, named.conf, zone file stuff.
If current domain names is NOT kept by hosting B company,
your need to login into admin page at your domain registrar company and change
domain nameserver setting that point to hosting B's names
server provided to you, for example, ns1.hostingB.com ns2.hostingB.com
After 24 hours, propagation delay of your domain name transfer through
world wide, you will power your website correctly on browser under
hosting company B server.
also transfter all your domain zone file to your new server so that
you don't need to involve any MX, CNAME, named.conf, zone file stuff.
If current domain names is NOT kept by hosting B company,
your need to login into admin page at your domain registrar company and change
domain nameserver setting that point to hosting B's names
server provided to you, for example, ns1.hostingB.com ns2.hostingB.com
After 24 hours, propagation delay of your domain name transfer through
world wide, you will power your website correctly on browser under
hosting company B server.
Author: pmitllc replied at 2024-07-27 21:16:09
It looks like the telecom does it, because if I go to the DNS settings page it tells me I need to first move the name servers over to them.
Expert: gmrstudios2013 replied at 2024-07-27 21:10:47
So does company A host your DNS? Or does the telecom company host both your website and your DNS?
