Got a domain name and have small issue ...

[zeta_immersion]

Got a domain name through aitdomains.com and have set it up as follows:

mydomain.com pointing to ns1/ns2.nameit.net

now the records look as following

A www.mydomain.com 69.xxx.xxx......

mail.mydomain.com 69.xxx.xxx......

MX mail.mydomain.com 10

CNAME www.mydomain.com mydomain.com

TXT mail.mydomain.com somestringoftext

I know it takes up to 24h for the changes to take effect, however, when I do an nslookup on

mydomain.com I get the IP of tybit.com

and when I do nslookup on 69.xxx.xxx...... I get the ISP 69-xxx-xxx...... (which is fine)

so, do I need to change anything or have t wait?

(for my other domain I also have a zoneedit.com account and resolves fine --- had it for a few years)

Thanks

[c3ntury]

Best off waiting another 12 hours before worrying. Try clearing your cache for your browser?

[zeta_immersion]

  On 06/12/2011 at 20:24, c3ntury said:

Best off waiting another 12 hours before worrying. Try clearing your cache for your browser?

sounds good, also, as it stands, do the records look fine as they are? is there anything I should change (I am thinking name resolution for the mail server as will give headakes with hotmail/yahoo) though I could puch it through the ISP

[PNWDweller]

On a good day, DNS will resolve within a few hours, but in most cases, it can be very unstable for the next 72 hours while the DNS Servers 'refresh' their cache.

You can use Whatsmydns.net to check the propagation as well as leafdns.com to name a few.

I recently did a couple of migrations, and on one, it took at least 3 days to fully resolve.

[+BudMan MVC]

"it can be very unstable for the next 72 hours while the DNS Servers 'refresh' their cache."

"to check the propagation"

Sorry but NO -- DNS servers do not refresh anything, unless they are asked, and the TTL for something that was cached has been expired. No records do not actually propagate anywhere.

As to taking 3 days to fully resolve -- well what was the TTL on the records, and you would of known exactly how long it would of taken before there were no cached entries possible out there.

DNS cache check would be a better term for that whatsmydns site

Why don't you just query your nameservers for whatever records you interested about. Query ns1/ns2.nameit.net directly!

be with with nslookup or dig, or host whatever dns tool you like best

dig @ns2.nameit.net www.mydomain.com

For example.

Records are cached for the life of the TTL, period!

If your TTL for a record is 2 hours, and you change it on the owning name server to point to some other IP. Then 2 hours from that moment every single person on the planet will resolve the new IP.. Unless their dns server is breaking the rules!! Your not allowed to cache a record for longer than its TTL - PERIOD!!

Now if your TTL is 2 weeks, then yeah a nameserver that had been requested for that record before you changed it will cache it for 2 weeks.

When your looking to change nameservers or even a record, then before hand you lower the TTL so that you know once the change is made - whatever the length of the TTL was is the max amount of time someone could be getting the old record or NS for that domain.

[zeta_immersion]

all is good. the problem was with the nameservers baing hte wrong ones thus it was pointing to some random tybit resolution.

thaks guys .... the TTL was a few hours so all is well.

cheers :beer: