I'm trying to make sense of something I've been seeing and hope someone here can enlighten me.
Lookalike domains are nothing new. It's been common to see something like gооgle[.]com ( note the Cyrillic 'о' characters instead of the Latin 'o' expected in google, encoded as 'xn--ggle-55da[.]com' ) to appear to be google[.]com . Lately, I've been seeing things like google[.]cоm ( note the Cyrillic 'о' in 'cоm' instead of the Latin 'o', encoded as google[.]xn--cm-fmc ).
What is the point of the lookalike TLD? It's not going to publicly resolve anywhere, right? It seems like it's likely to be a typo. If a TA was using the impersonated domain's infrastructure and mistyped the TLD, the targets won't resolve and it's game over. If the typo is from a legitimate representative of the accidentally impersonated domain, then it's just an oops. No harm, no foul.
Am I missing something here? It seems like it's simply a typo happening multiple times, but I don't want to assume just because I don't understand the potential.
Simdzone, our super fast #DNS zone file parser, will be maintained as a standalone project. We now took another step towards a releasing as part of NSD with support for makefile based builds. https://github.com/NLnetLabs/simdzone/issues/11
Is there really no #Linux#firewall that can allow or block FQDNs or domains?
iptables doesn't do it, and #ufw is just a frontend for #iptables. What else is out there for #Debian based machines?
For context: I've been around Linux since the days of ipchains. I know the #OSI model and run my own #DNS servers (primary, secondary, and resolving/caching) so there's no need to explain why this feature is non-trivial to implement
Most other OSes have this feature and it's pretty reasonable to want
Internet.bs domain name registration price increase announcement:
"[...] we have faced the challenges of inflation and escalating supplier expenses. Although we have absorbed some of the price hikes from our providers in the past, our costs have continued to surge. [...] we need to modify our domain pricing."
Jeroen is working on an individual #IETF Internet-Draft "Zone file format". The document aims to remove ambiguity from the master file, or zone file, format originally specified in RFC1034 and RFC1035. #DNS#OpenStandards#OpenSource
Awwww yah, I'm speaking @BSidesCharm again this year! But this time around I'll be joined on stage by @JimSycurity, and I could not be more psyched. We'll be talking about the unholy couple that is Active Directory and DNS.
It looks like https://ns-global.zone/ is serving 558 domains at the moment. I am the most amused that we are one of the authoritative DNS servers for the Internet Archive. #DNS#networking#selfhosted