Forum Moderators: phranque

Message Too Old, No Replies

IP to Domain DNS prob

         

mrmean

9:03 pm on Feb 17, 2004 (gmt 0)

10+ Year Member



Currently, I can access my domain only by the IP address. Although every now and then(Rarely) I can access it by the domain name itself. I have tried to clear the temp int files, flush the dns, clear the history, reboot, yet I still get a page that says to the affect of:

Oops. There may be an issue with the Free URL Forwarding service for this
domain, in which case our technical staff is currently working the situation. Otherwise,
this domain is currently under construction and will be back online soon.

other people can access my site through the domai name, but i can not see it through my machine. Any suggestions?

thanks for all your help

bakedjake

9:06 pm on Feb 17, 2004 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



You're probably behind a firewall doing NAT. If this is the case, you won't be able to see it from the inside, unless you put an entry in your hosts file mapping the domain to the local (inside) interface.

This should probably be moved to Website Technology Issues...

tombola

9:08 pm on Feb 17, 2004 (gmt 0)

10+ Year Member



Welcome to Webmasterworld!

Normally, you should be able to access your domain within a few days. It has to do with DNS propagation: once the nameservers have been updated at your domain registrar, it takes up to 3 days for this information to pass through the Internet.

mrmean

9:15 pm on Feb 17, 2004 (gmt 0)

10+ Year Member



thanks for your help everyone. It has been about a week, giving it enough time for propogation. Plus others outside of my apartment can view the site, thus making the problem on my machine. I'll try that firewall tweak there you mentioned. I am behind a router.

thanks again for quick responses!

mrmean

9:46 pm on Feb 17, 2004 (gmt 0)

10+ Year Member



ok i tried just the domain name, not the "www" and it worked. any clue why this?

bakedjake

9:47 pm on Feb 17, 2004 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



Do an nslookup - what are you getting for www.domain.com and domain.com? Any difference?

mrmean

9:53 pm on Feb 17, 2004 (gmt 0)

10+ Year Member



just kidding it's not working now.
shoot.

mrmean

9:55 pm on Feb 17, 2004 (gmt 0)

10+ Year Member



I altered the hosts file on my computer, and maybe that is why it worked?

bakedjake

9:56 pm on Feb 17, 2004 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



Heh, yeah. If you point the name to the local (internal) interface, it should work.

mrmean

10:06 pm on Feb 17, 2004 (gmt 0)

10+ Year Member



so that is what helped it? hard coding the IP to the domain name in the host file? I am not hosting the site myself. But this seemed to have worked, but only for the domain.com(not the "www.domain.com")

bakedjake

10:07 pm on Feb 17, 2004 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



Yes, that's what helped it. Add both domain.com and www.domain.com if you want to access both.

mrmean

10:14 pm on Feb 17, 2004 (gmt 0)

10+ Year Member



thanks for your help. any idea why on earth i had to do this? Is it because my dns is cached to the worng address? just confused on this one..lol

bakedjake

10:56 pm on Feb 17, 2004 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



Post number two. ;-)

NAT firewalls can't go out and come back in again. They get confused. ;-)

mrmean

11:08 pm on Feb 17, 2004 (gmt 0)

10+ Year Member



I see, so the only way would be to turn off the firewall through my router configuration huh?

not sure i'd want to do that.