Help
hi,
can someone help me out about the nameserver thingy....as in what should be the nameserver for my website....
eg: if website is www.abc.com should i change its nameserver or should i keep it d way the hosting co. gave it to me...eg: server1.godaddy.com
and whats the advantages and disadvantages if i change the nameserver to my domain or if i keep it with the hosting co.
hoping to see some replies soon
thanks in advance
Page 1 of 1
what should be the namer server for my website
#2
simplypixie 
- Forum Newcomer
-
- Group: Members
- Posts: 62
- Joined: 23-November 11
- Reputation: 11
- Gender:Female
- Location:Shropshire
- Experience:Intermediate
- Area of Expertise:Web Developer
Posted 17 December 2011 - 07:25 AM
You can't change your name servers. They tell the web where your website and emails are hosted so if you host on GoDaddy and they are the name servers that have been allocated then don't change them or everything will die.
If you want to move your hosting to a new hosting company then that is when you would change your name servers to be the ones for your new hosting package.
If you want to move your hosting to a new hosting company then that is when you would change your name servers to be the ones for your new hosting package.
#3
sclarke
- Forum Newcomer
-
- Group: Members
- Posts: 27
- Joined: 03-January 12
- Reputation: 1
- Gender:Male
- Experience:Intermediate
- Area of Expertise:Web Developer
Posted 11 January 2012 - 02:30 PM
The nameservers point to your website, they aren't there just for fun to rename, they are what tell your website visitors where to go to find the website.
#4
AdvantageDigitalMedia
- Forum Newcomer
-
- Group: Gold Membership
- Posts: 21
- Joined: 31-January 12
- Reputation: 1
Posted 31 January 2012 - 09:11 AM
Nameservers are crucial to the correct operation of your website.
They should be left well alone if you're not sure what they do.
For reference however, they usually point to wherever your domain is hosted, which can be completely different from where your website is hosted, it's important to distinguish the difference. You can have your website hosted with 123-reg for instance, but a domain with fasthosts meaning your nameservers will be something like ns1.fasthosts.co.uk and ns2.fasthosts.co.uk or whatever they are.
It then gives control to the DNS zone of that domain to the nameserver owner, in this example fasthosts. Depending on your hosting environment you may see DNS zones for your domain on the hosting platform, but unless they nameservers are pointing there it's irrelevant. All DNS zone control is with fasthosts, so any changes to MX and A records etc would need to be done there.
My initial thoughts are that asking a question like this means you're not experienced in DNS management and should not make any changes unless you're sure what they do, as it will leave you with an inoperable site.
It's also worth baring in mind that DNS changes can take up to 24hrs to propogate worldwide so any changes you do make can take 24hrs to "go wrong" worldwide but more important up to 24hrs to put right worldwide. Worst case scenario is you lose your site for 2 days!
Good luck and take care.
They should be left well alone if you're not sure what they do.
For reference however, they usually point to wherever your domain is hosted, which can be completely different from where your website is hosted, it's important to distinguish the difference. You can have your website hosted with 123-reg for instance, but a domain with fasthosts meaning your nameservers will be something like ns1.fasthosts.co.uk and ns2.fasthosts.co.uk or whatever they are.
It then gives control to the DNS zone of that domain to the nameserver owner, in this example fasthosts. Depending on your hosting environment you may see DNS zones for your domain on the hosting platform, but unless they nameservers are pointing there it's irrelevant. All DNS zone control is with fasthosts, so any changes to MX and A records etc would need to be done there.
My initial thoughts are that asking a question like this means you're not experienced in DNS management and should not make any changes unless you're sure what they do, as it will leave you with an inoperable site.
It's also worth baring in mind that DNS changes can take up to 24hrs to propogate worldwide so any changes you do make can take 24hrs to "go wrong" worldwide but more important up to 24hrs to put right worldwide. Worst case scenario is you lose your site for 2 days!
Good luck and take care.
#5
zed
- Web Guru
-
- Group: Moderators
- Posts: 4,941
- Joined: 25-May 10
- Reputation: 703
- Gender:Male
- Experience:Intermediate
- Area of Expertise:Designer/Coder
Posted 31 January 2012 - 09:19 AM
AdvantageDigitalMedia, on 31 January 2012 - 09:11 AM, said:
It's also worth baring in mind that DNS changes can take up to 24hrs to propogate worldwide so any changes you do make can take 24hrs to "go wrong" worldwide but more important up to 24hrs to put right worldwide. Worst case scenario is you lose your site for 2 days!
why would you lose the site for 2 days. If it's already pointed to one server and is being propogated to another then won't it be up....somewhere?
#6
AdvantageDigitalMedia
- Forum Newcomer
-
- Group: Gold Membership
- Posts: 21
- Joined: 31-January 12
- Reputation: 1
Posted 31 January 2012 - 09:26 AM
zed, on 31 January 2012 - 09:19 AM, said:
why would you lose the site for 2 days. If it's already pointed to one server and is being propogated to another then won't it be up....somewhere?
Because, as he suggested he might do, he changes his nameservers to something that don't exists and looks pretty, then there's no DNS being served at all?
Share this topic:
Page 1 of 1