Hi. Speaking of all this dns weirdness and bill's latest message it prompted me to wonder why my domain is not updated on all changes. I'll explain. I have asmodean.net and set up 4 authoritive dns servers ns1.mi.sprintbbd.net, ns2.mi.sprintbbd.net, ns1.az and ns2.az. Now the host saidin.asmodean.net used to have IP 216.254.102.192 but when I moved and got a new IP address I changed it to 216.254.114.61 which is the current one. Since I currently only have one machine I figured I would just have cname records to www.asmodean.net, ftp.asmodean.net and mg.asmodean.net all cname to saidin.asmodean.net. OK, now to the problem. When I moved and changed it to 216.254.114.61 everything seemed to be working yet if you query dns servers at random some still say that saidin resolves to the 102.192 address instead of the 114.61 address. And so of course because the www. host was cnamed to saidin it too was not resolving. I checked and rechecked my zone file and it looks correct. I can ask ns1.mi, ns2.mi, ns1.az and ns2.az for the information with dig or host and they give the correct 114.61 IP address. If you ask for example ns1.earthlink.net and ns1.kc.rr.com they do not have the correct address. Furhter more what I di was change the cname records to a records and just have the individual hosts www, ftp, and mg resolve to the IP 114.61 directly instead of the cname saidin. NOw those ns servers which still say that saidin is on 102.192 report the correct ip address 114.61 for www and mg yet they still say that saidin is 102.192. Can anyone explain why this would be so? The change from the old ip to the new one happened in March. That is definitely past the one week ttl time set on most default name servers. -- If you perceive that there are four possible ways in which a procedure can go wrong, and circumvent these, then a fifth way will promptly develop. Raul A. Gallegos - http://www.asmodean.net
