Nick Danger · @niqdanger
50 followers · 312 posts · Server social.linux.pizza

Ticket - "Can't connect to host using DNS" ... Investigation - changed hostname, changed IP and put neither in DNS. Yup, that would do it.

#itwasdns

Last updated 1 year ago

TimedIn :verified: · @timedin
25 followers · 243 posts · Server mastodontech.de

TimedIn.net war down

#itwasdns

Last updated 1 year ago

Seth · @saluki
55 followers · 139 posts · Server fosstodon.org

WiFi at this holiday cottage wasn't working.

#itwasdns

Last updated 1 year ago

@dcid UPDATE: it was a DNS issue. blocks noc.social (my other devices use quad9 which is why they worked)

#itwasdns #bt

Last updated 2 years ago

Christoph Jahn · @road42
69 followers · 148 posts · Server mastodon.green
Doc Edward Morbius โญ•โ€‹ · @dredmorbius
2353 followers · 15548 posts · Server toot.cat

@n8chz If I'm understanding you correctly, your telephone number is a "some character string", though composed (usually, not always) of numbers.

URLs evolved from domain names plus a local path component and additional arguments or values. The domain-name system mapped logical network locations (IP addresses) to mnemonic identifiers, and provided routing through them. I remember using bang-path notation to route email, briefly, in the 1980s, prior to this being fully hammered out.

(Bang paths specified the routing instructions for email between two points, something that's now handled automatically.)

Note that DNS and host names are mappings to but also independent of the underlying network topology. I can have, say, "example.com" as a domain, but hosts "local.example.com" and "remote.example.com" be located at two distinct networks, with no underlying logical network location. It's also possible to specify "service addresses" such as "mail.example.com" and "ftp.example.com" which refer to specific protocols (email and FTP respectively, "WWW" is another of these though it's largely been dropped). Or subdomains, so that host.lon.example.com and host.nyc.example.com might correspond to sub-networks in London and New York, where "lon.example.com" and "nyc.example.com" are subdomains.

And there's a whole lot of other detail.

When DNS first started there were literally a few hundred, maybe a few thousand, internet hosts let alone domains, and the directory was printed, with the system operator's names and phone numbers in it twice (forward and reverse lookup), updated and distributed regularly.

There are now billions of hosts (devices), ranging from supercomputers to electronic doorbells and drones, and at the very least millions of domains. Management is ... more complicated than it once was.

Sorting out what namespaces should map to what address schemes is complex, and as anyone who's attempted ontologies and rational organisational schemes, there's no one solution, and correspondence of use to design intent tends to rapidly diverge over time.

It's complicated.

@dansinker

#dns #itsnotdns #thereisnowayitsdns #itwasdns #itscomplicated #historyoftheinternet

Last updated 2 years ago

RT @geerlingguy
@UnderEu @ControlDNS

#itwasdns

Last updated 2 years ago

@minecraftchest1@wp.arsrobotics.org
The main page is back up again! After deleting the record in Cloudflare, waiting about twenty minutes, and readding it, arsrobotics.org now resolves correctly. Now to setup WordPress on that domain.

#itwascloudflare #itwasdns

Last updated 2 years ago