1

Ok, I just recently changed Name Servers for my site (Oct. 29th): http://dream-portal.net but there is an issue, the name servers were changed from godaddy, however, the DNS is being hosted elsewhere. Godaddy states that the DNS is resolving the site to www.dream-portal.net and that is making it inaccessible from the DNS on the other host and that they can't do anything because I'm not hosting DNS with godaddy.

I've contacted the other host and they say that everything is fine, however, people are not able to access the site and I can't access it from my work computer. I can only access it from my home computer. From my work computer it says that the page can not be found.

What should I do? What can I do?

Other people reported problems with the site here: http://www.simplemachines.org/community/index.php?topic=487592.msg3629960#msg3629960

8
  • Everything checks out; your DNS seems fine and your web site comes up correctly. Nov 3, 2013 at 1:15
  • Godaddy Domain Diagnostics says that their is a problem with the name servers though and that some people may not be able to access the site. Also, godaddy said that they themselves are not able to access my site at dream-portal.net and that it reports "Page Not Found" Nov 3, 2013 at 1:21
  • 3
    whatsmydns.net/#A/www.dream-portal.net shows that you do indeed have a problem.
    – Skyhawk
    Nov 3, 2013 at 1:44
  • Site comes up fine here. Nov 3, 2013 at 2:43
  • You have internet dudes running your name servers. They can say any old thing about nothing being wrong, but I cannot resolve NS1 through NS4 at xarpixels.com. No name server resolution, no web server resolution. The root servers cannot find your xarpixels.com dudes according to dig. Nov 3, 2013 at 3:28

1 Answer 1

1

Who maintains the name server? Is that you or another company?

At GoDaddy you have two settings:

1. Nameservers

That's easy, something such as ns1.dream-portal.net and ns2.dream-portal.net

If those are from another company, you should be all good. If you are running your own name server, then you also need to setup the Host Names.

2. Host Names

This is the IP addresses for the ns1 and ns2 name servers. This is required if you host your own nameserver.


Now, I checked your whois and it shows the name server as: NS1.XARPIXELS.COM

If I run dig against it, it says it doesn't know anything about your domain:

> dig @NS1.XARPIXELS.COM dream-portal.net
dig: couldn't get address for 'NS1.XARPIXELS.COM': failure

So the setup at XarPixels.com is wrong. Without that, what still works comes from caches. Notice the @<nameserver> syntax to very that this very nameserver is properly setup.

10
  • ns1 through ns4 for xarpixels.com are DOA, no ip address resolution. For some reason, the ip address is stuck in the name resolution I use, will probably expire out soon and the site will totally disappear. Name: dream-portal.net Address: 192.65.243.61 -> Name: cronus-dal.thewebhostserver.com Address: 192.65.243.61 Nov 3, 2013 at 3:15
  • cronus-dal.thewebhostserver.com is the PTR of that IP address. You need the PTR to send emails and if you accept credit cards. Otherwise it's not too important. But if ns1.xarpixels.com cannot be resolved, then you should not use that name in your GoDaddy settings. Instead, directly specify the IP addresses for ns1 & ns2... Nov 3, 2013 at 3:44
  • Nameservers are set within godaddy, but I don't control anything else besides name servers on godaddy, xarpixels.com controls the rest of it all. So, I'm assuming that the problem lies with XarPixels than? This was my original thought, but they say that everything is fine on their end of things. I don't have any IP on NS1, or NS2 set. Nov 3, 2013 at 3:55
  • Bad case of "Dude, where's my name server?" The name servers are unreachable and unresolvable, you need them to prove that the root servers can find the name servers, which they can't. Nov 3, 2013 at 3:56
  • 1
    We can be sure because dig traces show the routing from the root servers attempting to direct us to XARPIXELS.COM and majorly failing to get an answer. We can use dig to try to resolve the name servers to get their IP addresses, which fails. I can go do the same things on my live ecommerce site and immediately find my server ip and all three name server IPs. Out of all the name servers I plugged in for dig, only one actually resolved anything. Root Servers can't find you, only one oddball out there responds. Especially when Skyhawk pointed out that out you do indeed have a problem. Nov 3, 2013 at 6:09

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .