netlify

Attention over time

7-day rolling share of analyzed posts/comments mentioning this entity · 90 daily points ending 2026-10-15

Final complete day: 2026-10-15. Attention was 0.3% — this entity appeared in 8 of 2,852 analyzed posts/comments in the seven days ending that day (13 mentions).

Each point is a seven-day rolling window of complete UTC days; a point is comparable only when at least 100 analyzed posts or comments fall inside it. A day with no analyzed records counts as zero; missing coverage is marked and never shown as zero. The series ends at the latest complete analyzed day — it never extends into the current incomplete day. How attention is measured.

Recent mentions

1. 2026-10-13 12:42 UTCComment

   When you say it isn’t saving, does the record disappear from the DNS dashboard after you refresh, or does it stay there but Resend can’t verify it? If it disappears, try saving in a private window and check the Network tab in dev tools for a failed request. If it stays, check which nameservers the domain is using and make sure you’re adding the record at that provider. The site can be hosted on Netlify while DNS is still managed elsewhere.

2. 2026-10-13 08:49 UTCComment

   A few things to try. Since the Google TXT worked before, the issue is probably with this specific record's value or name, not your DNS setup. 1. Check the value length. DNS TXT strings max out at 255 characters per chunk. Resend's DKIM public key can be longer than that. If it is, split the value into quoted chunks of 255 characters each and paste them together. Most DNS panels accept that. Netlify's form may silently reject an over-long single string. 2. Use the Netlify CLI or API instead of the dashboard. The web form hides errors. Adding the record via CLI or API will show you the real error message, which usually points straight at the problem. 3. Double-check the name field. Netlify appends your domain automatically, so enter only resend.\_domainkey, not the full resend.\_domainkey.yourdomain.com. Also strip any quotes and trailing spaces from the value when pasting. 4. Try a different browser or an incognito window. A silent save with no error sometimes means the dashboard's JavaScript failed, not your record. 5. After it saves, verify with dig TXT resend.\_domainkey.yourdomain.com or an online DNS checker before hitting verify in Resend. Propagation can take a few minutes to a few hours. If none of that works, the Netlify community forum is worth a post. Their team answers DNS threads fast.

3. 2026-10-13 06:24 UTCPost

   Is Neon PostgreSQL Free Tier reliable enough for a production booking app? - I'm planning to use Neon PostgreSQL for a production booking application and would like feedback from people with real world experience. **My workload:** • 300 daily active users • Up to 30 concurrent users • Users can book 2 to 3 slots daily, and frequently check available slots and existing bookings • Next.js backend, with a landing page hosted on Netlify Would Neon's free plan be sufficient for this workload, or should I opt for a paid plan? I'm particularly interested in reliability, unexpected downtime, query latency, compute limits, and any production issues you've experienced. Would you trust Neon Free for this use case?

4. 2026-10-13 04:43 UTCPost

   Netlify DNS Record problem - I have purchased domain on godaddy and connected via netlify. Now i am trying to add resend(email service) domain verification TXT code but it's not saving it and not showing any error. In the past i have saved google search console domain verification TXT successfully. what should be issue and how to resolve this issue?

5. 2026-10-12 07:34 UTCComment

   Hey! Nice to read that! I used Nuxt/Vue, been using that for a while and it’s always been my favorite framework, and animations are basically js/css and gsap only more those simple title reveals Hosting is in netlify although after pricing changes, I use cloudflare for most of my projects now