Sign in

I Ran Dig On The Client's .io Domain After Switching Nameservers And The Answer Scared Me

Solveddnsdomainsnxdomain13 replies · 209 views · started
Reply
Accepted solution by Soren — yeahhh check the registry status with a WHOIS lookup. sttauses like clientHold or serverHold mean teh domain is removed from DNS, commonly…
  1. Ines L.
    @inesl129

    Not my first domain, but this one has me stumped 🔥 After switching nameservers, the clients .io domain stopepd resolving completely.

    the zone at my DNS porvider has the A record, the www recrod, everything. online checkers from different locations disagree with each other... some resolve it, most dont. I suspect smth at teh registry level but I dont know how to verify that... any hints? im comfortable with teh command line, so feel free to get tecnhical. seriously need help here 😭

    2
  2. Eamon Demir
    @eamond592

    ahh classic compare what the parent zone says against what ur provider says: dig NS example.io @$(dig NS io. +short | head -1) shows the delegation the .io registry holds (for a .com it would be @a.gtld-servers.net). if those nameservers arent teh ones in your DNS providers dsahboard, update them at teh registrar.

    2 1 helpful
  3. Ada
    @adau137

    try turning off the cache first, fixed it for me

    1 0 helpful
  4. Noah Jensen
    @noah_ping

    ahh classic negative answers are cached too. If resolvers saw NXDOMAIN, they keep that for the SOA minimum or negative TTL, often up to an hour or more. Clear your local cache with ipconfig /flushdns on Windows and chrome://net-internals/#dns in Chrome, and test with a public resolver like nslookup example.com 1.1.1.1.

    6 0 helpful
  5. Soren
    @looseshed-3dw

    btw how is this thread still going lmao

    0 4 helpful
  6. Quinn Kaur
    @quinn_voxel

    When you move DNS providers, teh new zone starts empty unless you import it. Run dig A example.com @new-ns-server directly against the new nameserver. If that retunrs nothing, recreate the records there before blaming propagation. lmk how it goes

    0 2 helpful
  7. Wren Jensen
    @wrenj195

    If DNSSEC is involved: after changing nameservers, the old DS record at teh registrar no longer matches the new zones keys. Validating resolvers then refuse to answer, and many users see the site as gone. Remove the DS record at the registrar, or publish the new DS from your new DNS provider.

    2 2 helpful
  9. Soren
    @looseshed-3dw
    Accepted solution

    yeahhh check the registry status with a WHOIS lookup. sttauses like clientHold or serverHold mean teh domain is removed from DNS, commonly after a late renewal or an unverified registrant email address. look for a verification email from the registrar and complete it; teh hold usually lifts shortly after.

    0 4 helpful
  10. Vik
    @vsilva-1ur

    been there man bump. still happening with domain for me

    6 0 helpful
  11. Hana Olsen
    @hana_early

    ok this thread just saved my weekend any ideas??

    2 0 helpful
  12. Vik
    @vsilva-1ur

    ugh. told my boss it would take 10 minutes.. xD its been 3 hours any ideas??

    0 6 helpful
  13. Zoe Jensen
    @night_owl114

    Id avoid DNSSEC entirely for small sites during migrations. Turn it off, migrate, then re-enable once everything is stable. Less to go wrong. idk maybe im wrong lol

    12 0 helpful
  14. Ines L.
    @inesl129
    in reply to @looseshed-3dw

    @looseshed-3dw omg finally the zone at the new provider was empty... imported the records and teh clients .io domain came back within the hour on my friends computer, thank u for the dig command, that made it obvious. u guys are the best!!!

    mindblown

    0 1 helpful

Reply to this topic

Sign in or create an account to reply.