yes, i've googled.

anyway, i changed the dns entries for one of my domains yesterday to point to the new server.

today, if i ping or put http://mydomain.com into my web browser, it goes to the new server as it should.

if i ping or put http://www.mydomain.com into my web browser, it goes to the old.

what's up? i assume it's just "one of those dns propogation" things and will straighten itself out, but honestly i've never seen this happen before. usually it all changes at once, not one piece changing and the other not.

[Edited on December 15, 2005 at 11:19 AM. Reason : *]

12/15/2005 11:18:15 AM

might take 24-48hrs?

-ZiP!-

12/15/2005 11:26:59 AM

just means the DNS servers you use for your connection haven't updated. No biggie. Sometimes it takes days.

12/15/2005 11:40:24 AM

yeah i figured that.

every other time i've gone through this, the www part made no difference whatsoever, so it seems strange that it does this time

12/15/2005 12:05:32 PM

ipconfig /flushdns.

Also, flush dns on any other dns servers your computer might be connected to (aka routers) up to your ISP.

12/15/2005 12:09:48 PM

If you have a linux machine try this:

gephelps-lnx1:32> host -v http://www.ncsu.edu
Trying "www.ncsu.edu"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62483
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 6, ADDITIONAL: 6

;; QUESTION SECTION:
;http://www.ncsu.edu. IN A

;; ANSWER SECTION:
http://www.ncsu.edu. 2638 IN CNAME uni200v.unity.ncsu.edu.
uni200v.unity.ncsu.edu. 2638 IN A 152.1.226.10

;; AUTHORITY SECTION:
unity.ncsu.edu. 2502 IN NS ns2.ncsu.edu.
unity.ncsu.edu. 2502 IN NS ns3.ncsu.edu.
unity.ncsu.edu. 2502 IN NS ns4.ncsu.edu.
unity.ncsu.edu. 2502 IN NS ns5.ncsu.edu.
unity.ncsu.edu. 2502 IN NS ns6.ncsu.edu.
unity.ncsu.edu. 2502 IN NS ns1.ncsu.edu.

;; ADDITIONAL SECTION:
ns1.ncsu.edu. 1674 IN A 152.1.1.22
ns2.ncsu.edu. 1674 IN A 152.1.1.208
ns3.ncsu.edu. 1674 IN A 152.1.1.206
ns4.ncsu.edu. 1674 IN A 152.1.1.161
ns5.ncsu.edu. 1674 IN A 152.1.1.248
ns6.ncsu.edu. 1674 IN A 152.1.2.22

Received 278 bytes from x.x.x.x#53 in 58 ms


See where the CNAME for the www entry points. It probably points to the old server and will need someone to go in there and change it.

12/15/2005 12:13:35 PM

Progress Hosting refugee?

12/15/2005 12:18:34 PM

did you point the domain to new DNS servers? Or did you try to modify the DNS records yourselves with the registrar?

12/15/2005 12:23:05 PM

changed the dns with godaddy

yes, progress refugee

12/15/2005 12:42:46 PM

while we're on the topic, do hosts generally have to make a subdomain called "www" because it doesn't always work with domains?

and if that's the case, then maybe your www subdomain was hard-coded to your old IP and will be that way until you change it.

12/15/2005 2:34:42 PM

no you just add an entry for http://www.domain to point to domain.com in the nameservers.

12/15/2005 2:36:34 PM

Just an FYI:

This is a good DNS site that I use.

http://www.dollardns.net/cgi-bin/dnscrawler/index.pl

12/15/2005 3:55:39 PM

http://www.dnsstuff.com/
http://www.checkdns.net/quickcheck.aspx
http://www.samspade.org/

12/15/2005 4:29:42 PM