LAN: IETF reserved domains (.lan, .home, ...)

[kafene]

I see .local is already covered by this list.

There are some additional reserved domains for local usage. For example my router is mapped to router.lan on my network.

https://tools.ietf.org/id/draft-chapin-rfc2606bis-00.html#new

So ideally it could allow local access from these top-level domains:

• .local
• .localdomain
• .domain
• .lan
• .home
• .host
• .corp

[ghost]

This is an expired draft and these TLDs are not reserved except for .local.

[kafene]

Ah, you're right. Well it's okay, I have uBlock disabled on my router management page anyway.

It does mention 4 other reserved TLDs that are not in draft - .test, .example, .invalid and .localhost.

[ghost]

I just pointed out your mistake. I don't know if @gwarser would consider it important that they are not reserved.

[gwarser]

I need to read about it when I will have free time.

[gwarser]

So ideally it could allow local access from these top-level domains:

I should rather block these to prevent scanning such devices.

[salim-b]

OpenWrt's default DHCP server dnsmasq appends .lan to all configured hostnames by default, so blocking these pseudo TLDs would be cool!

This is an expired draft and these TLDs are not reserved except for .local.

Similar sets of pseudo TLDs are mentioned in other RFCs, too, see e.g. this serverfault answer.

Relevant excerpt from RFC 6762 Appendix G. Private DNS Namespaces:

We do not recommend use of unregistered top-level domains at all, but should network operators decide to do this, the following top-level domains have been used on private internal networks without the problems caused by trying to reuse ".local." for this purpose:

  .intranet.
  .internal.
  .private.
  .corp.
  .home.
  .lan.