Re: 4 part domain names
On Wed, Nov 24, 2004 at 07:48:56AM -0700, Peter Risdon wrote: The following article explains how to delegate sub domains to name servers using bind. I can't find an equivalent for djbdns and suspect there might be a limitation in that software: The Delegating names to another server portion of the following page is instructive: http://cr.yp.to/djbdns/run-server.html -- Danny ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4 part domain names
* stheg olloydson [EMAIL PROTECTED] [1157 00:57]: .. Generally, however, the tertiary domain level is the system's function: www, ftp, mail, etc. if the system is public. nitpick the function is often the leftmost component, not the tertiary - plenty of domains have more than 2 domain components. /nitpick -- In the beginning the Universe was created. This has made a lot of people very angry and been widely regarded as a bad move. - The Guide Rasputin :: Jack of All Trades - Master of Nuns ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4 part domain names
: Every unique combination of subdomain.domain.tld could point to an : arbitray other URL or IP. : For example : us.510.mail.example.com = example.com : de.510.mail.example.com = europe.mail.example.com I guess my question is this... if 'us' is the name of the node (machine) and 'example.com' is the registered domain name, what do the '510' and 'mail' parts uniquely identify? Why not just 'us.example.com'? jm -- My other computer is your Windows box. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4 part domain names
Jonathon McKitrick wrote: : Every unique combination of subdomain.domain.tld could point to an : arbitray other URL or IP. : For example : us.510.mail.example.com = example.com : de.510.mail.example.com = europe.mail.example.com I guess my question is this... if 'us' is the name of the node (machine) and 'example.com' is the registered domain name, what do the '510' and 'mail' parts uniquely identify? Why not just 'us.example.com'? I'm not an expert (IANAE should perhaps be a new acronym...), but here's how I understand it. The domain name system is completely open-ended and hierarchical. I tend to use djbdns for DNS servers, but found the bind concept of zones (and therefore zone files) very helpful. The top level is . and this is managed by the top level name servers, which have to be hard-wired into any name server. These name servers delegate responsibility for the next level down to other name servers, so .com. (the trailing dot is left out for most purposes, but not all - see your hosts file as generated by sysinstall) is managed by a number of servers, .uk. by others, and so on. These name servers delegate authority for zones within their zones to yet more name servers. This is where we come in with .com. domains, but not .uk. where there is another layer of delegation before we ordinary mortals start managing delegated zones. If you have registered example.com then authority for the whole zone of the internet, or the domain name system, below example.com. is delegated to you. You normally run name servers which publish information about hosts within this zone, but this is not the only thing you can do. You can also delegate authority for zones within this zone. Thus, there is a private company in the UK that delegates authority for zones below .uk.com. and thereby operates as a sort of private domain name registry. So you could delegate authority to stated nameservers for a zone such as mailservers.example.com and host information (A records) could be published by them for hosts such as smtp.mailservers.example.com. Of course, some of these could be aliases, and point to other hosts, but they don't have to be. And so it goes on; there's no limit to the possible delegation of zones beyond common sense and convenience. The fact that we normally manage second level domains is a function of normal practice, it isn't intrinsic to the system and it isn't the case in the UK where we normally manage third level domains. A DNS lookup for smtp.mailservers.example.com. would run as follows: 1. Look up in the static table of root name servers at least one value for a namserver that is authoritiative for . 2. Ask the . nameserver who is authoritative for .com. 3. Ask the .com. nameserver who is authoritative for example.com. 4. Ask the example.com. nameserver who is authoritative for mailservers.example.com. 5. Ask the mailservers.example.com. nameserver for the ip address of the host smtp.mailservers.example.com. The following article explains how to delegate sub domains to name servers using bind. I can't find an equivalent for djbdns and suspect there might be a limitation in that software: http://www.zytrax.com/books/dns/ch9/delegate.html Corrections welcome... Peter. -- the circle squared network systems and software http://www.circlesquared.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re[2]: 4 part domain names
JM : Every unique combination of subdomain.domain.tld could point to an JM : arbitray other URL or IP. JM : For example JM : us.510.mail.example.com = example.com JM : de.510.mail.example.com = europe.mail.example.com JM I guess my question is this... JM if 'us' is the name of the node (machine) and 'example.com' is the JM registered domain name, what do the '510' and 'mail' parts uniquely JM identify? Why not just 'us.example.com'? - Imagine not beeing a person with very simple needs like me or you but a big corporation. The corp where I work for example has adresses like uws015.ham.example.com and uws015.fra.example.com uws015 stands for unix workstation number 15 ham stands for Hamburg and fra for Frankfurt (actually these are 3 letter airport codes as I'm employed by an airline) that makes sense as you now can delegate the numbering of workstations to the local sysadmins in Hamburg and Frankfurt. Whichout them having to worry about taking a number that is already used. For your question it is very likely that example.com is a big webmail provider it would therefore make sense for them to have many different login servers all over the world. I could guess that mail identifies a mail server (big surprise there) and us.mail.example.com would therefore be a mail server in the United States whereas de.mail.example.com would be a mail server in Germany. Why they use mail.example.com, because they maybe also have us.news.example.com used. So it makes sense to group their many servers by function first and then by location. 510 could identify a rack or a datacenter so that us.510.mail.example.com means a mail server in the datecenter with the id 510 which serves the United States. But be aware that that extra meaning is arbitrary choosen by the Sysadmins at example.com they could aswell setup something like only.dump.persons.login.here.example.com and point their accountants to this server for login purposes. So if you are interested into why some specific specific subdomain names where choosen it would be wissest to ask the Sysadmins wo administer DNS for that domain. Hexren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4 part domain names
On Wed, Nov 24, 2004 at 04:08:06PM +0100, Hexren wrote: : location. 510 could identify a rack or a datacenter so that : us.510.mail.example.com means a mail server in the datecenter with : the id 510 which serves the United States. So 'us.510.mail' is an atomic, arbitrary identifier. All three as a unit identify a certain node, and are selected purely for convenience of human operators, right? I'm just making sure that the network doesn't treat 'us.510.mail' any different than it would treat 'foobar', right? I was thinking in java/python mode, where each 'dot-level' actually pointed to a node in the network, while what I understand now is that once you go beyond the domain name, the way you handle the other nodes is just up to the sysadmin, and is purely for human readability, right? jm -- My other computer is your Windows box. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re[2]: 4 part domain names
JM On Wed, Nov 24, 2004 at 04:08:06PM +0100, Hexren wrote: JM : location. 510 could identify a rack or a datacenter so that JM : us.510.mail.example.com means a mail server in the datecenter with JM : the id 510 which serves the United States. JM So 'us.510.mail' is an atomic, arbitrary identifier. All three as a unit JM identify a certain node, and are selected purely for convenience of human JM operators, right? I would say yes. JM I'm just making sure that the network doesn't treat 'us.510.mail' any JM different than it would treat 'foobar', right? I would say yes too. JM I was thinking in java/python mode, where each 'dot-level' actually pointed JM to a node in the network, while what I understand now is that once you go JM beyond the domain name, the way you handle the other nodes is just up to the JM sysadmin, and is purely for human readability, right? I would say yes yet again, only I do not know anything about python (exept the name) so I cannot really say anything about that. - Answers inline with the original Mail. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4 part domain names
Jonathon McKitrick wrote: On Wed, Nov 24, 2004 at 04:08:06PM +0100, Hexren wrote: : location. 510 could identify a rack or a datacenter so that : us.510.mail.example.com means a mail server in the datecenter with : the id 510 which serves the United States. So 'us.510.mail' is an atomic, arbitrary identifier. All three as a unit identify a certain node, and are selected purely for convenience of human operators, right? I'm just making sure that the network doesn't treat 'us.510.mail' any different than it would treat 'foobar', right? No, I don't think this is right. mail can be a zone beneath example.com, 510 a zone beneath that and us a hostname. This host might be aliased to foobar.example.com but it doesn't have to be. Peter. -- the circle squared network systems and software http://www.circlesquared.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4 part domain names
Hexren wrote: JM On Wed, Nov 24, 2004 at 04:08:06PM +0100, Hexren wrote: JM : location. 510 could identify a rack or a datacenter so that JM : us.510.mail.example.com means a mail server in the datecenter with JM : the id 510 which serves the United States. JM So 'us.510.mail' is an atomic, arbitrary identifier. All three as a unit JM identify a certain node, and are selected purely for convenience of human JM operators, right? I would say yes. JM I'm just making sure that the network doesn't treat 'us.510.mail' any JM different than it would treat 'foobar', right? I would say yes too. How does this square with the fact, as I understand it, that I can delegate authority for mail.example.com to new nameservers which can then publish host information about this zone? Here's the example zone file extracts from the article I linked to in an earlier mail, which is delegating authority for the sub domain us.example.com: quote ; zone fragment for 'zone name' example.com ; name servers in the same zone example.com. IN SOA ns1.example.com. root.example.com. ( 2003080800 ; serial number 2h ; refresh = 2 hours 15M; update retry = 15 minutes 3W12h ; expiry = 3 weeks + 12 hours 2h20M ; minimum = 2 hours + 20 minutes ) ; main domain name servers IN NS ns1.example.com. IN NS ns2.example.com. ; mail domain mail servers IN MX mail.example.com. ; A records for name servers above ns1 IN A 192.168.0.3 ns2 IN A 192.168.0.4 ; A record for mail server above mail IN A 192.168.0.5 ; sub-domain definitions $ORIGIN us.example.com. ; we define two name servers for the sub-domain @ IN NS ns3.us.example.com. ; the record above could have been written without the $ORIGIN as ; us.example.com. IN NS ns1.us.example.com. ns3 IN A 10.10.0.24 ; 'glue' record ; the record above could have been written as ; ns3.us.example.com. A 10.10.0.24 if it's less confusing /quote Peter. -- the circle squared network systems and software http://www.circlesquared.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4 part domain names
the zone description listed was pretty good. Basically, the leftmost name in a fully qualified domain name is the host (which could really be an alias or something) and the rest is the domain name. So for example u17.us.mail.somecompany.com u17 is the host (in this fictional account, a departmental mail server in the US division of somecompany) us.mail.somecompany.com is the domain The names get more general from left to right. It is a hierarchy. Similar to a postal address. For example John Doe 17 Main Street Anytown, TX 75263 USA John Doe is the host 17 is a specific location on a general street Main Street which is found in Anytown which is found in TX which is found in the USA. As a domain name it might be written JohnDoe.17.MainStreet.75263.Anytown.TX.USA Alfons Mueller Schardthof 10 D-84051 Essenbach Germany would be the same. AlfonsMueller.10.Schardthof.84051.Essenbach.Bayern.Germany is a progressively more general description of where Mr. Alfons Mueller can be located. When you send a postal letter to one of these people (John Doe or Alfons Mueller), the letter is sent to the respective country's main postal office, then to a regional and then a city and then maybe a neighborhood (depending on your area) post office before being delivered. The hierarchy helps the routing of the mail. Same with domain names. The hierarchy helps to keep trach of the complexity in a delegated fashion Sorry for the complex examples Chad ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4 part domain names
* Peter Risdon [EMAIL PROTECTED] [1140 15:40]: Hexren wrote: JM On Wed, Nov 24, 2004 at 04:08:06PM +0100, Hexren wrote: JM : location. 510 could identify a rack or a datacenter so that JM : us.510.mail.example.com means a mail server in the datecenter with JM : the id 510 which serves the United States. JM So 'us.510.mail' is an atomic, arbitrary identifier. All three as a unit JM identify a certain node, and are selected purely for convenience of human JM operators, right? I would say yes. JM I'm just making sure that the network doesn't treat 'us.510.mail' any JM different than it would treat 'foobar', right? I would say yes too. How does this square with the fact, as I understand it, that I can delegate authority for mail.example.com to new nameservers which can then publish host information about this zone? That's got nothing to do with the network. For example, I can create a host in example.com called us.510.mail and you can't stop me (evil laughter). -- Robots don't have emotions, and that sometimes makes me feel sad. - Bender Rasputin :: Jack of All Trades - Master of Nuns ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re[2]: 4 part domain names
JM : Every unique combination of subdomain.domain.tld could point to an JM : arbitray other URL or IP. JM : For example JM : us.510.mail.example.com = example.com JM : de.510.mail.example.com = europe.mail.example.com JM I guess my question is this... JM if 'us' is the name of the node (machine) and 'example.com' is the JM registered domain name, what do the '510' and 'mail' parts uniquely JM identify? Why not just 'us.example.com'? - Imagine not beeing a person with very simple needs like me or you but a big corporation. The corp where I work for example has adresses like uws015.ham.example.com and uws015.fra.example.com uws015 stands for unix workstation number 15 ham stands for Hamburg and fra for Frankfurt (actually these are 3 letter airport codes as I'm employed by an airline) that makes sense as you now can delegate the numbering of workstations to the local sysadmins in Hamburg and Frankfurt. Whichout them having to worry about taking a number that is already used. For your question it is very likely that example.com is a big webmail provider it would therefore make sense for them to have many different login servers all over the world. I could guess that mail identifies a mail server (big surprise there) and us.mail.example.com would therefore be a mail server in the United States whereas de.mail.example.com would be a mail server in Germany. Why they use mail.example.com, because they maybe also have us.news.example.com used. So it makes sense to group their many servers by function first and then by location. 510 could identify a rack or a datacenter so that us.510.mail.example.com means a mail server in the datecenter with the id 510 which serves the United States. But be aware that that extra meaning is arbitrary choosen by the Sysadmins at example.com they could aswell setup something like only.dump.persons.login.here.example.com and point their accountants to this server for login purposes. So if you are interested into why some specific specific subdomain names where choosen it would be wissest to ask the Sysadmins wo administer DNS for that domain. Hexren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4 part domain names
Dick Davies wrote: * Peter Risdon [EMAIL PROTECTED] [1140 15:40]: Hexren wrote: JM On Wed, Nov 24, 2004 at 04:08:06PM +0100, Hexren wrote: JM : location. 510 could identify a rack or a datacenter so that JM : us.510.mail.example.com means a mail server in the datecenter with JM : the id 510 which serves the United States. JM So 'us.510.mail' is an atomic, arbitrary identifier. All three as a unit JM identify a certain node, and are selected purely for convenience of human JM operators, right? I would say yes. JM I'm just making sure that the network doesn't treat 'us.510.mail' any JM different than it would treat 'foobar', right? I would say yes too. How does this square with the fact, as I understand it, that I can delegate authority for mail.example.com to new nameservers which can then publish host information about this zone? That's got nothing to do with the network. For example, I can create a host in example.com called us.510.mail and you can't stop me (evil laughter). Hmmm... RFC921: quote There are some limits on these names. They must start with a letter, end with a letter or digit and have only letters or digits or hyphen as interior characters. Case is not significant. For example: USC-ISIF Hierarchical Names Because of the growth of the Internet, structured names (or domain style names) have been introduced. Each element of the structured name will be a character string (with the same constraints that previously applied to the simple names). The elements (or components) of the structured names are separated with periods, and the elements are written from the most specific on the left to the most general on the right. /quote Peter. -- the circle squared network systems and software http://www.circlesquared.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4 part domain names
Dick Davies wrote: * Peter Risdon [EMAIL PROTECTED] [1140 15:40]: Hexren wrote: JM On Wed, Nov 24, 2004 at 04:08:06PM +0100, Hexren wrote: JM : location. 510 could identify a rack or a datacenter so that JM : us.510.mail.example.com means a mail server in the datecenter with JM : the id 510 which serves the United States. JM So 'us.510.mail' is an atomic, arbitrary identifier. All three as a unit JM identify a certain node, and are selected purely for convenience of human JM operators, right? I would say yes. JM I'm just making sure that the network doesn't treat 'us.510.mail' any JM different than it would treat 'foobar', right? I would say yes too. How does this square with the fact, as I understand it, that I can delegate authority for mail.example.com to new nameservers which can then publish host information about this zone? That's got nothing to do with the network. For example, I can create a host in example.com called us.510.mail and you can't stop me (evil laughter). Sent the RFC mail prematurely... RFC 952 says: quote A name (Net, Host, Gateway, or Domain name) is a text string up to 24 characters drawn from the alphabet (A-Z), digits (0-9), minus sign (-), and period (.). Note that periods are only allowed when they serve to delimit components of domain style names. (See RFC-921, Domain Name System Implementation Schedule, for background). /quote So I guess you could, but it wouldn't be canonical. If authority ever gets delegated for mail.example.com, then for 510.mail.example.com, then a host called us is published, there's going to be a bit of a problem with your network. Peter. -- the circle squared network systems and software http://www.circlesquared.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4 part domain names
* Peter Risdon [EMAIL PROTECTED] [1153 16:53]: For example, I can create a host in example.com called us.510.mail and you can't stop me (evil laughter). Sent the RFC mail prematurely... RFC 952 says: quote A name (Net, Host, Gateway, or Domain name) is a text string up to 24 characters drawn from the alphabet (A-Z), digits (0-9), minus sign (-), and period (.). Note that periods are only allowed when they serve to delimit components of domain style names. (See RFC-921, Domain Name System Implementation Schedule, for background). /quote So I guess you could, but it wouldn't be canonical. If authority ever gets delegated for mail.example.com, then for 510.mail.example.com, then a host called us is published, there's going to be a bit of a problem with your network. Oh my god yes. I've done this for shuddercustomers/shudder. It works. And is horribly confusing for everyone. I stand by my demented cackle ^_^ -- Rasputin :: Jack of All Trades - Master of Nuns ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4 part domain names
it was said: * stheg olloydson [EMAIL PROTECTED] [1157 00:57]: .. Generally, however, the tertiary domain level is the system's function: www, ftp, mail, etc. if the system is public. nitpick the function is often the leftmost component, not the tertiary - plenty of domains have more than 2 domain components. /nitpick Quite right. I should have said, In domains following the domain.xxx structure the tertiary..., and domains following the cTLD structure of domain.yy(y).xx the quartenary And instead of Generally, I should have said, Customarily. Thanks, Stheg __ Do you Yahoo!? The all-new My Yahoo! - Get yours free! http://my.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
4 part domain names
AFAIK, a fully qualified domain name is like machine.domain.xxx but what about addresses like us.510.mail.yahoo.com?? Is there any hierarchy to the names in this case? jm -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4 part domain names
JM AFAIK, a fully qualified domain name is like JM machine.domain.xxx JM but what about addresses like JM us.510.mail.yahoo.com?? JM Is there any hierarchy to the names in this case? JM jm - I would think that viewing mail.yahoo.com as machine.domain.xxx might be flawed if you think of mail.yahoo.com as subdomain.domain.top-level-domain it is (or so I think) easier to comprehend that subdomain.subdomain.domain.top-level-domain is not that different. Now add to that picture that every subdomain could be an alias for another domain or point to an IP address, which incase of the IP address is meaning a real machine. Did I misinterpret your question ? Hexren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4 part domain names
On Wed, Nov 24, 2004 at 12:48:49AM +0100, Hexren wrote: : Now add to that picture that every subdomain could be an alias for another : domain or point to an IP address, which incase of the IP address is : meaning a real machine. So that means that the right-most portion of the subdomain would be either the aliased domain of another machine or an IP address, right? So does that mean us.510.mail.yahoo.com could be us.510.some_secret_domain.xxx?? Or that it could be a new domain within a private network? Or either? jm -- My other computer is your Windows box. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4 part domain names
it was said: On Wed, Nov 24, 2004 at 12:48:49AM +0100, Hexren wrote: : Now add to that picture that every subdomain could be an alias for another : domain or point to an IP address, which incase of the IP address is : meaning a real machine. So that means that the right-most portion of the subdomain would be either the aliased domain of another machine or an IP address, right? So does that mean us.510.mail.yahoo.com could be us.510.some_secret_domain.xxx?? Or that it could be a new domain within a private network? Or either? jm Either - although the likelihood of a private network's DNS being publicly advertised is small. The some_secret_domain part is really very common. Usually it is called domain forwarding or domain masking. This is useful companies that, for whatever reason, want to redirect traffic from one URL to another. For instance, HP bought Compaq. If you try to go to compaq.com, you'll arrive at hp.com. Really, the only thing matters is the .xxx part and which DNS root servers you use. A number of alternative DNS networks outside of ICANN's control have been in existence for some years, the most famous and widely supported being new.net and adns.net. Of course, you need to be authoritative for a secondary level domain if you expect systems not using your DNS servers to get to that domain. Other than that you can follow whatever naming scheme makes sense to you. Generally, however, the tertiary domain level is the system's function: www, ftp, mail, etc. if the system is public. Also, any public DNS probably shouldn't have things like ccard-srvr.company.xxx or database.company.xxx - no sense in handing out invitations to the barbarian hordes. HTH, Stheg __ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re[2]: 4 part domain names
JM On Wed, Nov 24, 2004 at 12:48:49AM +0100, Hexren wrote: JM : Now add to that picture that every subdomain could be an alias for another JM : domain or point to an IP address, which incase of the IP address is JM : meaning a real machine. JM So that means that the right-most portion of the subdomain would be either JM the aliased domain of another machine or an IP address, right? So does that JM mean us.510.mail.yahoo.com could be us.510.some_secret_domain.xxx?? Or that JM it could be a new domain within a private network? Or either? - Every unique combination of subdomain.domain.tld could point to an arbitray other URL or IP. For example us.510.mail.example.com = example.com de.510.mail.example.com = europe.mail.example.com us.487.mail.example.com = 10.0.0.1 us.512.mail.example.com = 192.168.0.1 mail.yahoo.com = nowhere (teher is no entry in the dns for that URL) The point I am trying to make ist that dns only defines a structure for data. The fact that the data stored in that structure tends to be orderly in some sort is the result of that order making administering and using the stored data easier (techs are lazy people after all). But something like zdfdfjkb.12462323df.example.com would be valid even though it would contradict the point of using dns to take the burden of remembering complex data (IPs) from people. Hexren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
