ucomp No. Browser cache has nothing to do with domain resolution of non-existent names and what appears in the address bar.
Hi,
O.K., lets shot a light in the magic :
One could only know what probably happened at balanga when he wrote
that a magician was at work who solved all .
The information from the initial posting was not clear -
if balanga would have known what was really happening he wouldn`t have asked ...
domain resolution of non-existent names...
if the
A-Record wouldn't have set by "the Magician" and wouldn't exist,
the Magician would have had no chance, but he succeeded.
So the name exists but didn't appear in the address bar because of
DNS propagation time and/or Browser-Cache.
Of course, we do not know exactly in which order or combination, because we are not sitting next to balanga and probably even balanga doesn't know or remember.
but that doesn't matter...
... if you've done server-setups approx. 50.000 times, you know that when you first set up a web server, you're dealing with dns propagation time , browser cache & WebServer-Configuration(proxies, folders, symlinks and so on and so forth...).
Since balanga didn't touch the configuration-files (from what he wrote/told) and only the Magician was at work-
it was clear what happened , because that are always the same procedures...
so a web-dev has to deal with Cache-control, not only on the client-side but also on the sever-side ... but that's another topic, not for today.. but just to turn off the light in magic right away ;-) :
Session-lifecycles/management , parameter, getter/setter, proxy-server, EcmaScript, Ajax, CSS , node , json, Python, java servlets, tomcat, certbot ...
happy coding !
O.K, thanks for reading,
good night
P.S:
----
Of course, I assume that abc.xyz was just a nick for an actual domain with a different name owned by balanga.
If that's not the case and this has been an offline fake test, we can forget this thread, but I guess it was a real Sevrer scenario that balanga described ...
apart from this : abc.xyz is a
FQDN...
---