A friend has a website and it seems there is now (for some reason) a problem with DNS resolving. If I nslookup domain.com I get a NXDOMAIN response, but if I do nslookup domain.com ns2.powweb.com I get the correct lookup. (ns2.powweb.com is one of the name servers from the web hosting company)

What are some reasons this could be happening? I'm fairly n00bish with this kind of stuff.

closed as off-topic by mdpc, kasperd, Jenny D, HBruijn, MadHatter Oct 15 '14 at 20:49

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions must demonstrate a minimal understanding of the problem being solved. Try including attempted solutions, why they didn't work, and the expected results. See How can I ask better questions on Server Fault? for further guidance." – kasperd, Jenny D, HBruijn, MadHatter
If this question can be reworded to fit the rules in the help center, please edit the question.

  • 1
    What is the domain in question? – EEAA Oct 14 '14 at 23:45
  • it's bayonics.com – sean Oct 14 '14 at 23:49
  • 1
    From my tests it looks like there are no name servers configured for the domain. My suggestion would be to contact the registrar or log into their control panel and designate name servers for the domain. – joeqwerty Oct 15 '14 at 2:50

It seems that the domain is expired. A whois request on the domain name gives, among other info:

Domain Status: clientHold

This is clearly related to an expired domain, according to the corresponding info page from Tucows (the registrar used to register the domain).

  • 1
    But: Expiration Date: 09-jan-2015. – EEAA Oct 15 '14 at 0:02
  • 1
    @EEAA Yes, they "extend" the expiration date in this circumstance. – Michael Hampton Oct 15 '14 at 2:57

Not the answer you're looking for? Browse other questions tagged or ask your own question.