Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There is no law against (ab)using someone elses domain or IP address in examples, but it is a very bad idea. As some uses will use your example values verbatim.<br> For example, the IP address <code>1.2.3.4</code> have been used in examples. But that is live real IPv4 addresses that are used in <code>1/8</code> as valid global IPv4-prefix. There are already some concerns about this use of that address in examples.</p> <p><a href="https://tools.ietf.org/html/rfc5737" rel="nofollow noreferrer">RFC5737</a> is about IPv4 addresses used for examples, which are any address in networks <code>192.0.2.0/24</code> (<code>TEST-NET-1</code>), <code>198.51.100.0/24</code> (<code>TEST-NET-2</code>) and <code>203.0.113.0/24</code> (<code>TEST-NET-3</code>), like <code>192.0.2.10</code>, <code>198.51.100.3</code> or <code>203.0.113.254</code>. These doesn't exist on Internet.</p> <blockquote> <p>Three IPv4 unicast address blocks are reserved for use in examples in specifications and other documents. This document describes the use of these blocks.</p> </blockquote> <p><a href="https://tools.ietf.org/html/rfc3849" rel="nofollow noreferrer">RFC3849</a> is about IPv6 addresses used for examples, which are any address in <code>2001:db8::/32</code>. These are are also not used on Internet.</p> <blockquote> <p>The document describes the use of the IPv6 address prefix <code>2001:DB8::/32</code> as a reserved prefix for use in documentation.</p> </blockquote> <p><a href="https://tools.ietf.org/html/rfc2606" rel="nofollow noreferrer">RFC2606</a> is about reserved TLD:s for different use. Those are "<code>.test</code>", "<code>.example</code>", "<code>.invalid</code>" and "<code>localhost</code>". Any domain under those can be used, like "<code>a-host.example</code>"<br> "<code>test</code>" is used for testing, "<code>example</code>" for documentation, "<code>invalid</code>" in configuration files that needs to be tweeked and "<code>localhost</code>" for <code>127/8</code> (mostly <code>127.0.0.1</code>). There are also three reserved second level domains to be used for example domains (<code>example.com</code>, <code>example.net</code> and <code>example.org</code>).</p> <blockquote> <p>To reduce the likelihood of conflict and confusion, a few top level domain names are reserved for use in private testing, as examples in documentation, and the like. In addition, a few second level domain names reserved for use as examples are documented.</p> </blockquote> <p><a href="https://tools.ietf.org/html/rfc1918" rel="nofollow noreferrer">RFC1918</a> is about the private network addresses <code>10/8</code>, <code>172.16/12</code> and <code>192.168/16</code>. Those are private and should not exist on Internet, so they might be used for example networks. But it's better to use the other reserved IP addresses mentioned above, as they will not conflict with real private network use in users LAN setup.</p> <blockquote> <p>This document describes address allocation for private internets. The allocation permits full network layer connectivity among all hosts inside an enterprise as well as among all public hosts of different enterprises.</p> </blockquote> <p><a href="https://tools.ietf.org/html/rfc3330" rel="nofollow noreferrer">RFC3330</a> should be of interest as an overview of all special IPv4 networks.</p> <blockquote> <p>This document describes the global and other specialized IPv4 address blocks that have been assigned by the Internet Assigned Numbers Authority (IANA).</p> </blockquote>
    singulars
    1. This table or related slice is empty.
    1. POexample.com is OK for domain example, what is example IP Address?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAnders
    1. USAnders
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO"There is no law against abusing someone elses domain or IP address in examples, but it is a very bad idea." Not that I'm arguing with you, but can you explain why it's such a bad idea?
      singulars
      1. PO
      1. USb1nary.atr0phy
    2. COBecause people will use the values in your example configuration and documentation, even if you tell them not to. Especially if your configs/docs get used and read. That is why there are IP addresses and domains explicitly reserved for use in example configuration files and in documentations.
      singulars
      1. PO
      1. USAnders
    3. COI understand that aspect, I'm just wondering if there are any kind of legal ramifications.
      singulars
      1. PO
      1. USb1nary.atr0phy
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload