create domain tracking

potschops

Member
Hello friends,

I have a server with dedicated IP in OVH.

I installed Webmin with Virtualmin.

I added only 1 domain and mailwizz installed in that domain.

But when you add the service "Tracking domain", placing the cname, example.dominio.com points to example.com does not recognize the server.

I have also created a subdomain if needed, but not working.

Note: to access the IP or to track.example.com not redirected to Mailwizz, however; shows:



any suggestions?
 
Did you click Apply Changes first?

If not, below:
Webmin->Servers->Apache Webserver->Apply Changes
Webmin->Servers->WhatEverDNSYou'reUsing->Apply Changes
 

potschops

Member
According to what you said, here I eliminated a virtual server where the file ip pointed demonstration of apache (I think I did well).



However, I do not know that I do here
 

twisted1919

Administrator
Staff member
Seems your dns is hosted with cloudflare?
When i query your dns records, using this:
PHP:
<?php
$dnsRecords = (array)dns_get_record('aimails.com', DNS_ANY);
print_r($dnsRecords);
i get:
Code:
$ php cname.php
Array
(
    [0] => Array
        (
            [host] => aimails.com
            [class] => IN
            [ttl] => 4737
            [type] => HINFO
            [cpu] => Please stop asking for ANY
            [os] => See draft-jabley-dnsop-refuse-any
        )

)
So the dns server does not return any info.


Same happens if instead of asking the dns server for any record, i ask specifically for cname only:
PHP:
<?php
$dnsRecords = (array)dns_get_record('aimails.com', DNS_CNAME);
print_r($dnsRecords);
i get:
Code:
$ php cname.php
Array
(
)
So again, your DNS server does not return any proper info to use.
 

You need to edit your master zone and create records for the following if not done already:
A records for www.domain.com, ns1.domain.com, ns2.domain.com and (mail or mx).domain.com point your IP address.
NS records for ns1.domain.com & ns2.domain.com
MX record for mail or mx.domain.com.
CNAME record track.domain.com pointing to mailwizz.domain.com
TXT records for DKIM & SPF (if needed)

Handle that first, then you can worry about Apache.

I really hate control panels & BIND. Give me PowerDNS or djbdns anyday of the week.
 

potschops

Member
In cloudflare I had targeted all records without problems, however when changing records pointing directly to the server, I had forgotten the nameserver, however and just placed. Let's wait a bit to spread. Thank you
 

twisted1919

Administrator
Staff member
They look good. make sure you restart bind after you add them.
However, for now, your host doesn't answer at ping:
Code:
ping: cannot resolve www.aimails.com: Unknown host
 
you think are good DNS records like this?

Combine the two SPF records into one and get rid of all of those DNS lookups.
"v=spf1 ip4:158.69.xxx.xxx include:mailgun.org ~all"

You need to make a habit in keeping your SPF record as small as possible or use variables that don't count as DNS lookups (all, ip4, ip6) as possible when you're including other people's SPF record. They can change it on the fly without you knowing and your SPF records hits the 10 record limit which will result in giving you a "SPF PermError".

See how Mailgun is set up?

dig txt mailgun.org (two lookups here):
"v=spf1 include:spf1.mailgun.org include:spf2.mailgun.org ~all"

dig txt sp1.mailgun.org (no lookups here):
"v=spf1 ip4:173.193.210.32/27 ip4:50.23.218.192/27 ip4:174.37.226.64/27 ip4:208.43.239.136/30 ip4:184.173.105.0/24 ip4:184.173.153.0/24 ip4:104.130.122.0/23 ~all"

dig txt sp2.mailgun.org (no lookups here):
"v=spf1 ip4:209.61.151.0/24 ip4:166.78.68.0/22 ip4:198.61.254.0/23 ip4:192.237.158.0/23 ip4:23.253.182.0/24 ip4:23.253.183.0/24 ip4:104.130.96.0/28 ~all"
 

potschops

Member
Combine the two SPF records into one and get rid of all of those DNS lookups.
"v=spf1 ip4:158.69.xxx.xxx include:mailgun.org ~all"

You need to make a habit in keeping your SPF record as small as possible or use variables that don't count as DNS lookups (all, ip4, ip6) as possible when you're including other people's SPF record. They can change it on the fly without you knowing and your SPF records hits the 10 record limit which will result in giving you a "SPF PermError".

See how Mailgun is set up?

dig txt mailgun.org (two lookups here):
"v=spf1 include:spf1.mailgun.org include:spf2.mailgun.org ~all"

dig txt sp1.mailgun.org (no lookups here):
"v=spf1 ip4:173.193.210.32/27 ip4:50.23.218.192/27 ip4:174.37.226.64/27 ip4:208.43.239.136/30 ip4:184.173.105.0/24 ip4:184.173.153.0/24 ip4:104.130.122.0/23 ~all"

dig txt sp2.mailgun.org (no lookups here):
"v=spf1 ip4:209.61.151.0/24 ip4:166.78.68.0/22 ip4:198.61.254.0/23 ip4:192.237.158.0/23 ip4:23.253.182.0/24 ip4:23.253.183.0/24 ip4:104.130.96.0/28 ~all"
Thanks.
 
UOTE="potschops, post: 6539, member: 399"]the reverse record should place it somewhere? It is also a DNS record?

[/QUOTE]

You hosting provider "owns" that IP address you're server is running. There should be a means to change your rDNS inside the hosting provider's user interface. Change the default hostname to the hostname of your mail server (if you are running one).

will this have something to do?

An NS record points to a nameserver, not an IP address.

Make sure you have the following:
A Records
IP address (xxx.xxx.xxx.xxx) pointing to nameserver (ns1.domain.com)
IP address (xxx.xxx.xxx.xxx) pointing to nameserver (ns2.domain.com)

NS Records
nameserver (ns1.domain.com)
nameserver (ns2.domain.com)
 
Last edited:

potschops

Member
Install your operating system on the server to configure it now if you can ping the nameserver.
Hopefully now if work.
Before, there had been problems because apuntaa used cloudflare and from there straight to the ip.
 
Top