0
I'm running OSX 10.12.6 and I've added some packages using Homebrew including components to run a local LAMP stack. For some reason, when I attempt to visit https://archive.is, the .is extension resolves locally and it sends me to my localhost's web root.
I've checked everything I can think of, including DNSMasq and its resolvers, but I haven't been able to spot why that extension resolves locally.
There is nothing in /etc/hosts relating to ad blocking, parental blocking, or .is specific entries and dig isn't indicating any local lookups.
How can I trace the DNS lookup on my machine to see where it's being resolved locally?
cfx
Posted 2019-09-24T12:40:57.977
Reputation: 101
you can use dig with the trace option, see here and dont forget to check /etc/hosts
– Zina – 2019-09-24T12:46:31.900Have you installed any
/etc/hosts-based ad-blocking or parental-blocking entries? – user1686 – 2019-09-24T13:32:52.513Nothing in
/etc/hostsrelating to ad blocking, parental blocking, or.isspecific entries. Added this to my original question for clarity anddigisn't indicating any local lookups. – cfx – 2019-09-24T13:34:17.737What does
scutil --dnsreport? What do you get if you query archive.is fromdns-sd? What apps or tools were you using to try archive.is before? Please note that Chrome, Firefox,nslookup,dig, andhosteach bring their own DNS resolver code and thus do things differently from most of macOS and may get different results. – Spiff – 2019-09-24T15:49:31.773what happens when you stop all LAMP services? – Zina – 2019-09-24T21:48:31.003
@Zina great question, Chrome gives me
ERR_CONNECTION_REFUSEDand FF/Safari give me similar "unable to connect" errors. – cfx – 2019-09-24T22:33:39.413that is strange, I tested the link and it opened the web archive site, so you must have something else (outside of LAMP) which is not allowing you to connect to the site. could you check with
lsof -nP -i4TCP:443 | grep -i listenwhat process is listening on 443? – Zina – 2019-09-26T21:52:00.207