User Domain not working

R

rrd2009

New member
Joined
Mar 31, 2010
Messages
7
I'm new to directadmin. I have it installed, created the nameservers for my main domain, created the domain in the User Level and registered and changed the nameservers with godaddy. It works fine. I can build the site in /home/admin/domains/domain.com

the problem I'm having is with moving our other domains over. I changed the nameservers with godaddy and went to my directadmin panel as admin. Clicked on User Level > Domain Administration > Add Another Domain and created it.

The problem is the domain isn't working. I can't find it with a browser, or even ping it. Ping request could not find host www.iussa.org. Please check the name and try again. I think it was created as I have a /home/admin/domains/domain2.com

What am I missing? I changed the namservers yesterday afternoon so they should have propagated by now.
 
Is it showing a site? I still can't get it . . I registered a new domain, created the domain in the User Level and it worked perfectly . . just the ones I already have are all screwed up for me lol Maybe I've just gotta give it a few days?!

I wanna make sure I can switch over a few lesser used domains before I go and move over more important ones.

Thanks floyd!
 
It shows the default DirectAdmin page which says "Welcome to the home of iussa.org"
 
you need to wait 74 Hours (3 Days) for the DNS Servers to update all around the worlds ISPs
 
Geez! Guess I'm just used to registering new domains and having them resolve in a few minutes. So much for the "superhighway".
 
TheKiller said:
you need to wait 74 Hours (3 Days) for the DNS Servers to update all around the worlds ISPs
Click to expand...

What registrar are you using? In recent years I have never had to wait more than a few hours.
 
i am using DOMAIN.COM
but at my domains i only waited a few minutes or MAX One day at my first domain

a friend of mine took a domain from this guys http://www.thecompanywarehouse.co.uk/
and it took 3 days so i can access it in my country... in his was fine
between floyd...
is newwebsite.com yours?
i wanted to move to that host a few months ago xD
 
I'm using godaddy and it's still not working for me. If I ping it from home it says can't find the host, and if I ping it from the server it lists the old IP, but godaddy says it's been changed when I check their site.

Is there something I have to clear or refresh to get it to work?? I'd really not like to have my other domains to be unavailable for days while I switch things over :eek:
 
Hey,

Right now your name servers for iussa.org (NS1.FREEDOMHOST.INFO and NS2.FREEDOMHOST.INFO) do not resolve to an IP address...

I'm not sure what happened between now and when Floyd first checked, but something apparently changed.

David
 
Any idea how to change that? I've got two domains set up with the same nameserver and they both work fine, but not this one?

http://www.intodns.com/iussa.org
ERROR: Some of your DNS servers do not have A records at all. I could not find any A records for the following DNS servers:
ns2.freedomhost.info
ns1.freedomhost.info

You must have A records for all of your nameservers.

http://www.intodns.com/rockinghampatriots.info
NS records got from your nameservers listed at the parent NS are:

ns2.freedomhost.info [] (NO GLUE) [TTL=14400]
ns1.freedomhost.info [] (NO GLUE) [TTL=14400]

Is this something on the server or is it just taking an unusually long time for godaddy to work its magic?
 
Remember, I'm a newbie ;x I didn't change anything, just set up a domain with whatever defaults directadmin sets up, so I'd assume they'd both work? I guess not.

Here is the DNS Management for the domain that doesn't work
ftp A 208.73.74.20
iussa.org. A 208.73.74.20
localhost A 127.0.0.1
mail A 208.73.74.20
pop A 208.73.74.20
smtp A 208.73.74.20
www A 208.73.74.20
iussa.org. NS ns1.freedomhost.info.
iussa.org. NS ns2.freedomhost.info.
mail MX 10
iussa.org. TXT "v=spf1 a mx ip4:208.73.74.20 ~all"

So I need to add an A record like
ns1 A 208.73.74.20 ?

The only nameservers registered on godaddy are for the main domain ns1 & ns2.fredomhost.info
 
Hey,

You need to add the A records in the freedomhost.info zone file. Like:

ns1 208.73.74.20
ns2 208.73.74.21

David
 
Notes on that infamous 72 hour rule:

The problem is the TTL. If you've looked at a domain before it exists on the new server (while it's still on the old server) your ISP (if you're using their nameservers for resolution on your desktop, as most of us do) is now caching the old IP#. It will continue to look at the old server until the TTL expires and it gets new information.

The 72 hour rule comes from the situation years ago, when the root servers were updated only once a day (at midnight EST if I recall correctly, for the main root servers) and admins used long TTLs.

If I recall correctly, by Default DirectAdmin now sets up TTLs that are four hours long; we use ten minutes.

However your nameservers (as registered at the registrar) use 48 hours, and there's no way to change that.

So up to one day (24 hours) to actually update the nameservers, plus up to 48 hours for the namervers' TTLs to expire, adds up to a maximum of 72 hours.

The one-day has now been replaced by almost instantaneous, and the nameservers in many cases are now updated by a push when the IP#s are changed, so it should take much less time.

Usually the problem is your local ISPs nameserver cache.

And of course whichever nameservers your visitors are using.

Jeff
 
You must log in or register to reply here.
Back
Top