-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for SRV records [dns] #43
Comments
Maybe not a SRV record, which has a specific format not entirely applicable (PORT, WEIGHT, PROTO, PRIORITY) but maybe a TXT record with a specified format, similar to SPF (Sender Framework Policy). I've been thinking of this as well. user@domain.com assumes the Lightning URL will reside on the A record for domain.com. But similar to MX, you may want to have that data reside somewhere else. DNS is a more flexible place to specify where the LN URL data will reside or even what it is. |
This (a TXT field) would be a significantly better plan as far as I can see than .well-known; I'd welcome it if it's a possibility. |
Hi,
I'm not sure if this is the right place, but I was wondering if there is support for srv records.
The use case is an already existing domain with a bunch of services and a separate server that runs
lnd
andsatdress
for example.SRV _lightning-address._tcp.example.com --> points to --> mySatdress.otherserver.tld
The text was updated successfully, but these errors were encountered: