Hi there, I registered the Domain localdns dot me and set two A-Records (pure domain + wildcard) to point to 127.0.0.1. Sadly the A-records for the local IP address do no longer work. I faced the same problem for the localtest dot me Domain (a previous prominent example that was used by developers).
I was googling until my fingers bleed, to figure out, if there had recently been a global change of no longer accepting 127.0.0.1 A-Records on public DNS Servers, but I can’t find anything.
So the records are already pass through, no proxying.
Anyways, there seem to be multiple Domains offered, that are pointing to 127.0.0.1 (e.g. localtest dot me), which are all not working from my machine.
Also asking nslookup dot io, I don’t get the records displayed (same of course, when using nslookup from my local macine - macOS).
That’s why I’m asking myself if there was a general rule applied to the global DNS System, that on most DNS systems does not promote any 127.0.0.1 A records any longer-
Check your local resolver or firewall isn’t blocking queries that return a private IP address. Strictly a public DNS should not return private IP addresses so many resolvers will filter these out for safety; the one on my LAN does for example (returning 0.0.0.0).
That’s a good advice, I need to figure out, how that get’s blocked within my mac (or even in the router). Anyways, does anyone have an explanaition, why nslookup dot io is also not showing any records here?
nslookup dot io is a service, where you can enter the domain and get the nslookup response displayed. It simply does not show any A records for 127.0.0.1 - but it seems, in my home network, the error is raised by a default filter of my router. That was a very good advice.
Click on the Settings icon () in the right side above the content block.
Enable “Show raw data”.
It will then change from:
→
So, it seems like it actually works on that nslookup.io site as well.
They are just not displaying it, unless you select “Show raw data”.
It is a common practice these days to filter away certain private / reserved IP address spaces, as an attempt to prevent DNS rebinding attacks.
Could be a similar filter that nslookup.io has made on purpose, or some library that they use to parse the raw data, which ignore private / reserved IP address spaces, or similar.
Some additional advice:
One or more of the tools you’re trying, could actually be of bad quality, have temporary issues, or similar things, which makes it look like your domain may have issues, even if it doesn’t.
I would therefore strongly advice that you don’t stick to one single DNS lookup service / DNS propagation checker, but try a few, when / if you see issues.
) in the right side above the content block.
