IBDNS: Intentionally Broken DNS server
11–20 of 30 posts
Re: IBDNS: Intentionally Broken DNS server
#12Very happy to see another Elixir application doing work.
Re: IBDNS: Intentionally Broken DNS server
#13Very happy to see another Elixir application doing work.
Writing servers like this is a joy using Erlang and OTP. I assume the same holds for Elixir though I have not used it.
Elixir to some extent is just syntactic sugar on top of Erlang.
Elixir is to Erlang as Kotlin is to Java. At the end of the day, it's the same thing. There are some conveniences added, like less verbose ways to deal with GenServer or other abstractions on top of it - but all-in-all it is pretty similar aside from the syntax parts.
You might consider taking it for a spin.
Re: IBDNS: Intentionally Broken DNS server
#14The purpose of this tool is testing if a domain name system follows (or does not follow) the correct specifications: IBDNS fills a gap in the universe of DNS test tools by offering the possibility of deviating intentionally and on demand from the DNS specifications, and thus simulating incorrect behaviour of authoritative name servers.
Re: IBDNS: Intentionally Broken DNS server
#15Also, for the love that all that is holy, some ISP DNS servers just break if you try using ipv6 only which is just saddening.
Re: IBDNS: Intentionally Broken DNS server
#16Re: IBDNS: Intentionally Broken DNS server
#17Re: IBDNS: Intentionally Broken DNS server
#18/s
Re: IBDNS: Intentionally Broken DNS server
#19Re: IBDNS: Intentionally Broken DNS server
#20Somewhat related....I think that while fiber needs to become faster and more affordable and accessable, the other big factor is speed is the latency in DNS. DNS is such a pain to troubleshoot personally,and factors like how fast DNS takes plays a big role in network speed. Also, for the love that all that is holy, some ISP DNS servers just break if you try using ipv6 only which is just saddening.