You can inspect some stuff while you're waiting to make sure things are
set up right using terminal. Start by doing
nslookup
and hit return. Normally this lets you put in an address, like
www.caraquinn.com and it will tell you the IP address of your DNS server
and the IP address of the server your computer connects to to retrieve a
page after the line 'Non-authoritative answer'. It's non-authoritative
because you are asking your DNS who asked the DNS of caraquinn.com what
the answer was and then cached it. So you're one step removed from the
source and it might be old information. To get closer to the source we
can find out who does DNS for caraquinn.com. The way I do it is to look
up the mx record for a domain which will include the DNS server that is
authoritative for that domain. So type
set type=mx
and hit return. Now when you put in a domain like caraquinn.com it will
tell you who has all the authoritative DNS info for that domain in the
lines after "Authoritative answers can be found from". Most sites will
have more than one DNS for reliability and ideally the best one is
listed first. In the case of caraquinn.com that would be ns58.1and1.com.
So now I can tell nslookup to talk to ns58.1and1.com instead of the DNS
from my local ISP. To do that I would type
server sn58.1and1.com
and hit return. Then any queries I make will be asking the caraquinn.com
authoritative DNS server instead of my local ISP's DNS server. So now I
wand to switch back to getting name server address records so I type
set type=a
and hit return. Now I can type in
www.caraquinn.com
it spits back 74.208.159.32, which should be the IP address of the
server responding to requests sent to www.caraquinn.com. So if you do
all this I would check that your authoritative DNS has the right IP to
www.whatever.com mapping since that's where all the other DNS machines
are going for answers. If that is correct but your local DNS has it
wrong then it's just a cache/propagation problem. My experience is
changes don't take more than an hour and often float around in a matter
of minutes. Note that this stuff can get complicated fast with content
delivery networks, multiple servers answering to the same web address,
cnames (like aliases that map to the same server) and more. Hope this
helps nail down the issue.
CB
On 6/24/13 9:16 PM, Mike wrote:
Hi everyone,
I need help with fixing a broken website.
My domain name is registered through Wordpress.com but self hosted at dream
host.
Well apparently my automatic renewal of the domain name wasn't set up after all
and it expired last night.
I've since renewed it but when the url is visited it takes me back to the old
Wordpress blog I was using originally not the self hosted site.
I am guessing that the dns settings pointing the domain name to dream host
broke when the domain expired and now I don't know how to fix it.
I refreshed the domain on dream host but it hasn't helped.
Can anyone give me some other things to try here? I am lost now.
Feel free to email me off list.
Skype or facetime are options too it they're needed.
Thanks for any help.
Mike
--
¯\_(ツ)_/¯
--
You received this message because you are subscribed to the Google Groups
"MacVisionaries" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to macvisionaries+unsubscr...@googlegroups.com.
To post to this group, send email to macvisionaries@googlegroups.com.
Visit this group at http://groups.google.com/group/macvisionaries.
For more options, visit https://groups.google.com/groups/opt_out.
