Is it true to say that an hosting provider's DNS server is what links the entire hosting environment to ICANN? Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?Recommendations for managing DNS issues when hosting customer sitesThird-party SaaS will also host our web site. They want our registrar username and password. Is this normal?Problem with the DNS settings for our new company mailserverWeb hosting announced downtime and how it affects FORWARD domain names?How to find domain registrar and DNS hosting with good DNSSEC support?DNS: forward part of a managed domain to one host, but sub domain services to another (Google Apps)Only I can access my hosted website!My website's DNS no longer resolved after my hosting provider suffered a DDoS attackHow to configure DNS for hosting a domain with 000webhost.com when purchased from whois.com?What records (DNS, Nameservers etc.) need to be used to map a Domain to a Hosting Server
Single word antonym of "flightless"
The logistics of corpse disposal
Do I really need recursive chmod to restrict access to a folder?
If Jon Snow became King of the Seven Kingdoms what would his regnal number be?
What causes the vertical darker bands in my photo?
What are the motives behind Cersei's orders given to Bronn?
Sorting numerically
How does a Death Domain cleric's Touch of Death feature work with Touch-range spells delivered by familiars?
Letter Boxed validator
If 'B is more likely given A', then 'A is more likely given B'
How to draw this diagram using TikZ package?
Why are there no cargo aircraft with "flying wing" design?
"Seemed to had" is it correct?
How to find all the available tools in macOS terminal?
Withdrew £2800, but only £2000 shows as withdrawn on online banking; what are my obligations?
What are 'alternative tunings' of a guitar and why would you use them? Doesn't it make it more difficult to play?
Stars Make Stars
I am not a queen, who am I?
What makes black pepper strong or mild?
How can I make names more distinctive without making them longer?
How can I fade player when goes inside or outside of the area?
Did Xerox really develop the first LAN?
Using et al. for a last / senior author rather than for a first author
How do I keep my slimes from escaping their pens?
Is it true to say that an hosting provider's DNS server is what links the entire hosting environment to ICANN?
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Announcing the arrival of Valued Associate #679: Cesar Manara
Unicorn Meta Zoo #1: Why another podcast?Recommendations for managing DNS issues when hosting customer sitesThird-party SaaS will also host our web site. They want our registrar username and password. Is this normal?Problem with the DNS settings for our new company mailserverWeb hosting announced downtime and how it affects FORWARD domain names?How to find domain registrar and DNS hosting with good DNSSEC support?DNS: forward part of a managed domain to one host, but sub domain services to another (Google Apps)Only I can access my hosted website!My website's DNS no longer resolved after my hosting provider suffered a DDoS attackHow to configure DNS for hosting a domain with 000webhost.com when purchased from whois.com?What records (DNS, Nameservers etc.) need to be used to map a Domain to a Hosting Server
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
As of my understanding, after we register a domain as our property in ICANN via a local domain-register authorized by a local internet society branch (like ISOC UK for Great Britain), we need to point the domain-register's DNS servers to those of the hosting providers by their DNS names and by that we "link" the hosting provider to ICANN and use the ICANN domain to address our Website directory,
Hence, is it true to say that an hosting provider's DNS server is what links the entire hosting environment to ICANN?
web-hosting dns icann
add a comment |
As of my understanding, after we register a domain as our property in ICANN via a local domain-register authorized by a local internet society branch (like ISOC UK for Great Britain), we need to point the domain-register's DNS servers to those of the hosting providers by their DNS names and by that we "link" the hosting provider to ICANN and use the ICANN domain to address our Website directory,
Hence, is it true to say that an hosting provider's DNS server is what links the entire hosting environment to ICANN?
web-hosting dns icann
add a comment |
As of my understanding, after we register a domain as our property in ICANN via a local domain-register authorized by a local internet society branch (like ISOC UK for Great Britain), we need to point the domain-register's DNS servers to those of the hosting providers by their DNS names and by that we "link" the hosting provider to ICANN and use the ICANN domain to address our Website directory,
Hence, is it true to say that an hosting provider's DNS server is what links the entire hosting environment to ICANN?
web-hosting dns icann
As of my understanding, after we register a domain as our property in ICANN via a local domain-register authorized by a local internet society branch (like ISOC UK for Great Britain), we need to point the domain-register's DNS servers to those of the hosting providers by their DNS names and by that we "link" the hosting provider to ICANN and use the ICANN domain to address our Website directory,
Hence, is it true to say that an hosting provider's DNS server is what links the entire hosting environment to ICANN?
web-hosting dns icann
web-hosting dns icann
edited 7 hours ago
JohnDoea
asked 8 hours ago
JohnDoeaJohnDoea
651324
651324
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Stephen's answer gives you all the details, but I think your misconception or slight changes of wording is related to something else, the "IANA root".
ICANN oversees the running of the system, and plays no operational part (which is a simplification, as they technically run some root nameservers, and are also the "registry" of .int
, but this is tangential to your case).
ICANN has a direct contract with gTLD registries, but it still needs to manage a single hierarchy in which all TLDs fit in, because obviously there is a need of uniqueness. This is called the "IANA root". Because there have been multiple attempts in the past of people trying, for technical, political, philosophical, experiment, to define other roots, which would/could carry other TLDs.
This was called "alternate roots". They all failed for various reasons. Or at least the one trying to sell "new" TLDs, that would work only in the alternate root. There are still some alternate roots used for experiments, like the YETI Project
But the IANA root is described in RFC 2826: "IAB Technical Comment on the Unique DNS Root" which says in its summary:
The DNS name space is a hierarchical name space derived from a
single, globally unique root. This is a technical constraint
inherent in the design of the DNS. Therefore it is not technically
feasible for there to be more than one root in the public DNS.
That one root must be supported by a set of coordinated root
servers administered by a unique naming authority.
IANA was previously a specific service just maintaining this and other parameters for the IETF. After ICANN was built, IANA became a service inside ICANN. After latest ICANN evolutions, IANA is now more technically called "PTI" for "Public Technical Identifiers", see https://pti.icann.org/
It is a separate structure, in contract with ICANN, that manages the IANA functions.
add a comment |
ICANN is several layers removed from your hosting. There is a link, but isn't a direct link in any sense.
- ICANN is an organization that oversees the domain name system. They allow other companies to operate top level domains. They run some of the DNS servers that point to the DNS servers of the top level domain operators.
- The top level domain operator runs the name servers for a top level domain and allows domains to be sold under that top level domain. For example Verisign operates the
.com
top level domain. - Your domain registrar sells domains and can insert NS records for the top level domain. For example GoDaddy registers domains and can insert NS records for
.com
domains to Verisign. These NS records point to your DNS records at your DNS hosting company. - Your DNS host has the
A
andCNAME
records that point to your web hosting company. - Your web hosting company runs a web server on an IP address that is specified in your DNS records at your DNS host.
Your web host and your DNS host may not even be the same company. It is very common to get DNS hosting bundled with web hosting. However, you can use DNS hosting from your domain registrar or from another company.
When somebody wants to get to your website using your domain name, ICANN isn't usually involved at all.
- The web browser contacts a local DNS server to get the IP address.
- The local DNS server looks it up from a parent DNS server and then caches it.
- If no parent has it in the cache, the DNS servers for the top level domain are consulted to get the NS records for your DNS host.
- Your DNS host returns the IP address and sends it back down this chain.
- The only time that ICANN's DNS server would be queried, is if no caching DNS server had the records for the top level domain. This happens only for a very small percentage of DNS requests.
Most of the time, ICANN isn't directly involved in fulfilling requests to your website. Even when it is involved, it is involved only tangentially and through several other intermediaries.
"The only time that ICANN's DNS server would be queried, is if no caching DNS server had the records for the top level domain." No or not always. See root-servers.org there are 13 root servers, only one (theL
one) is managed technically by ICANN. All others are managed by corporations, universities, the US army or non profit organizations, that do not have real formal contracts with ICANN.
– Patrick Mevzek
7 hours ago
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "45"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fwebmasters.stackexchange.com%2fquestions%2f122256%2fis-it-true-to-say-that-an-hosting-providers-dns-server-is-what-links-the-entire%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Stephen's answer gives you all the details, but I think your misconception or slight changes of wording is related to something else, the "IANA root".
ICANN oversees the running of the system, and plays no operational part (which is a simplification, as they technically run some root nameservers, and are also the "registry" of .int
, but this is tangential to your case).
ICANN has a direct contract with gTLD registries, but it still needs to manage a single hierarchy in which all TLDs fit in, because obviously there is a need of uniqueness. This is called the "IANA root". Because there have been multiple attempts in the past of people trying, for technical, political, philosophical, experiment, to define other roots, which would/could carry other TLDs.
This was called "alternate roots". They all failed for various reasons. Or at least the one trying to sell "new" TLDs, that would work only in the alternate root. There are still some alternate roots used for experiments, like the YETI Project
But the IANA root is described in RFC 2826: "IAB Technical Comment on the Unique DNS Root" which says in its summary:
The DNS name space is a hierarchical name space derived from a
single, globally unique root. This is a technical constraint
inherent in the design of the DNS. Therefore it is not technically
feasible for there to be more than one root in the public DNS.
That one root must be supported by a set of coordinated root
servers administered by a unique naming authority.
IANA was previously a specific service just maintaining this and other parameters for the IETF. After ICANN was built, IANA became a service inside ICANN. After latest ICANN evolutions, IANA is now more technically called "PTI" for "Public Technical Identifiers", see https://pti.icann.org/
It is a separate structure, in contract with ICANN, that manages the IANA functions.
add a comment |
Stephen's answer gives you all the details, but I think your misconception or slight changes of wording is related to something else, the "IANA root".
ICANN oversees the running of the system, and plays no operational part (which is a simplification, as they technically run some root nameservers, and are also the "registry" of .int
, but this is tangential to your case).
ICANN has a direct contract with gTLD registries, but it still needs to manage a single hierarchy in which all TLDs fit in, because obviously there is a need of uniqueness. This is called the "IANA root". Because there have been multiple attempts in the past of people trying, for technical, political, philosophical, experiment, to define other roots, which would/could carry other TLDs.
This was called "alternate roots". They all failed for various reasons. Or at least the one trying to sell "new" TLDs, that would work only in the alternate root. There are still some alternate roots used for experiments, like the YETI Project
But the IANA root is described in RFC 2826: "IAB Technical Comment on the Unique DNS Root" which says in its summary:
The DNS name space is a hierarchical name space derived from a
single, globally unique root. This is a technical constraint
inherent in the design of the DNS. Therefore it is not technically
feasible for there to be more than one root in the public DNS.
That one root must be supported by a set of coordinated root
servers administered by a unique naming authority.
IANA was previously a specific service just maintaining this and other parameters for the IETF. After ICANN was built, IANA became a service inside ICANN. After latest ICANN evolutions, IANA is now more technically called "PTI" for "Public Technical Identifiers", see https://pti.icann.org/
It is a separate structure, in contract with ICANN, that manages the IANA functions.
add a comment |
Stephen's answer gives you all the details, but I think your misconception or slight changes of wording is related to something else, the "IANA root".
ICANN oversees the running of the system, and plays no operational part (which is a simplification, as they technically run some root nameservers, and are also the "registry" of .int
, but this is tangential to your case).
ICANN has a direct contract with gTLD registries, but it still needs to manage a single hierarchy in which all TLDs fit in, because obviously there is a need of uniqueness. This is called the "IANA root". Because there have been multiple attempts in the past of people trying, for technical, political, philosophical, experiment, to define other roots, which would/could carry other TLDs.
This was called "alternate roots". They all failed for various reasons. Or at least the one trying to sell "new" TLDs, that would work only in the alternate root. There are still some alternate roots used for experiments, like the YETI Project
But the IANA root is described in RFC 2826: "IAB Technical Comment on the Unique DNS Root" which says in its summary:
The DNS name space is a hierarchical name space derived from a
single, globally unique root. This is a technical constraint
inherent in the design of the DNS. Therefore it is not technically
feasible for there to be more than one root in the public DNS.
That one root must be supported by a set of coordinated root
servers administered by a unique naming authority.
IANA was previously a specific service just maintaining this and other parameters for the IETF. After ICANN was built, IANA became a service inside ICANN. After latest ICANN evolutions, IANA is now more technically called "PTI" for "Public Technical Identifiers", see https://pti.icann.org/
It is a separate structure, in contract with ICANN, that manages the IANA functions.
Stephen's answer gives you all the details, but I think your misconception or slight changes of wording is related to something else, the "IANA root".
ICANN oversees the running of the system, and plays no operational part (which is a simplification, as they technically run some root nameservers, and are also the "registry" of .int
, but this is tangential to your case).
ICANN has a direct contract with gTLD registries, but it still needs to manage a single hierarchy in which all TLDs fit in, because obviously there is a need of uniqueness. This is called the "IANA root". Because there have been multiple attempts in the past of people trying, for technical, political, philosophical, experiment, to define other roots, which would/could carry other TLDs.
This was called "alternate roots". They all failed for various reasons. Or at least the one trying to sell "new" TLDs, that would work only in the alternate root. There are still some alternate roots used for experiments, like the YETI Project
But the IANA root is described in RFC 2826: "IAB Technical Comment on the Unique DNS Root" which says in its summary:
The DNS name space is a hierarchical name space derived from a
single, globally unique root. This is a technical constraint
inherent in the design of the DNS. Therefore it is not technically
feasible for there to be more than one root in the public DNS.
That one root must be supported by a set of coordinated root
servers administered by a unique naming authority.
IANA was previously a specific service just maintaining this and other parameters for the IETF. After ICANN was built, IANA became a service inside ICANN. After latest ICANN evolutions, IANA is now more technically called "PTI" for "Public Technical Identifiers", see https://pti.icann.org/
It is a separate structure, in contract with ICANN, that manages the IANA functions.
answered 7 hours ago
Patrick MevzekPatrick Mevzek
3,0031622
3,0031622
add a comment |
add a comment |
ICANN is several layers removed from your hosting. There is a link, but isn't a direct link in any sense.
- ICANN is an organization that oversees the domain name system. They allow other companies to operate top level domains. They run some of the DNS servers that point to the DNS servers of the top level domain operators.
- The top level domain operator runs the name servers for a top level domain and allows domains to be sold under that top level domain. For example Verisign operates the
.com
top level domain. - Your domain registrar sells domains and can insert NS records for the top level domain. For example GoDaddy registers domains and can insert NS records for
.com
domains to Verisign. These NS records point to your DNS records at your DNS hosting company. - Your DNS host has the
A
andCNAME
records that point to your web hosting company. - Your web hosting company runs a web server on an IP address that is specified in your DNS records at your DNS host.
Your web host and your DNS host may not even be the same company. It is very common to get DNS hosting bundled with web hosting. However, you can use DNS hosting from your domain registrar or from another company.
When somebody wants to get to your website using your domain name, ICANN isn't usually involved at all.
- The web browser contacts a local DNS server to get the IP address.
- The local DNS server looks it up from a parent DNS server and then caches it.
- If no parent has it in the cache, the DNS servers for the top level domain are consulted to get the NS records for your DNS host.
- Your DNS host returns the IP address and sends it back down this chain.
- The only time that ICANN's DNS server would be queried, is if no caching DNS server had the records for the top level domain. This happens only for a very small percentage of DNS requests.
Most of the time, ICANN isn't directly involved in fulfilling requests to your website. Even when it is involved, it is involved only tangentially and through several other intermediaries.
"The only time that ICANN's DNS server would be queried, is if no caching DNS server had the records for the top level domain." No or not always. See root-servers.org there are 13 root servers, only one (theL
one) is managed technically by ICANN. All others are managed by corporations, universities, the US army or non profit organizations, that do not have real formal contracts with ICANN.
– Patrick Mevzek
7 hours ago
add a comment |
ICANN is several layers removed from your hosting. There is a link, but isn't a direct link in any sense.
- ICANN is an organization that oversees the domain name system. They allow other companies to operate top level domains. They run some of the DNS servers that point to the DNS servers of the top level domain operators.
- The top level domain operator runs the name servers for a top level domain and allows domains to be sold under that top level domain. For example Verisign operates the
.com
top level domain. - Your domain registrar sells domains and can insert NS records for the top level domain. For example GoDaddy registers domains and can insert NS records for
.com
domains to Verisign. These NS records point to your DNS records at your DNS hosting company. - Your DNS host has the
A
andCNAME
records that point to your web hosting company. - Your web hosting company runs a web server on an IP address that is specified in your DNS records at your DNS host.
Your web host and your DNS host may not even be the same company. It is very common to get DNS hosting bundled with web hosting. However, you can use DNS hosting from your domain registrar or from another company.
When somebody wants to get to your website using your domain name, ICANN isn't usually involved at all.
- The web browser contacts a local DNS server to get the IP address.
- The local DNS server looks it up from a parent DNS server and then caches it.
- If no parent has it in the cache, the DNS servers for the top level domain are consulted to get the NS records for your DNS host.
- Your DNS host returns the IP address and sends it back down this chain.
- The only time that ICANN's DNS server would be queried, is if no caching DNS server had the records for the top level domain. This happens only for a very small percentage of DNS requests.
Most of the time, ICANN isn't directly involved in fulfilling requests to your website. Even when it is involved, it is involved only tangentially and through several other intermediaries.
"The only time that ICANN's DNS server would be queried, is if no caching DNS server had the records for the top level domain." No or not always. See root-servers.org there are 13 root servers, only one (theL
one) is managed technically by ICANN. All others are managed by corporations, universities, the US army or non profit organizations, that do not have real formal contracts with ICANN.
– Patrick Mevzek
7 hours ago
add a comment |
ICANN is several layers removed from your hosting. There is a link, but isn't a direct link in any sense.
- ICANN is an organization that oversees the domain name system. They allow other companies to operate top level domains. They run some of the DNS servers that point to the DNS servers of the top level domain operators.
- The top level domain operator runs the name servers for a top level domain and allows domains to be sold under that top level domain. For example Verisign operates the
.com
top level domain. - Your domain registrar sells domains and can insert NS records for the top level domain. For example GoDaddy registers domains and can insert NS records for
.com
domains to Verisign. These NS records point to your DNS records at your DNS hosting company. - Your DNS host has the
A
andCNAME
records that point to your web hosting company. - Your web hosting company runs a web server on an IP address that is specified in your DNS records at your DNS host.
Your web host and your DNS host may not even be the same company. It is very common to get DNS hosting bundled with web hosting. However, you can use DNS hosting from your domain registrar or from another company.
When somebody wants to get to your website using your domain name, ICANN isn't usually involved at all.
- The web browser contacts a local DNS server to get the IP address.
- The local DNS server looks it up from a parent DNS server and then caches it.
- If no parent has it in the cache, the DNS servers for the top level domain are consulted to get the NS records for your DNS host.
- Your DNS host returns the IP address and sends it back down this chain.
- The only time that ICANN's DNS server would be queried, is if no caching DNS server had the records for the top level domain. This happens only for a very small percentage of DNS requests.
Most of the time, ICANN isn't directly involved in fulfilling requests to your website. Even when it is involved, it is involved only tangentially and through several other intermediaries.
ICANN is several layers removed from your hosting. There is a link, but isn't a direct link in any sense.
- ICANN is an organization that oversees the domain name system. They allow other companies to operate top level domains. They run some of the DNS servers that point to the DNS servers of the top level domain operators.
- The top level domain operator runs the name servers for a top level domain and allows domains to be sold under that top level domain. For example Verisign operates the
.com
top level domain. - Your domain registrar sells domains and can insert NS records for the top level domain. For example GoDaddy registers domains and can insert NS records for
.com
domains to Verisign. These NS records point to your DNS records at your DNS hosting company. - Your DNS host has the
A
andCNAME
records that point to your web hosting company. - Your web hosting company runs a web server on an IP address that is specified in your DNS records at your DNS host.
Your web host and your DNS host may not even be the same company. It is very common to get DNS hosting bundled with web hosting. However, you can use DNS hosting from your domain registrar or from another company.
When somebody wants to get to your website using your domain name, ICANN isn't usually involved at all.
- The web browser contacts a local DNS server to get the IP address.
- The local DNS server looks it up from a parent DNS server and then caches it.
- If no parent has it in the cache, the DNS servers for the top level domain are consulted to get the NS records for your DNS host.
- Your DNS host returns the IP address and sends it back down this chain.
- The only time that ICANN's DNS server would be queried, is if no caching DNS server had the records for the top level domain. This happens only for a very small percentage of DNS requests.
Most of the time, ICANN isn't directly involved in fulfilling requests to your website. Even when it is involved, it is involved only tangentially and through several other intermediaries.
edited 6 hours ago
answered 7 hours ago
Stephen Ostermiller♦Stephen Ostermiller
69.7k1396253
69.7k1396253
"The only time that ICANN's DNS server would be queried, is if no caching DNS server had the records for the top level domain." No or not always. See root-servers.org there are 13 root servers, only one (theL
one) is managed technically by ICANN. All others are managed by corporations, universities, the US army or non profit organizations, that do not have real formal contracts with ICANN.
– Patrick Mevzek
7 hours ago
add a comment |
"The only time that ICANN's DNS server would be queried, is if no caching DNS server had the records for the top level domain." No or not always. See root-servers.org there are 13 root servers, only one (theL
one) is managed technically by ICANN. All others are managed by corporations, universities, the US army or non profit organizations, that do not have real formal contracts with ICANN.
– Patrick Mevzek
7 hours ago
"The only time that ICANN's DNS server would be queried, is if no caching DNS server had the records for the top level domain." No or not always. See root-servers.org there are 13 root servers, only one (the
L
one) is managed technically by ICANN. All others are managed by corporations, universities, the US army or non profit organizations, that do not have real formal contracts with ICANN.– Patrick Mevzek
7 hours ago
"The only time that ICANN's DNS server would be queried, is if no caching DNS server had the records for the top level domain." No or not always. See root-servers.org there are 13 root servers, only one (the
L
one) is managed technically by ICANN. All others are managed by corporations, universities, the US army or non profit organizations, that do not have real formal contracts with ICANN.– Patrick Mevzek
7 hours ago
add a comment |
Thanks for contributing an answer to Webmasters Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fwebmasters.stackexchange.com%2fquestions%2f122256%2fis-it-true-to-say-that-an-hosting-providers-dns-server-is-what-links-the-entire%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown