DNS changes kind of suck.

Currently testing out a migration process from SquareSpace (thanks Google) to AWS.

Switched my squarespace NS to AWS hosted zone NS, and slowly but surely some websites are showing the DNS change.

However ‘dig’ on my machine still says it ain’t never heard of my domain before.

I understand things take time, but when an operation takes a day or more to complete it would be great if I had confidence that my configuration is correct.

(At least this time I lowered my DNS TTL, so hopefully next changes will be faster)

#techrant

Reply to this note

Please Login to reply.

Discussion

i always set mine to the shortest possible time limit on namecheap... which is like one minute or something, the changes really seem to update that fast, it's just a TTL so it makes sense it should be possible to make it update fast on the DNS server

one thing that's always bothered me for a long time is why is it that i don't have a full caching bind server by default on all my devices? instead this dumbass "stack" thing which doesn't work and asks every time and doesn't autonomously update itself according to proper BIND9 rules like the TTL

it's almost like they want you to tell the DNS servers what sites you are looking at in real time

I think it is something related to DNSSEC which I don’t really understand. Just turned it off and hopefully will recover relatively soon

ah, could be that

usually even in worst case it's working in a few hours from recent past experience, but i always obsessively click the shortest TTL i can in the namecheep advanced DNS page