uklans/cache-domains

lookup to 77.68.81.103

Opened this issue · 1 comments

Y9fK commented

Hello!
I turned the lancash around. If I request to the dns server of the lancache directly, the response is the cache's ip-address. However, if I do a forward on my primary dns server, the lancache responds with the ip address 77.68.81.103
inetnum: [77.68.80.0 - 77.68.87.255
netname: UK-NGCS
org: [ORG-FHL1-RIPE]
descr: UK Next Generation Cloud Server (NGCS)

My primary dns server has a real ip-address.
When does the dns server lancaсhe respond with this address?
Thank you

sjt5 commented

This (non-obvious) issue is because *.cache.lancache.net (inappropriately IMO) resolves on the global Internet.
On your DNS server a Domain Override needs to be created for:

cache.lancache.net

Pointing to your lancache-dns server IP.
(lancache server 192.0.2.2)
(non-lancache DNS server 192.0.2.1)

Improper configuration:

C:\Users\SomeUser>nslookup uplay.cache.lancache.net
Server:  yakko.somelan.lan
Address:  192.0.2.1

Non-authoritative answer:
Name:    uplay.cache.lancache.net
Address:  77.68.81.103

Proper configuration:

C:\Users\SomeUser>nslookup uplay.cache.lancache.net
Server:  yakko.somelan.lan
Address:  192.0.2.1

Non-authoritative answer:
Name:    uplay.cache.lancache.net
Address:  192.0.2.2

Would be awesome if whomever owns/runs the webserver for cache.lancache.net would add a custom HTTP header pointing to lancache documentation or something giving those troubleshooting a clue bat instead of simply 404'ing every HTTP/HTTPS request. ):

Hope this post helps others scratching their head with this issue.

  • 👍2