Hi, sometimes you are about to register a domainname beneath some “strange” topleveldomain like .tl, .pe, .ec and so on and in all cases you have to enter a nameserver which is responsible for that domainname you will register and I once got into trouble with cocca.cx which is the registry for .tl. I registered a name and told the nameservers but after a few months users complained that they can’t resolve my domainname but I also had a lot of users who could resolve that domainname so I believed it was a misconfigured nameserver of the side of the users… But in the end I was utterly wrong. The real problem was that the responsible dns servers of cocca weren’t synchronized so a that a bunch were up and running with correct nameserver information and some others weren’t. I could easily find out with “dig”: 1.) dig This gives you a list of all root nameservers. Pick one, e.g. “L.ROOT-SERVERS.NET.”. 2.) dig @L.ROOT-SERVERS.NET. as.tl …where “as.tl” is your desired domainname like “heise.de” e.g. It will give you a list of responsible nameservers of the associated registry which controls the topleveldomain. Pick one! 3.) dig @ns.anycast.nic.tl. as.tl Do not forget to append your domainname again…you should now get a list of _your_ nameservers or the ones of your provider. If that works, the chosen nameserver “ns.anycast.nic.tl.” works and has valid records…you now have to cycle through all of them to find out if they are all synchronized! I’m sure you can automate all this but I just wanted to give a straight “way” to walk through to find out if your registrys nameservers are well configured… Hope it will help some day :P…
Sun, 7/12/2009
Comments
