Opened 12 months ago

Last modified 3 months ago

#632 new enhancement

devhack.internal?

Reported by: m Owned by: m
Priority: major Milestone:
Component: Diplomacy Keywords:
Cc:

Description

I'm kind of warming up to trying out a devhack.internal subdomain for our internal services. eg homeassistant.devhack.internal points to hass VM IP addr,gatekeeper.devhack.internal points towards the ESP32's IP address, etc

I think I can run my own DNS / rootserver to enable this to happen. Can someone configure our top level DNS server to point *.devhack.internal requests to a specific IP?

Change History (9)

comment:1 by m, 12 months ago

I understand this is functionally equivalent to core.devhack.net (or int.devhack.net??). I'm not too interested in arguing out the upsides or downsides to doing it different ways, just looking to extend existing functionality to try it out.

comment:2 by m, 10 months ago

maybe we can just do <name>.internal tbh. idk

comment:3 by m, 5 months ago

ppl keep getting confused when int.devhack.net URLs 404.

comment:5 by m, 4 months ago

whatever we choose for this should probably be accessible from the outside so that we can list a page that says "you need to be on the devhack internal network to access this page"

comment:6 by m, 4 months ago

devhack.network?

comment:7 by m, 3 months ago

amber doesn't like devhack.network because it is close to devhack.net

I don't know of a better one to use?

comment:8 by m, 3 months ago

also, haven gone down this path a little:

something that supports hostnames via dhcp requests is a must. something that supports hostnames via other avenues like RFC2136 or whatever is very nice. dynamically requesting domain names and stuff. also just pulling from config files is cool too.

BIND does all of this, powerdns might too?

I should set up a reproducible deploy of the bind server. on lxc perhaps?

comment:9 by m, 3 months ago

related / I'm accidentally crossposting to: #828

Note: See TracTickets for help on using tickets.