Forum Moderators: phranque

Message Too Old, No Replies

** server can't find www.example.com: NXDOMAIN error

dns error

         

thewpfan

1:17 pm on Oct 12, 2010 (gmt 0)

10+ Year Member



I am on one of those shared hosting services and recently updated my name server entries where I purchased the domain.

I read it takes 24-72 hours to fully convert to the new name servers so should I expect the following error when doing an nslookup:

** server can't find www.example.com: NXDOMAIN


I did this check after 11 hours of changing name servers. When I do a dig, the name servers are listed as the updated one. However, ping, nslookup, and traceroute fail to resolve the domain name.

Is this error normal and do I just need to wait a day or so?

phranque

1:57 pm on Oct 12, 2010 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



did you also edit your zone file on the name server or did you only edit your registry records?

thewpfan

6:06 pm on Oct 13, 2010 (gmt 0)

10+ Year Member



Thank you. Actually, I found that my subdomain for www.example.com was not setup. I only had example.com setup so I just added www.example.com.

phranque

8:50 pm on Oct 13, 2010 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



make sure you didn't introduce a wildcard subdomain problem.
should be ok if you specifically added www.