Unable to ping a new already working domain until reboot
Summary
On a server that I manage, which already had a working website with domain example.com
(obviously that's not the actual domain), I configured a subdomain newsubdomain.example.com
(that's not the real subdomain name either) within the same domain. Meaning that I added the A
and AA
DNS records and created a separate virtual host. This subdomain happened to be hosted on a different server, but I'm pretty sure that's irrelevant.
After I set everything up, I checked the following:
- the new subdomain records had propagated to the entire world according to https://www.whatsmydns.net/
- I checked at https://dns.google/query that the new subdomain was visible by Google's DNS
- the webs servers for both the original domain (which had already been working before) and the new subdomain were both working (which is also confirmed by the following two points)
- I asked a coworker to access http://newsubdomain.example.com from their computer from my same country and it was accessible
- I checked from a third unrelated host that I could
wget http://newsubdomain.example.com
So, on my Manjaro local computer, I tried opening http://newsubdomain.example.coom in Google Chrome, and it failed with ERR_NAME_NOT_RESOLVED
; so I also tried to ping the subdomain from a terminal and it also failed.
I changed my network configuration to use Google's DNSs 8.8.8.8
, disconnected and reconnected to the network; retried and it kept failing.
So I rebooted, and sure enough, it could access the domain.
It's very likely (I'm almost sure) that I had also tried and (expectedly) failed to access the subdomain before I set it up. So maybe the failure response from some DNS had been cached somehow. I certainly had accessed the root domain before.
Version affected
1.44.2-3 on Manjaro Linux
Steps to reproduce
see Summary Should be something like this:
- try to ping a subdomain that isn't reachable, whose root domain is reachable
- also ping the root domain for good measure
- set up the server so that the subdomain is reachable
- make sure the DNS information has propagated, that the subdomain is indeed reachable
- make sure your local network is set up to use a DNS server that does know about the subdomain
- disconnect and reconnect physically to the local network
- try again to ping the subdomain
Actual result
- the subdomain is still unreachable until reboot
Expected result
- the subdomain should be reachable without needing a reboot.
Note: I create new domains all the time almost on a daily basis, and never had this issue. MAYBE this is specific to the situation where a subdomain becomes reachable, which belongs to a root domain that was already previously reachable. But I'm just speculating.
Relevant logs
(Please see the DEBUGGING section of "man NetworkManager" and attach any relevant log)
"By default, NetworkManager logs are not verbose and thus not very helpful for investigating a problem in detail" Well then I'm afraid it's too late for that