Error no domain set

Junior Member

Junior Member

Проверьте соединения DC вообще: Ссылка

И в заключение есть похожая тема в новостных группах: Ссылка

Источник

How to Fix No Domain Under Control Error in iRedMail

While I’m setting up a mail server on Ubuntu 18.04 with iRedMail 0.9.8, I encountered the “No domain under control” error in iRedAdmin panel. This article will explain how to fix this error.

Fixing No Domain Under Control Error in iRedMail

Although the postmaster account is the global admin of the email server, iRedAdmin told me that no domain is under control. The domain name can’t be deleted from iRedAdmin panel. You need to delete the domain name from MySQL/MariaDB database and add it back in iRedAdmin panel. The following steps are for MariaDB users on Ubuntu.

Log into MariaDB shell. (Enter sudo user password, not MariaDB root password)

Select the vmail database.

Check available domains in the domain table.

Delete your first domain name in the domain table.

Exit MariaDB shell.

Then add it back in iRedAdmin panel.

Configuring Amavis DKIM Signing

If the above error happened to you, then amavis is likely not working. You can check the status of Amavis by running the following command.

As you can see, Amavis is not running on my server because the private key file is not found. You can generate the private key with:

Then restart Amavis.

Show the public key.

In your DNS manager, create a TXT record. Enter dkim._domainkey in the Name field. Copy everything in the parentheses and paste into the value field. Delete all double quotes.

After saving your changes. Check the TXT record with this command.

That’s it! I hope this article helped you fix the no domain under control error in iRedMail.

Источник

Contact US

Thanks. We have received your request and will respond promptly.

Come Join Us!

• Talk With Other Members
• Be Notified Of Responses
  To Your Posts
• Keyword Search
• One-Click Access To Your
  Favorite Forums
• Automated Signatures
  On Your Posts
• Best Of All, It’s Free!

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

mountd[12314]: [ID 664212 daemon.error] No default domain set

mountd[12314]: [ID 664212 daemon.error] No default domain set

mountd[12314]: [ID 664212 daemon.error] No default domain set

Can someone tell me why I see this message in /var/adm/messages.
mountd[12314]: [ID 664212 daemon.error] No default domain set

/etc/defaultdomain is not set, but we are not using NIS. I thought that was the only time the file was needed.

Solaris 8 — kernel 18
SunFire 6800

RE: mountd[12314]: [ID 664212 daemon.error] No default domain set

Are you sure that autofs is not running? Autofs trys to mount nfs shares when you try to access those directories.

Make sure there aren’t any auto_[something] in /etc. Those should be a moot point though if autofs is not running. You should eb able to safely shutdown autofs by running:

Hope this helps!

RE: mountd[12314]: [ID 664212 daemon.error] No default domain set

RE: mountd[12314]: [ID 664212 daemon.error] No default domain set

It sounds almost like it is trying to pull the automount info from nis and the /etc/defaultdomain file is not present. check the /etc/nsswitch.conf file and see what the setting is for automount. If it has nis in that line, remove it so it only says files.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Источник

FIX: The Specified Domain Either Does Not Exist or Could Not Be Contacted (Solved)

This tutorial contains instructions to resolve the following problem, when you try to join a Windows based computer to an existing domain: «The Specified Domain Either Does Not Exist or Could Not Be Contacted».

The error «The Specified Domain Either Does Not Exist or Could Not Be Contacted» commonly occurs due to invalid DNS settings on the workstation’s side, because Active directory requires you to use domain DNS to work properly (and not router’s address).

How to fix: Specified Domain Does Not Exist or Could Not Be Contacted.

Let’s suppose that your Active Directory Domain Controller (and DNS Server) is a Windows Server 2016 machine and is responsible for the domain «wintips.local» and has the IP Address «192.168.1.10».

At this example, the IP and the Preferred DNS address on the Primary Domain Controller (Server 2016) must be the same, e.g.

Method 1. Set the Preferred DNS Server Address to match the Domain Controller’s IP Address (on Client Workstation)

To resolve the «Specified Domain Does Not Exist or Could Not Be Contacted» error, you have to set the Preferred DNS IP to point to Primary Domain Controller’s IP address, on each client workstation that you want to join in the domain. To do that:

1. Open Network and Sharing Center.
2. Right click on Local Area Connection and click Properties.
3. Double click on Internet Protocol TCP/IPv4.
4. Change the Preferred DNS server address to match the Primary Domain Controller’s IP Address (e.g. «192.168.1.10» in this example).
6. Click OK twice and close all windows.

7. Try to join the workstation in the Domain.

Method 2. Specify the WINS Server’s IP Address on Client.

If your Active Directory Domain Controller acts also as a WINS server, then set the WINS IP address to point to WINS Server’s (Primary Domain Controller’s IP address),* on the client machine that you want to join to the Domain. To do that:

* Note: This method works even when the Primary Domain Controller does not act as a WINS Server.

1. Open Network and Sharing Center.
2. Right click on Local Area Connection and click Properties.
3. Double click on Internet Protocol TCP/IPv4.

4. Click the Advanced button.

5. At WINS tab, click Add.

6. Type at WINS Server’s IP Address filed, the IP address of the WINS server (e.g. «192.168.1.10» in this example) and click Add.

7. Press OK three (3) times to apply changes and close all windows.

8. Try to join the machine in the Domain.

That’s it! Let me know if this guide has helped you by leaving your comment about your experience. Please like and share this guide to help others.

Источник