2 Improved Formating, Spelling and Grammar
source | link

I notice that, with most of the webhostsweb hosts I use, they provide nameserver addresses under their main domain (or a related domain). 

For example, Mediatemple provides nameserversname servers which are ns1.mediatemple.net and ns2.mediatemple.net:

  1. ns1.mediatemple.net
  2. ns2.mediatemple.net

So, when I setup a website on their servers, under a domain like myserver.com,myserver.com the nameservers are not under that domain.

When I was setting up with a new host for another site, they setup nameservers under the domain of the site I was setting up. So, the website I was installing was myserver.commyserver.com, they setup nameservers as ns1.myserver.comns1.myserver.com and ns2.myserver.comns2.myserver.com.

Is this best practice? Should the nameservers be associated with a different domain?Is this best practice? Should the nameservers be associated with a different domain?

(My thoughts are that they should, otherwise you need to access the DNS records for myserver.commyserver.com in order to find out where the servers which house the DNS records you just accessed are.... Sounds a bit chicken & egg to me.)

Any Any advice or observations greatly appreciated.

I notice that, with most of the webhosts I use, they provide nameserver addresses under their main domain (or a related domain). For example, Mediatemple provides nameservers which are ns1.mediatemple.net and ns2.mediatemple.net So, when I setup a website on their servers, under a domain like myserver.com, the nameservers are not under that domain.

When I was setting up with a new host for another site, they setup nameservers under the domain of the site I was setting up. So, the website I was installing was myserver.com, they setup nameservers as ns1.myserver.com and ns2.myserver.com

Is this best practice? Should the nameservers be associated with a different domain?

(My thoughts are that they should, otherwise you need to access the DNS records for myserver.com in order to find out where the servers which house the DNS records you just accessed are.... Sounds a bit chicken & egg to me.)

Any advice or observations greatly appreciated.

I notice that, with most of the web hosts I use, they provide nameserver addresses under their main domain (or a related domain). 

For example Mediatemple provides name servers which are:

  1. ns1.mediatemple.net
  2. ns2.mediatemple.net

So when I setup a website on their servers, under a domain like myserver.com the nameservers are not under that domain.

When I was setting up with a new host for another site, they setup nameservers under the domain of the site I was setting up. So, the website I was installing was myserver.com, they setup nameservers as ns1.myserver.com and ns2.myserver.com.

Is this best practice? Should the nameservers be associated with a different domain?

(My thoughts are that they should, otherwise you need to access the DNS records for myserver.com in order to find out where the servers which house the DNS records you just accessed are.... Sounds a bit chicken & egg to me.) Any advice or observations greatly appreciated.

    Tweeted twitter.com/#!/StackWebmasters/status/146505361086611457
1
source | link

Should your Nameservers be under a Different Domain

I notice that, with most of the webhosts I use, they provide nameserver addresses under their main domain (or a related domain). For example, Mediatemple provides nameservers which are ns1.mediatemple.net and ns2.mediatemple.net So, when I setup a website on their servers, under a domain like myserver.com, the nameservers are not under that domain.

When I was setting up with a new host for another site, they setup nameservers under the domain of the site I was setting up. So, the website I was installing was myserver.com, they setup nameservers as ns1.myserver.com and ns2.myserver.com

Is this best practice? Should the nameservers be associated with a different domain?

(My thoughts are that they should, otherwise you need to access the DNS records for myserver.com in order to find out where the servers which house the DNS records you just accessed are.... Sounds a bit chicken & egg to me.)

Any advice or observations greatly appreciated.