upstream/opnsense-src
1
0
Fork 0
mirror of https://github.com/opnsense/src.git synced 2026-04-23 15:19:31 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions
opnsense-src/lib/libc/net/hosts

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

31 lines
1 KiB
Text
Raw Normal View History

Initial import of 386BSD 0.1 othersrc/etc
1993-06-20 09:41:45 -04:00
#
# Host Database
- Improve line-wrapping and spacing so as to improve readability. - Add instructions regarding replacing 'my.domain', as this has come up on freebsd-questions. - Remove reference to rs.internic.net/templates, as that directory no longer exists. Instead, encourage them gently to talk to their network provider. MFC after: 1 week
2001-12-11 17:36:10 -05:00
#
# This file should contain the addresses and aliases for local hosts that
# share this file. Replace 'my.domain' below with the domainname of your
# machine.
#
Added RCS Id. Also changed comment to indicate that /etc/host.conf determines when and how this file will be consulted. Added comment to the effect that (1) zero is not a vaild network number and (2) please get a valid network number assigned by your provider or by the Internet Registry.
1993-11-11 17:32:36 -05:00
# In the presence of the domain name service or NIS, this file may
Add nsswitch support. By creating an /etc/nsswitch.conf file, you can configure FreeBSD so that various databases such as passwd and group can be looked up using flat files, NIS, or Hesiod. = Hesiod has been added to libc (see hesiod(3)). = A library routine for parsing nsswitch.conf and invoking callback functions as specified has been added to libc (see nsdispatch(3)). = The following C library functions have been modified to use nsdispatch: . getgrent, getgrnam, getgrgid . getpwent, getpwnam, getpwuid . getusershell . getaddrinfo . gethostbyname, gethostbyname2, gethostbyaddr . getnetbyname, getnetbyaddr . getipnodebyname, getipnodebyaddr, getnodebyname, getnodebyaddr = host.conf has been removed from src/etc. rc.network has been modified to warn that host.conf is no longer used at boot time. In addition, if there is a host.conf but no nsswitch.conf, the latter is created at boot time from the former. Obtained from: NetBSD
2000-09-06 14:16:48 -04:00
# not be consulted at all; see /etc/nsswitch.conf for the resolution order.
Initial import of 386BSD 0.1 othersrc/etc
1993-06-20 09:41:45 -04:00
#
#
Backout revision 1.9 that added `myname.my.domain' as another alias for `localhost'. If your /etc/nsswitch.conf has ``hosts: files dns'', and you changed `myname.my.domain' in /etc/hosts to match hostname(1), and you run inetd(8) with the -l option, any connect to `myname' using its real IP address through inetd(8), e.g. `ftp -a myname', will spam your /var/log/messages with: inetd[PID]: warning: /etc/hosts.allow, line 23: host name/name mismatch: myname.my.domain != localhost This is especially bad for -STABLE, where /etc/host.conf defaults to "files first then DNS" resolution order. Noticed by: Igor Kucherenko <kivvy@sunbay.com> MFC after: 1 week
2001-09-29 08:20:08 -04:00
::1 localhost localhost.my.domain
127.0.0.1 localhost localhost.my.domain
Initial import of 386BSD 0.1 othersrc/etc
1993-06-20 09:41:45 -04:00
#
# Imaginary network.
Added reference to RFC 1597 about "private-net" IP#'s. The following numbers will never be routed over the InterNet: 10.0.0.0 - 10.255.255.255 172.16.0.0 - 172.31.255.255 192.168.0.0 - 192.168.255.255
1994-06-03 22:03:45 -04:00
#10.0.0.2 myname.my.domain myname
#10.0.0.3 myfriend.my.domain myfriend
Added RCS Id. Also changed comment to indicate that /etc/host.conf determines when and how this file will be consulted. Added comment to the effect that (1) zero is not a vaild network number and (2) please get a valid network number assigned by your provider or by the Internet Registry.
1993-11-11 17:32:36 -05:00
#
/etc/hosts: Wording changes to better match RFC 1918 Summary: No functional change. Subscribers: imp Differential Revision: https://reviews.freebsd.org/D34391
2022-02-27 23:07:34 -05:00
# According to RFC 1918, you can use the following IP blocks for
# private internets:
Added reference to RFC 1597 about "private-net" IP#'s. The following numbers will never be routed over the InterNet: 10.0.0.0 - 10.255.255.255 172.16.0.0 - 172.31.255.255 192.168.0.0 - 192.168.255.255
1994-06-03 22:03:45 -04:00
#
/etc/hosts: Wording changes to better match RFC 1918 Summary: No functional change. Subscribers: imp Differential Revision: https://reviews.freebsd.org/D34391
2022-02-27 23:07:34 -05:00
# 10.0.0.0 - 10.255.255.255 (10/8 prefix)
# 172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
# 192.168.0.0 - 192.168.255.255 (192.168/16 prefix)
Added reference to RFC 1597 about "private-net" IP#'s. The following numbers will never be routed over the InterNet: 10.0.0.0 - 10.255.255.255 172.16.0.0 - 172.31.255.255 192.168.0.0 - 192.168.255.255
1994-06-03 22:03:45 -04:00
#
/etc/hosts: Wording changes to better match RFC 1918 Summary: No functional change. Subscribers: imp Differential Revision: https://reviews.freebsd.org/D34391
2022-02-27 23:07:34 -05:00
# In case you want to make addresses available on the Internet, you need
- Improve line-wrapping and spacing so as to improve readability. - Add instructions regarding replacing 'my.domain', as this has come up on freebsd-questions. - Remove reference to rs.internic.net/templates, as that directory no longer exists. Instead, encourage them gently to talk to their network provider. MFC after: 1 week
2001-12-11 17:36:10 -05:00
# real official assigned numbers. Do not try to invent your own network
Re-add information for applying for IP space from a registry since that hasn't been included since the ancient rs.internic.net address was removed. Offer the option of the five regional registries. MFC after: 3 days
2003-01-28 16:29:23 -05:00
# numbers but instead get one from your network provider (if any) or
# from your regional registry (ARIN, APNIC, LACNIC, RIPE NCC, or AfriNIC.)
Added RCS Id. Also changed comment to indicate that /etc/host.conf determines when and how this file will be consulted. Added comment to the effect that (1) zero is not a vaild network number and (2) please get a valid network number assigned by your provider or by the Internet Registry.
1993-11-11 17:32:36 -05:00
#
Reference in a new issue Copy permalink