0

I've got a quite common question, which I can't find an answer for.

Is it possible to create a SRV Record for any possible service I'm running? For example: I want webinterface.example.com to redirect to example.com:1234

The corresponding SRV record would be _WebInterface._TCP IN SRV 1 255 1234 example.com.

We've set up something similar but it's not working as intended.

closed as off-topic by user36472, Ron Maupin Jun 28 '18 at 13:58

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "NE is a site for to ask and provide answers about professionally managed networks in a business environment. Your question falls outside the areas our community decided are on topic. Please visit the help center for more details. If you disagree with this closure, please ask on Network Engineering Meta." – Community, Ron Maupin
If this question can be reworded to fit the rules in the help center, please edit the question.

  • Are you sure the application uses the SRV record? You can put anything you want in the DNS it then needs to be specifically requested for by some application. And web browsers specifically do not use SRV records.... – Patrick Mevzek Jun 28 '18 at 13:35
  • Unfortunately, questions about protocols above OSI alyer-4 are explicitly off-topic here. You could try to ask this question on Server Fault for a business network, or on Super User for a personal network. – Ron Maupin Jun 28 '18 at 14:03
0

Is it possible to create a SRV Record for any possible "service" I'm running?

Yes

The corresponding SRV Record would be "_WebInterface._TCP IN SRV 1 255 1234 example.com"

I'd personally reduce the size of the service name to _httpd._tcp.company.local

Questions? RFC 2782 is a good resource and includes a fictitious example on page 7.

  • It is not a question of size, the first underscore field is the service as defined in iana.org/assignments/port-numbers (/etc/services in Unix systems), so it is not a freeform value. The second underscore field is hence _udp or _tcp. – Patrick Mevzek Jun 28 '18 at 13:42
  • I didn’t say size was an important issue – Mike Pennington Jun 28 '18 at 13:43
  • You wrote: " I'd personally reduce the size " :-) the problem is not size at all.... _WebInterface is not among the list of services defined in IANA registry hence invalid, so it should be _http probably in this context. Which is shorter indeed but this is only a side effect. – Patrick Mevzek Jun 28 '18 at 13:48
  • Your understanding of English isn’t terribly refined in this case. Expressing a personal preference in no way means it should be important to the reader (or anyone else). A personal preference is just me saying what I like – Mike Pennington Jun 28 '18 at 13:50
  • BTW there is no mention of service records conforming to the IANA registry in the RFC. How did you decide that’s important to SRV records? – Mike Pennington Jun 28 '18 at 13:58

Not the answer you're looking for? Browse other questions tagged or ask your own question.