DNS by port number...
konrad.roeder at gmail.com
Sun Apr 9 19:25:13 PDT 2017
I don't get what the additional IP addresses buy you. Why do you want to
waste IP addresses?
The UDP and TCP ports are in the same machine, but in layer 4-7 ...
different transport and applications.
http:// should translate to port 80
ftp:// should translate to port 21
ssh:// should translate to port 22
telnet:// should translate to port 23
On Sun, Apr 9, 2017 at 1:12 PM, Bill Vodall <wa7nwp at gmail.com> wrote:
> Another great idea of mine - that somebody has probably thought of
> before. But does anybody here know if and where it's been thought of
> We all know DNS A records - give a name and get an IP address back.
> For years (really!) I've wondered how that magic extends to give a
> name and get both an ID address - and - a port number back. Thanks to
> (Happy BDay) John H and his Ham DNS presentation at uHams - I now know
> about SRV and LOC DNS records. Awesome cool stuff.
> Butt.... (there's always one ain't there....)
> I want to take it a step further. I want to vary the IP address
> returned from a DNS query dependent on the port number I give it.
> For example:
> www.findewe.ham -> returns IP 126.96.36.199
> findewe.ham -> returns IP 188.8.131.52
> findewe.ham:14580 -> returns aprs.findewe.ham == IP 184.108.40.206
> findewe.ham:443 -> returns linlink.findewe.ham == IP 220.127.116.11
> Has anybody heard of some such magic?
> Thanks and 73,
> Bill - WA7NWP
> PS. Sure - 14580.findewe.ham could be mapped to IP 18.104.22.168 - but
> that's not as cool as having one
> seatcp mailing list
> seatcp at wetnet.net
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seatcp