Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.protocols.tcp-ip    |    TCP and IP network protocols.    |    14,669 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 14,105 of 14,669    |
|    Pascal Hambourg to All    |
|    Re: Trying to understand DNS    |
|    11 Dec 13 00:26:35    |
      From: boite-a-spam@plouf.fr.eu.org              Barry Margolin a écrit :       > In article <5c679fe6-0585-4a5a-990b-4acca832deb8@googlegroups.com>,       > iamhereintheworld@gmail.com wrote:       >       >> OK, we'll get into more complicated things later, I'm just trying to       >> understand from the beginning :) Sorry, what's an NS record?       >       > NS records specify the nameservers for delegated subdomains.       >       > So if the nameservers for hello.google.com were ns1.netsol.com and       > ns2.netsol.com, the google.com zone would contain records like:       >       > hello IN NS ns1.netsol.com.       > IN NS ns2.netsol.com.              And if the nameservers names for hello.google.com were ns1.google.com       and ns2.hello.google.com instead, which belong to the parent and child       zone respectively, the google.com zone would contain additional "glue"       records like :              ns1.google.com. IN A 192.0.2.1       ns2.hello.google.com. IN A 192.0.2.2              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca