#Nameserver
LightNews LightNews
jaba.hosting
Tipp: Nameserver ändern Sie im Kundenlogin selbst. Vorher beim neuen Anbieter alle Einträge (A, MX) anlegen, sonst laufen Website und E-Mail nicht. https://www.jaba.hosting/ufaq/wie-aendere-ich-die-nameserver-meiner-domain/
Grafik in JABA-Blau: Nameserver ändern. Im Kundenlogin selbst, E-Mail-Einträge nicht vergessen.
November 5, 2026 at 9:00 AM
dokape.de
so wie immer vom Macbook aus via speedtest.net

Das macht die üblichen 250/25 im Normalfall.
Außer Vodafone hat im Cable wieder irgendwelche Misconfigs wie kaputte Nameserver.

Modem hat 1 Upstream und 20 Downstreams gefunden.
October 29, 2026 at 9:30 PM
forum.infinityfree.com.web.brid.gy
When the site will open?
status.infinityfree.com ### DNS resolution issues in us-west | InfinityFree Status Identified - The issue has grown: none of our nameservers are responding from our us-west monitoring location. This suggests the nameserver location serving that part of the world is down. Websites may be unreachable for visitors in the affected... If you live there, wait until it’s fixed.
forum.infinityfree.com
November 1, 2026 at 5:42 PM
forum.infinityfree.com.web.brid.gy
Website Not Accessible Even Though Hosting Account Is Active (Free Hosting)
NS is down worldwide, wait for a while status.infinityfree.com ### DNS resolution issues in us-west | InfinityFree Status Identified - The issue has grown: none of our nameservers are responding from our us-west monitoring location. This suggests the nameserver location serving that part of the world is down. Websites may be unreachable for visitors in the affected...
forum.infinityfree.com
November 1, 2026 at 5:41 PM
tristanjodsalz.bekanntefreunde.de
Ok it worked now! One nameserver was not reachable via one address so that might have been the problem.
Thank you very much!
October 27, 2026 at 8:05 PM
mackuba.eu
DIDKit for Ruby v. 0.5 is out:
Breaking changes: the ATProto spec now says that if there are multiple handles in a document, only the first one should be checked bi-directionally and the rest should be skipped: updated get_verified_handle to match this; removed Resolver#first_verified_handle. PLCImporter::PLC_SERVICE moved to DIDKit::DEFAULT_PLC_DIRECTORY DID::GENERIC_REGEXP moved to DIDKit::GENERIC_DID_REGEXP Resolver#nameserver changed to read-only Resolver#resolve_handle & DID.resolve_handle now verify the handle bi-directionally, checking also if the DID has that handle assigned too; pass verify: false to skip this. Added: added support for decoding signing keys – Document#signing_key, PLCOperation#signing_key & DIDKit::PublicKey. Resolver now accepts a plc_directory option that lets you use a PLC mirror server instead of plc.directory. added a shared DIDKit.default_resolver, used internally by DID & Document – you can reassign it to one using a custom config added support for PLC servers returning application/did+json content type instead of application/did+ld+json added support for PLC servers returning services with IDs in the absolute format did:...#id instead of just #id added DID#did_web_host, which returns the did:web host URL together with http(s):// and a port if included (only for localhost), and raises a DIDError if the DID is not a did:web; #web_domain renamed to #did_web_domain and kept with the old behavior, #web_domain added as an alias Other: more detailed validation of DID & handle strings and for service endpoint URLs fixed DNS-based handle verification if there are multiple text chunks in a TXT record or multiple TXT records make sure that handle verification is case-insensitive the global DID alias is not reassigned if something else already defines it before DIDKit is loaded fixed redirects to relative URLs, and disallowed redirects to non-HTTP URLs and from HTTPS to HTTP fixed :max_redirects & :timeout options not being used when loading a DID document
October 26, 2026 at 6:45 PM
devtocash.bsky.social
The NS delegation attack is mechanical: the parent still delegates dev.yourdomain to a zone you deleted. Attacker creates Route 53 zones for that name until AWS hands them a nameserver set overlapping one of your 4 NS names. Minutes.

Delete the delegation or recreate the zone.
October 28, 2026 at 1:16 AM
affiliatechproject.bsky.social
Diagnose DNS leaks with `dig @127.0.0.1 example.com`. Force DoH in HAOS via docker-compose: set `--nameserver` to DoH IP (e.g., 1.1.1.1) and ensure router forwards 53/UDP to it. Block ads via Pi-hole upstream. For market data latency, use TradingView Direct: https://www.tradingview.com/?aff_id=11726
October 27, 2026 at 2:22 PM
fratschi.bsky.social
Just wanted to switch from a decicated jumphost to #netbird.
But instead of making it easier #netbird cannot obtain a nameserver and nothing works anymore and blocking me the whole day.

I don't like tools that try to solve one problem by adding additional new problems.
October 27, 2026 at 10:55 AM
mackuba.eu
Using Eurosky plc.directory mirror to load DID documents:
> resolver = DIDKit::Resolver.new(plc_directory: 'https://plc.eurosky.network') => #<DIDKit::Resolver:... @nameserver=nil, @plc_service="https://plc.eurosky.network", @request_options={}> > resolver.resolve_handle('mackuba.eu') => #<DIDKit::DID:0x... @did="did:plc:oio4...", @type=:plc, @resolved_by=:dns> > resolver.resolve_did('did:plc:oio4...').pds_endpoint => "https://lab.martianbase.net"
October 26, 2026 at 7:10 PM
theunicornxxl.bsky.social
BIND 9: Codeschmuggel-Lücke im Nameserver | heise online

heise.de/-11497068
BIND 9: Codeschmuggel-Lücke im Nameserver
Die Entwickler des Nameservers BIND haben aktualisierte Quellcodes veröffentlicht, die eine Schadcode-Lücke im Dienst schließen.
heise.de
October 25, 2026 at 2:07 AM
simsus.social.tchncs.de.ap.brid.gy
#bind 9: Codeschmuggel-Lücke im Nameserver | Security https://www.heise.de/news/BIND-9-Codeschmuggel-Luecke-im-Nameserver-11497068.html #dns #domainnamesystem #patchday #bind9
BIND 9: Codeschmuggel-Lücke im Nameserver
Die Entwickler des Nameservers BIND haben aktualisierte Quellcodes veröffentlicht, die eine Schadcode-Lücke im Dienst schließen.
www.heise.de
October 24, 2026 at 3:53 PM
namedaemon.bsky.social
GoDaddy's nameservers run 21.66% of .com names and Cloudflare's 12.94%, together about a third of the zone. Counted across 167 million names on 8 Oct 2026, by each name's first nameserver.

namedaemon.com/blog/top-dns...
A card: Top DNS providers of .com: GoDaddy runs 21.66% of names and Cloudflare 12.94%.
October 26, 2026 at 6:58 AM
cyberhub.blog
📌 BIND 9 Nameserver Code Smuggling Vulnerability Patched https://www.cyberhub.blog/article/33771-bind-9-nameserver-code-smuggling-vulnerability-patched
BIND 9 Nameserver Code Smuggling Vulnerability Patched
The developers of the BIND nameserver have released updated source code that closes a code smuggling vulnerability in the service. The security flaw is described as a Codeschmuggel-Lücke (code smuggling vulnerability) affecting BIND 9. The update addresses a vulnerability that could potentially allow malicious code execution in the nameserver. No specific CVE identifier, version numbers, or technical details about the vulnerability's exploitation method are provided in the article excerpt.
www.cyberhub.blog
October 23, 2026 at 7:37 PM
redrumofcrows.bsky.social
I'd stop but don't wish to break this flow at the moment, emergent . . .

same ip and ... notably . . . 0xPay here

