Days since it was DNS

Days since it was DNS(dayssince.itwasdns.net)

32 points by scaglio 2 years ago | 36 comments

xist 2 years ago |

When will this tired meme be retired?

There's almost 300 RFCs related to DNS. It can do many things, and some of them are complex. But human error is almost always the root cause.

Your inability to configure DNS properly speaks more about you, then the service itself.

hi-v-rocknroll 1 year ago | |

I'm also a huge fan of the blog posts that suggest throwing away fundamental technologies and replacing them with half-bakery without understanding the problem domain or the problems that have been encountered and solved before.

zoky 2 years ago |

Ok, since I’m obviously not nerdy and/or cynical enough to get the joke, what exactly is wrong with DNS? None of the links seem to indicate what exactly the problem with it is.

EricE 2 years ago | |

It's not DNS. There's no way it's DNS. It was DNS.

https://medium.com/adevinta-tech-blog/its-not-always-dns-unl...

dang 2 years ago | | |

Discussed here:

It's not always DNS, unless it is - https://news.ycombinator.com/item?id=38719126 - Dec 2023 (73 comments)

cwicklein 2 years ago | |

I think it’s implied that it’s been zero days since the underlying cause of some such problem turned out to be DNS related. The number zero being hard coded implies that the root of the problem is always DNS. But, let’s give MTU its due.

fffrantz 2 years ago | | |

Lately, MTU has gotten up my list of things to check when stuff goes down.

It seems carriers can't get their MTUs straight as of late, especially on MPLS links...

I really thought we had this figured out 20 years ago...

justsomehnguy 2 years ago | |

Two days ago one (!) User reported they got \\contso.com\dfsroot\profiles\user inaccessible (with errors loading the desktop etc).

For me the path was accessible, logging on the same server proved the path was accessible, 3 hours of the proper troubleshooting confirmed everything should work. But yet.

Skipping short the circumstances, one of (the 6 total) DCs decided what... DNS server isn't worth running. And for this one user DFS (last changed at least two years ago) decided to fall back to the file server from 2018, which, of course, pointed the DFS target to a no longer existant share.

Of course it wasn't DNS in this case. It was the DNS in this one.

xist 1 year ago | | |

DFS-N != DNS

a.) lack of monitoring for running services b.) cruft/old configurations

linuxdaemon 2 years ago | |

As someone who administers DNS servers, I'm going to guess this is due to DNS being the first thing that gets blamed when something goes wrong; and it is almost never DNS.

scaglio 2 years ago | | |

That's the point, but often in many network issues, the name resolution is the root cause of the problem. Not necessarily the DNS itself. Sometimes the /etc/hosts is more than enough to cause headaches!

EricE 2 years ago | | |

Ha!

https://9gag.com/gag/avOj8WE

erikw 2 years ago | |

A DNS misconfiguration is often the root cause of an issue. Hence the saying “it’s always DNS”.

dervjd 2 years ago | |

"It’s always DNS" is basically tongue-in-cheek expression, because DNS issues are so frequently the cause of weird outages.

Almost anything you do on the internet (or local network) depends on DNS functioning correctly. DNS can get complex quickly - multiple servers (caching/authoritative/recursive) and protocols = lots of opportunities for something to be misconfigured. Cached entries in particular can be a nightmare if something gets outdated - it takes time for an update to a DNS record to propagate to all the other DNS servers on the Internet. All kinds of other random services etc depend on DNS records being correct and DNS working. When there’s an issue it’s not always immediately apparent that a DNS problem is the root cause, leading to lots of time chasing your tail/tearing your hair out trying to figure out what the heck broke.

xyst 2 years ago |

I was setting up my own mail server the other day and re-realized how long global DNS propagation really takes.

I’m in the US so it was almost instantaneous between updating the dns records in domain register any being able to verify the changes with my own rDNS server.

But using a UK or NL dns server didn’t immediately pick up those recent changes.

Had to wait an additional 48 hrs for global dns propagation.

nevir 2 years ago |

I hope it's also reported as a DNS record

gmuslera 2 years ago |

NTP, BGP, MTU and a lot of other acronyms should be also in the list of not trivial to trace root cause for things that goes from big outages to mysterious malfunctions, specially if there are many parties or servers involved. And the security protocols that are above those and more (DNSSEC, SSL, etc).

amacd31 1 year ago | |

I'd been meaning to/thinking about setting up a page for BGP, so here we go: https://itlookedlike.itwasdns.net/but-it-was-bgp/

hi-v-rocknroll 1 year ago | |

Shit can and must be troubleshooted with domain-specific tools.

DNS: I do have an ongoing problem specific to Unbound where it refuses to serve some entries in a transparent zone of DHCP-registered addresses that have written to config files properly but it insists on refusing to resolve certain hosts nondeterministically. But that's the only problem I have had in a long while because mostly infrastructure works out of necessity and scale.

byteknight 2 years ago |

Love the hard coded 0

Yasuraka 2 years ago | |

It goes up whenever you can't reach it

byteknight 1 year ago | | |

That would be opposite

EricE 2 years ago | |

Yup - nothing to compute!

Tijdreiziger 2 years ago | | |

Now that’s what I call optimization.

geerlingguy 2 years ago |

This would pair up well with my favorite t-shirt ;)