Reverse DNS for Azure VM created in Resource Manager

I have the same problem and found a solution. With an CNAME Record pointing to an PublicIpAddress DNS-Name I was abel to create the PublicIpAddress ReverseFqdn. After the Creation I have changed the CName back to an A Record Pointing to the new PublicIpAddress.

So Method 2 of the error works for me. Method 1 not.

Step by Step.

1.) New-AzureRmPublicIpAddress -Name tempstatic -ResourceGroupName cw-extesting -Location “west us” -AllocationMethod Static -domainnamelable tempstatic47115


3.) New-AzureRmPublicIpAddress -Name testingstatic -ResourceGroupName cw-extesting -Location “west us” -ReverseFqdn -AllocationMethod Static -domainnamelable testingstatic47115

4.) Change to A Record pointing to the Ip of 3. (testingstatic)

5.) Remove-AzureRmPublicIpAddress -Name tempstatic -ResourceGroupName cw-extesting

Hint: The ReverseFqdn works only in combination with domainnamelable because the method New-AzureRmPublicIpAddress checks if the domainnamelable is not empty to create the DNS Settings.



Backuppc – no ping response

no ping response

BackupPC will not start a backup if it does not receive a ping reply from a client. Here is how to backup a host when ping is blocked.

In the BackupPC webinterface, click the client host name, Edit Config, go to the Backup Settings and change the setting PingCmd ($pingPath -c 1 $host by default) to


Don’t forget to check override and click the Save button to apply the change.

BackupPC settings


Zimbra SplitDNS


Installations of Zimbra behind a firewall (or NAT Router) often require the creation of some form of split DNS, also called split-horizon or dual-horizon DNS. This is a DNS installation where machines receive different IP address answers to queries depending on whether they are (commonly) inside or outside a firewall and an IP address reply from the DNS server gives a Private Network IP address that is different than the Public IP of your internet connection. For further information on Private Network IP addresses see the following article:

This is because the Postfix mail system used by Zimbra performs a DNS MX lookup for the Zimbra server followed by a DNS A lookup when attempting to route email to the back-end message store. Frequently, this is the same physical host as Postfix. The DNS server frequently returns the external address of the mail host, not the internal address. Depending on how the firewall and network are configured, the external address may not even be reachable from the mail host, and mail will not be delivered.

Split DNS avoids this problem by providing an internal DNS server (this example uses bind or dnsmasq) that can be used to resolve the internal address of the server. This guide will detail how to set up a very specific, single-host DNS server (i.e. bind or dnsmasq) that can be installed on the Zimbra host itself so that it can resolve its own address. This should not be used for a multi-node Zimbra installation, and should not be used as the DNS server for any other hosts on your network.

It is possible to use a generalized split-horizon DNS server to perform this function, but it will need to be set up differently, and many people recommend against it because even a couple ms of delay can be too much on a heavily loaded system. If you decide to use another DNS server on your LAN then any functioning DNS server that provides a LAN IP response for the DNS MX lookup of the Zimbra server will do (BIND, Active Directory, PowerDNS etc.), check the ‘Verify…’ section in this article for details on how to check that your DNS server is configured correctly.

Attention! the use of Bind or dnsmasq are mutually exclusive, you have to setup one OR the other!

Configuring Bind on the Zimbra Server

Install Bind on Red Hat Enterprise Linux

Use up2date to download bind from Red Hat Network.

Install bind9 on Ubuntu/Kubuntu Hardy Heron

apt-get install bind9

You could also make sure it is installed from Synpatic Package Manager or Adept.

Edit the named.conf file

  • Substitute your fully-qualified server name for
  • If named runs in a chroot’ed directory (i.e. /var/named/chroot), named.conf should be placed in

/etc/named/chroot/etc/named.conf and you should create a symbolic link to /etc/named.conf,

  1. i.e. ln -s /etc/named.conf /etc/named/chroot/etc/named.conf
  2. or ln -s /etc/bind/named.conf /etc/bind/named/chroot/etc/named.conf
  • For Red Hat, edit: /etc/named.conf
  • For Ubuntu/Kubuntu, edit: /etc/bind/named.conf.options
