Cannot resolve domain

Tiras25
Tiras25 used Ask the Experts™
on
trying to reach to the companyname.com, using ping companyname.com

This domain is hosted by goddady.com

it was hosted my email myname@companyname.com
now I can send but cannot receive any more.  bouncing back..
Cannot resolve using nslookup either.
email hosted outlook.office365.com

The error is "Domain unavailable"
The domain is not expired (it expires in 2019)
however non-pingable and cannot resolve..
What could be an issue?  Please help troubleshoot..
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Everyone will need a little bit more information to assist you. let's start with some basic details.

what are you trying to accomplish? what does the certificate have to do with the situation? what DNS name or IP are you trying to ping?
I won't be able to answer over the weekend but here are some things needed to clarify to better advise:
1. What type of domain? Assuming Internet domain but needs clarified because you can name your Windows domain the same as an Internet domain.
2. From where; anywhere, within your Windows network which has the same domain name?
3. What type of server / service are you trying to ping?
4. Has it been pingable in the past?
5. Is the service(s) it provides still working but you cannot ping or ... ?

Just a few things to start off ...

Author

Commented:
trying to ping companyname.com
hosted by godaddy.com
it was hosted my email myname@companyname.com
now I can send but cannot receive anymore.  bouncing back.. cannot resolvle nslookup either.
email hosted outlook.office365.com
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

in order to actually help we would need the specifics but I understand you are trying to be protective of sensitive information.  

how are you resolving your mail domain?  are you using public DNS or DNS inside your local network? if you are inside a private network change your DNS resolver to a public DNS resolver. in the example below, i change from my router that is proving DNS to google DNS server before trying to query your destination.

C:\Users\madis>nslookup
Default Server:  UnKnown
Address:  10.10.10.1

> server 8.8.8.8
Default Server:  google-public-dns-a.google.com
Address:  8.8.8.8

www.google.com
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Non-authoritative answer:
Name:    www.google.com
Addresses:  2607:f8b0:4000:816::2004
          216.58.218.100
if you can resolve dns from the server 8.8.8.8 but not your internal dns server the problem could be your internal dns resolver.
Jose Gabriel Ortega CastroTop Rated Freelancer on MS Technologies
Awarded 2018
Distinguished Expert 2018
Commented:
Well step 1. NSLOOKUP

>nslookup
>google.com

Step2. Make sure you can resolve your internal DNS.
Internal.company.com

>internal.company.com
if it resolves internal DNS is good.

Now we need to check the Forwarders to the external DNSs

On a DC, go to DNS GUI, then open the server, right click on server name / go to forwarders tab, and check that you have 8.8.8.8 and 8.8.4.4 listed or any other external DNS that you know.

after you do this we can check.

Question: your internal domain is different than your external?

Author

Commented:
Public DNS.  Something happened to that domain.  *** google-public-dns-a.google.com can't find www.companyname.com: Server failed
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
Non accessible.  Website was on that domain that is non-accessible either.  Not sure what happened.  Website was hosted on that domain.
This is for external domain nothing to do with internal.
Try nslookup -type=soa companyname.com to find The primary name server

Author

Commented:
nada!  non-existent domain.
a little difference when I try to ping that domain it takes like 10sec.  trying to resolve something I think.  when I try to ping completely bogus stuff like... ping aodfhhhghouihsfdaghoi.com it comes immediately with Ping request could not find host
Sounds like there is an issue at the domain registrar.  Do you have access to the godaddy account?  Did you recently migrate to office365?

Author

Commented:
That's what I am thinking.  
omain Name: comanychangedname.COM
   Registry Domain ID: somenumber_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.godaddy.com
   Registrar URL: http://www.godaddy.com
   Updated Date: 2018-04-23T18:29:38Z
   Creation Date: 2015-06-20T23:47:23Z
   Registry Expiry Date: 2019-06-20T23:47:23Z
   Registrar: GoDaddy.com, LLC
   Registrar IANA ID: 146
   Registrar Abuse Contact Email: abuse@godaddy.com
   Registrar Abuse Contact Phone: 480-624-2505
   Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
   Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
   Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
   Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
   Name Server: ANDY.NS.CLOUDFLARE.COM
   Name Server: JUNE.NS.CLOUDFLARE.COM
   DNSSEC: unsigned
Lookup your domain WHOIS record. Check the DNS servers in the WHOIS. Can you ping those DNS servers? Can you perform a lookup against those DNS servers? Log into the account you have with your registrar and validate everything is OK. Contact your registrar and DNS providers on call numbers and find out what is going on.
Not familiar with cloudflare dns service but it looks like those are primary dns servers.  Quick google-fu and looks like they have some issues in the last couple of months.

Author

Commented:
Yes, DNS servers seems OK.  Can ping and resolve by name.   Let me find logins to the godaddy.  I am not the primary account owner there.
Thanks gents!
Were you able to resolve your issue?

Author

Commented:
sorry for the delay. Looks like things getting better.  Possibly registrar is trying to recover..

C:\>nslookup -type=soa domainname.com
Server:  UnKnown
Address:  192.168.1.1

Non-authoritative answer:
domainname.com
        primary name server = ns67.domaincontrol.com
        responsible mail addr = dns.jomax.net
        serial  = 2018070300
        refresh = 28800 (8 hours)
        retry   = 7200 (2 hours)
        expire  = 604800 (7 days)
        default TTL = 600 (10 mins)
well, I'm glad things are getting sorted out.


cheers

Author

Commented:
thanks bunch!

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial