[TZubiri]

To add a dissenting voice.

I've worked with small businesses and even small technical teams as a DNS consultant specifically.

DNS has only been a source of issues and confusion and not at all related to any requirements, just a form of checkbox implementation.

I do understand it's one of those technologies that are developed due to legitimate requirements, but it flows downstream and people just adopt it without really understanding the simpler solutions or what exactly it's meant to do.

That said if I had ever gotten a bigger client like a TLD registrar or a downstream registrar, then sure I would have had to work with it, but I've only ever had to learn how to uninstall it actually.

[gzread]

Can you explain better the most common problems you run into? I wonder if they can be solved.

[vbezhenar]

My two most common problems:

1. Need to change IP as soon as possible, but DNS record has huge TTL (e.g. 24h).

2. Client ISP DNS does not resolve my domain and it's absolutely not clear how to proceed from here. I don't have connections in huge ISPs, writing stuff to ISP support is as effective as throwing stones in the lake.

Funnily enough, for both cases, /etc/hosts or its Windows equivalent comes to the rescue.

[TZubiri]

1. 24 hours is not common at all for A records, it should be between 5 minutes to 60 minutes.

Perhaps you are thinking of NS records, which would only be changed very infrequently, and both the source and target systems should be up so that there's no loss of availability.

2. Never had that, it's more likely that you did something wrong rather it being an ISP issue.

Feel free to send me an email with specifics, the email is in my profile although in a cryptic format to avoid spam.