// Default named.conf generated by install of bind-9.2.4-2
options {
       directory "/var/named";
       dump-file "/var/named/data/cache_dump.db";
       statistics-file "/var/named/data/named_stats.txt";
forwarders { <address of current DNS server> ; };
include "/etc/rndc.key";
// We are the master server for
zone "" {
    type master;
    file "";

Make sure to set the forwarders to match the DNS servers currently in use on your system. The forwarders setting allows the server to query those DNS servers for any addresses for which it is not authoritative.

Create a /var/named/ zone file

  • If named runs in a chroot’ed directory /var/named/chroot, should be placed in /etc/named/chroot/var/named/ and you should create a symbolic link to /var/named/
;       Addresses and other host information.
@       IN      SOA (
                               10118      ; Serial
                               43200      ; Refresh
                               3600       ; Retry
                               3600000    ; Expire
                               2592000 )  ; Minimum
;       Define the nameservers and the mail servers
        IN      NS      <internal address of server>         IN      MX      10    IN      A       <internal address of server>

Change /etc/resolv.conf

  • Change /etc/resolv.conf to use the Zimbra server as the primary DNS address.
  • Also remember to change the search path to be the name of the Zimbra server.

Start named on the zimbra server

/etc/init.d/named start

Enable autostart of named on boot

chkconfig named on

Configuring dnsmasq on the Zimbra Server

dnsmasq is a very powerful tool that can provide basic dns services/caching, act as dhcp server and also as tftp server. It’s also easy to setup. So you can use dnsmasq INSTEAD of bind following these instructions.

Install dnsmasq on Debian GNU/Linux

aptitude install dnsmasq

Edit the /etc/dnsmasq.conf file

Let’s say that upstream dns are and Put only these lines in the config file:


Edit the /etc/hosts file

The loopback line should look like this: localhost.localdomain localhost

You need a line to resolve the IP of to the private IP of the zimbra server, so make sure you have: mail

Edit the /etc/resolv.conf file

To have the host resolv through dnsmasq, you have to set your localhost ( as nameserver


Restart dnsmasq

To have the settings take effect, you have to restart dnsmasq

/etc/init.d/dnsmasq restart

Verify that everything is working

To verify that your configuration of DNS is correct you should run the following commands on the Zimbra server itself (the expected output is in the boxes below the commands).: This is true whatever DNS program you use for this kind of configuration (i.e. dnsmasq instead of bind9).

dig mx

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> mx
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20907
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 2

;                IN      MX

;; ANSWER SECTION: 7200    IN      MX      30


;; Query time: 4 msec
;; WHEN: Thu Jul 15 14:38:48 2010
;; MSG SIZE  rcvd: 140

dig any

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> any
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36845
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 8, AUTHORITY: 0, ADDITIONAL: 4

;                IN      ANY

;; ANSWER SECTION: 7200    IN      NS 7200    IN      A 7200    IN      SOA admin. 2010051304 10800 3600 1814400 7200 7200    IN      MX      10 7200    IN      NS

;; ADDITIONAL SECTION: 7200 IN     A  7200 IN     A  7200 IN     A 

;; Query time: 11 msec
;; WHEN: Thu Jul 15 14:38:52 2010
;; MSG SIZE  rcvd: 367

host $(hostname) has address

NOTE: The host $(hostname) command should be typed exactly as you see, don’t change the word “hostname” to anything else.

You should also note that the output on your system may be slightly different than above examples but there should be an A record that points to the LAN IP address of your Zimbra server and an MX record that contains the FQDN (Fully Qualified Domain Name – that’s the hostname plus the domain name and it’s in the examples) of your Zimbra server.

You should also make sure that the DNS server that is responding to your dig commands is the one you have configured on your LAN and it’s the one that has your Zimbra server DNS records. If you see any IP that is not the correct LAN IP or the correct DNS server then you have entered the wrong information in your DNS configuration files.

If you’re asked in the forums to provide the information to confirm your DNS is correct then, in addition to the above information, you should also supply the output of the following commands (run on your Zimbra server):

cat /etc/resolv.conf
cat /etc/hosts

In this article it’s assumed that you’re installing the DNS server on your Zimbra server so your resolv.conf should look like this:


Although it’s mentioned in other articles it bears repeating that your hosts file should look like this: localhost.localdomain localhost mail

The line for the loopback adapter ( should be formatted as shown. The hosts file should also be formatted as shown and have the LAN IP of your Zimbra server (as shown in the DNS records) and contain the hostname (mail) and your domain name ( which gives you the Fully Qualified Domain Name (FQDN) of your server ‘’.

If you have a number of servers inside the firewall that need to use internal addresses to communicate to each other, you should consider setting up a full internal DNS server that can be authoritative for the whole domain. This example is not suitable for this task.

For information on performing the same task w/ TinyDNS / DJBDNS:

Additional Information: Zimbra Power Tip:


How to connect two vm via an internal network (Proxmox)

1. go to your host-node symbol, select Network tab and Create -> Linux Bridge, e.g. vmbr1 (no further parameters)

2. stop virtual machines (if they are running)

3. go to each virtual machine, select HW tab and
– Add -> Network Device, Bridge: vmbr1, “Bridged Mode” (if you want to have an additional virtual NIC)
– select proper Network Device -> Edit and adapt the settings as above (if you want to use an existing virtual NIC)

4. reboot proxmox host