this Alice Network has multiple affinties to a specific network, including the 'curitiba' nameserver (it's an intelligence coup to know this)

Adding this to the pile.
October 24, 2026 at 5:29 AM
mettbrtchen4711.bsky.social
Wie seid ihr immer noch mit ca-certificates oder PHP dran? Hier ist die nächste remote code execution Lücke www.heise.de/news/BIND-9-...
BIND 9: Codeschmuggel-Lücke im Nameserver
Die Entwickler des Nameservers BIND haben aktualisierte Quellcodes veröffentlicht, die eine Schadcode-Lücke im Dienst schließen.
www.heise.de
October 22, 2026 at 1:56 PM
heiseonline.flipboard.com.ap.brid.gy
BIND 9: Codeschmuggel-Lücke im Nameserver
https://www.heise.de/news/BIND-9-Codeschmuggel-Luecke-im-Nameserver-11497068.html?utm_source=flipboard&utm_medium=activitypub

Gepostet in Heise Security @heise-security-heiseonline
BIND 9: Codeschmuggel-Lücke im Nameserver
Die Entwickler des Nameservers BIND haben aktualisierte Quellcodes veröffentlicht, die eine Schadcode-Lücke im Dienst schließen.
www.heise.de
October 22, 2026 at 1:42 PM
aixzellent.bsky.social
BIND 9: Codeschmuggel-Lücke im Nameserver | Security www.heise.de/news/BIND-9-...
BIND 9: Codeschmuggel-Lücke im Nameserver
Die Entwickler des Nameservers BIND haben aktualisierte Quellcodes veröffentlicht, die eine Schadcode-Lücke im Dienst schließen.
www.heise.de
October 22, 2026 at 3:30 PM
heisec.bsky.social
Die Entwickler des Nameservers BIND haben aktualisierte Quellcodes veröffentlicht, die eine Schadcode-Lücke im Dienst schließen. #Security
BIND 9: Codeschmuggel-Lücke im Nameserver
Die Entwickler des Nameservers BIND haben aktualisierte Quellcodes veröffentlicht, die eine Schadcode-Lücke im Dienst schließen.
www.heise.de
October 22, 2026 at 1:29 PM
digitalscorpyun.bsky.social
For private Azure resources, check the DNS zone’s virtual-network links and the client’s DNS configuration. The durable lesson: finding an address, reaching it, and getting a working application response are three different steps.
Diagram titled “Complete DNS Lookup and Webpage Query.” Numbered arrows show an uncached lookup: 1, the client requests an address from a DNS resolver; 2–3, the resolver queries a root server and receives a referral; 4–5, it queries a top-level domain (TLD) server and receives another referral; 6–7, it queries example.com’s authoritative nameserver and receives the address; 8, it returns the address to the client. Separately, steps 9–10 show the client requesting a webpage from the web server and receiving its response. Cached DNS information can allow lookup steps to be skipped.
October 23, 2026 at 6:33 PM
dnwai.com
Atom's Premium tier wants your nameservers, a 30-day exit and 30% — the break-even math says a Premium sale has to close 32% higher. Premium Exclusivity: The Real Cost of Pointing NS to a Marketplace — dnwai blog

https://dnwai.com/d/blog/premium-exclusivity-nameserver-cost/

#domains
Premium Exclusivity: The Real Cost of Pointing NS to a Marketplace — DNWAI blog article cover
October 22, 2026 at 4:00 PM
linux-cowsay.bsky.social
cowsay
_____________________________________ / BOFH excuse #268: \ | | \ Neutrino overload on the nameserver / ------------------------------------- \ ^__^ \ (oo)\_______ (__)\ )\/\ ||----w | || ||
October 19, 2026 at 9:00 PM
lars.fedihub.space.ap.brid.gy
Älterer Archivbeitrag: So leitest du Bind9-Logs in separate Dateien um. Schau gern rein: https://dasnetzundich.de/bind9-log-in-seperates-file-umleiten @
#bind9 #dns #linux #selfhosting
Bind9 logfiles in seperate Dateien umleiten · dasnetzundich – Technik, Linux, Nextcloud & Open Source
Da ich einen Server betreibe, ist es logisch das ich auch meinen eigenen Nameserver betreibe, denn so spare ich mir einen Schritt wenn ich eine neue Domain erstellen muss. Ich brauche nicht für jede neue Domain oder Subdomain erst beim Regi
dasnetzundich.de
October 19, 2026 at 2:00 PM
codeflare.bsky.social
Beli Domain untuk Blogger: Jangan Terjebak Harga Promo Tahun Pertama

Mau beli domain untuk Blogger? Bandingkan 10 registrar, biaya daftar dan perpanjangan, lalu ikuti cara setting nameserver, DNS, dan HTT

https://www.codeflare.net/2026/10/beli-domain-untuk-blogger-jangan.html
Beli Domain untuk Blogger: Jangan Terjebak Harga Promo Tahun Pertama
Mau beli domain untuk Blogger? Bandingkan 10 registrar, biaya daftar dan perpanjangan, lalu ikuti cara setting nameserver, DNS, dan HTT
www.codeflare.net
October 18, 2026 at 2:34 PM
dotmoosehosting.bsky.social
DNS changes don't hit everywhere at once — your nameserver answers the new value, but resolvers keep serving the old one until the TTL expires. Tip: lower TTLs before a planned migration, raise them after. dotmoose.com/blog/dns-pro... #DNS #WebHosting
October 18, 2026 at 5:49 PM