Reserving .INTERNAL for Private-Use Applications | Lobsters

37

Reserving .INTERNAL for Private-Use Applications networking icann.org
via lcapaldo 7 months ago | caches
Archive.org Archive.today Ghostarchive
| 8 comments

8

1. 14
  
  FRIGN 7 months ago
  
  Whereas whereas whereas whereas whereas whereas whereas whereas whereas
2. 6
  
  hauleth 7 months ago
  
  Now make .localhost always point to loopback, and I will be happy.
  1. 3
    
    freddyb 7 months ago
    
    I wonder whatever happened to https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-let-localhost-be-localhost? I think some browsers may have adopted it anyway? (not sure and on monbile)
    1. 2
      
      hauleth 7 months ago
      
      I do not know about browsers, but systemd-resolved implements this. I wish that other OSes would do so as well, so I would not need to run DNSmasq locally on macOS for exactly that purpose.
  2. 1
    
    sknebel 7 months ago
    
    https://datatracker.ietf.org/doc/html/rfc6761#section-6.3 ?
3. 4
  
  lorddimwit 7 months ago
  
  Having it written as .INTERNAL makes my brain immediately treat it as a binary segment name for some reason. I don’t know why.
4. 2
  
  duncan_bayne 7 months ago
  
  There was a missed opportunity here to define .INTERCAL the same way.
  1. 2
    
    recursion 7 months ago
    
    ICANN’s plan is to define .INTERCAL to route to all IP addresses not explicitly excluded.