Windows 10: "Couldn't be delivered. The Domain Name System DNS reported that the recipient's domain...

My domain is not available what should I do I was about to withdraw payment from a website but it gave me a message that my domain is not available* Moved from Community Center** Original title: couldn't be delivered. The Domain Name System DNS reported that the recipient's domain does not exist.

:)

 

Getting a domain name...

Just simple 3 steps to make your website glow to millions…
Step 1: Sign up now and get a FREE domain!
Step 2: Design your new website in minutes!
Step 3: You are live! Share your life online!

Click here…

 

Windows 'domain'?

Hello,

Thank you for sharing your concern in the Microsoft Community. Follow these steps to find the domain name:

• Press the Windows key + R then choose System.
• The name of your computer will be listed as the Full computer name.
• The domain your computer belongs to will be listed as the Domain. If, instead of Domain, you see Workgroup, your computer
  is not a member of any domain.

If you have any questions or things you'd like to clarify, feel free to ask.

 

Additional DNS suffixes not checked if there's a dot in the partial domain name

Windows has always had the "Append these DNS suffixes" list in network adapter (IPv4) properties.

However, there's a difference in behavior between nslookup.exe and windows itself.

I wish I could find a workaround for this...

I have a forest of domains, names masked for security, length kept approximately intact.

External domain, registered, used for e-mail etc.: aaaaaaaaa.net

Internal top level AD domain: bbb.aaaaaaaaa.net.

(Having bbb there allows for split DNS, base domain forwarded to external server, only bbb and subdomains DNS-hosted internally in AD.)

Child domains: ccccccc.bbb.aaaaaaaaa.net, dddddddd.bbb.aaaaaaaaa.net, etc.

A server name may look like, for example, ccccccc-serv3.ccccccc.bbb.aaaaaaaaa.net

To avoid a lot of typing, I decided to try and add "bbb.aaaaaaaaa.net" to the DNS suffix list, but it turns out to be useless.

It works in nslookup.exe:

Code:

nslookup ccccccc-serv3.ccccccc
Server:  zzzzzzzz.bbb.aaaaaaaaa.netAddress:  10.250.9.1

Code:

Non-authoritative answer:Name:    ccccccc-serv3.ccccccc.bbb.aaaaaaaaa.netAddress:  10.13.1.9

But that's the only place where it works, if there is a period in the name being looked up.

Code:

ping ccccccc-serv3.ccccccc
Ping request could not find host ccccccc-serv3.ccccccc. Please check the name and try again.

Same when trying to connect to a share, trying to connect with RDP, etc.

Why can't Windows' built in network support treat this the way nslookup does?