VazScep wrote:The best error code you can get is 418, which means "I am a teapot", and is sent in response to a request to brew coffee according to HTCPCP.

Cito di Pense wrote:

VazScep wrote:The best error code you can get is 418, which means "I am a teapot", and is sent in response to a request to brew coffee according to HTCPCP.

This is an iOT concern, isn't it?

1. Rationale and Scope

There is coffee all over the world. Increasingly, in a world in which
computing is ubiquitous, the computists want to make coffee. Coffee
brewing is an art, but the distributed intelligence of the web-
connected world transcends art. Thus, there is a strong, dark, rich
requirement for a protocol designed espressoly for the brewing of
coffee. Coffee is brewed using coffee pots. Networked coffee pots
require a control protocol if they are to be controlled.

Increasingly, home and consumer devices are being connected to the
Internet. Early networking experiments demonstrated vending devices
connected to the Internet for status monitoring [COKE]. One of the
first remotely _operated_ machine to be hooked up to the Internet,
the Internet Toaster, (controlled via SNMP) was debuted in 1990
[RFC2235].

The demand for ubiquitous appliance connectivity that is causing the
consumption of the IPv4 address space. Consumers want remote control
of devices such as coffee pots so that they may wake up to freshly
brewed coffee, or cause coffee to be prepared at a precise time after
the completion of dinner preparations.

VazScep wrote:

crank wrote:I'd recommend not using your ISPs for various reasons.

Can I hear them?

VazScep wrote:The best error code you can get is 418, which means "I am a teapot", and is sent in response to a request to brew coffee according to HTCPCP.

Cito di Pense wrote:I like that. Coffee brewing is an art. Sort of like long-distance target shooting.

1998? Yes, that makes sense. It reminds me of some of the jokes in the original Unix fortune package, mainly the Dave Barry stuff somebody collected. That guy is a riot.

http://www.jr.co.il/humor/read.txt

crank wrote:OK, one reason ISP DNS servers can be slower

It gives them that much more ability to monitor and control

They can block access to some URLs for whatever reasons

There's probably more but that's all that pops at the moment.

I really recommend everyone running DNSCheck, it's likely you'll find significant improvements in your DNS performance if you use the data from its tests.

Cito di Pense wrote:http://www.jr.co.il/humor/read.txt

jamest wrote:Thanks for the earlier explanations, Cali and VazS. I wish I could motivate myself to learn more about this computer-stuff malarkey, but it's never really been my cup of tea.

VazScep wrote:

jamest wrote:Thanks for the earlier explanations, Cali and VazS. I wish I could motivate myself to learn more about this computer-stuff malarkey, but it's never really been my cup of tea.

Would you like computer-staff malarkey here or there?

The_Metatron wrote:Some good treatments of this problem in this topic. DNS servers go down all the time. On my network for the moment, my gateway router is using my ISPs DNS servers. I haven't noted any instability yet. If I do, I usually swing over to OpenDNS. There are other commercial DNS servers that usually work well, too. 4.2.2.2, and 4.2.2.1 come to mind. I can't remember who owns them, but I found a neat article that covers their history.

Some ISPs block connections to other DNS servers that aren't their own, but I've never seen that.

I'd recommend going with either OpenDNS, or perhaps Google's DNS at 8.8.8.8 or 8.8.4.4, if this instability continues.