4 ms·
> My website was missing. In fact, the domain name resolved to an IPv4 address I was unfamiliar with. Do you guys know this stuff? If my domain started resolvi
by wodenokoto 7y ago
> My website was missing. In fact, the domain name resolved to an IPv4 address I was unfamiliar with.
Do you guys know this stuff? If my domain started resolving to a new IP address, that would be just as unfamiliar to me, as the current address.
Should I ping my domain and write the results down?
- aasasd 7y agoNormally, if you did any setup before pointing the domain to the host, or if you connect via ssh, then you at least have seen the ip and probably have it recorded in files like ~/.ssh/known_hosts. But generally, the better your setup is documented, the better you can detect or diagnose when something goes awry.
- antsar 7y agoI might not recognize the address. But `whois 12.34.56.78` will tell me whose network it's on. Anything other than my hosting provider would be a red flag. If it's the right company but the site still looks wrong, I'd try to SSH, which would fail because known hosts (see adjacent comment) and also authentication would fail. Then I'd reach for the VM console inside my hosting provider's site, and see the correct/expected address there, and hopefully realize what's up. You could also check your DNS provider, assuming that hasn't been compromised. It can be a good tradeoff to know where/how to find information rather than actually knowing the information.
- dredmorbius 7y agoIf you have a small infrastructure, knowing your IPs is useful. For a larger one, the netblock(s), ASNs, or hosting. provider / region.
- unethical_ban 7y agoI tend to know recognize the networks my servers are on, because I only have one or two.