You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 and satdress for example.
SRV _lightning-address._tcp.example.com --> points to --> mySatdress.otherserver.tld
The text was updated successfully, but these errors were encountered:
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. [email protected] 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.
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: