ServerBuddies Support Blog

dig, or domain information groper, provides the ability to query any domain server for information about the domains it serves. It operates in both an interactive mode and a batch query mode.

Using dig is much like using host, in that in its simplest mode you enter just the command and the name to lookup.

However, dig is more verbose by default and presents a much wider array or information, though in a somewhat less readable form.

Just like host, it is possible to query your default system resolver, or you can query a name server specified on the command line. For example, I could query name server about the google.com domain.

Above, we have a large amount of information, though not all of it is generally useful to us. First is the version of dig, and the command line options we specified.

The comes some status information, including the NOERROR designator that indicates the name was retrieve without error. If the domain did not exist, or could not be queried, there would be an NXDOMAIN error or some other error. Next are the flags of the query.

In this case, we have one query and one answer which are contained in the QUESTION and ANSWER sections below it. The next two items inform us of the number of AUTHORITY and ADDITIONAL sections that follow. In this case, the authority section gives us the primary and secondary name servers for this domain, ns1.serverbuddies.com and ns2.serverbuddies.com, and the additional section provides the IP addresses of those name servers.

The last few lines give the time the query required, the server that was queried and the port on which it was queried, the time and date on which the query was made, and the size of the message received from the name server.

Like host, dig has a mode in which you can query all of the information available about the domain. This can be done by appending the ANY argument to the end of the command line. Furthermore, the options NS, MX, CNAME, etc. are also available and do just what you would expect.

Reference - for more please check - http://doxfer.com/Webmin/

How can I create a Webmin user who can only configure one Apache virtual server or DNS domain?

In the Webmin Servers module.

Create a new user and give him access to only the Apache Webserver module.

After saving, click on Apache Webserver next to the user’s name in the list of Webmin users and use the form that appears to deny him access to everything except one selected virtual server.

Many other modules can also be configured in a similar way to restrict the access of a user to only certain DNS domains, Unix users or mail aliases.

Unable login into the domain stats

Issue: Unable to login into the stats of the domain (in Plesk). It is asking the password continuously.

<Directory "/var/www/vhosts/domainName/statistics">
         AuthType Basic
         AuthName "Domain statistics"
         AuthUserFile /var/www/vhosts/domainName/pd/d..httpdocs@plesk-stat
         require  valid-user
</Directory>

It is in that AuthUserFile, the login name as well as the encrypted password is stored.

So adding a new user login details in that file fix the problem, and you can add it as follows.

Create the encrypted password using htpasswd command.

This will fix the issue.

Note : Replace the domainName by corresponding domain name.

Getting a 404 error when logging into sqladmin of any domain

If you are getting 404 error while accessing sqladmin page, please follow the two steps shown below.

This error is due to incorrect configuration of web admin in IIS.

DNS Records for Domain Aliasses not provisioned.

Error

Resolution:

Note : Please backup old module before copying.

The concerned files are available from the following links