When trying to add my the dkim DNS TXT record for my domain (to authenticate outgoing emails) in Amazon’s Route 53, I received the error message: “CharacterStringTooLong (Value is too long)”. This is how I fixed it.
You can look up the name servers associated with a domain name using either “whois” or “dig NS”. In some rare occasions, I have gotten back two different answers using these two techniques. In my experience, “dig NS” is the more trustworthy of the two.
At WordCamp Lehigh Valley 2018, I presented How to Avoid Mucking Up Your DNS. When I started working with websites, modifying DNS settings terrified me. We’ll discuss the things I wished I knew then: A records, CNAMEs, TTLs, name servers, and how to test these things. We’ll look at things I broke and how the […]
I’ve started compiling a list of name server domain names and the companies associated with them. This list has been helpful in guiding clients to the correct company to contact when modifying DNS records. You can determine your clients’ name servers by using a command line utility like whois or dig (e.g. whois salferrarello.com or […]
dig is command line DNS Lookup program pre-installed on *nix and Macs. If you don’t have access to dig from the command line, there are some websites that offer a web interface to dig (e.g. Google Toolbox’s Online Dig). Basic Lookup (Similar to ping) dig example.com Advantages over ping: Doesn’t get grumpy when you include […]