You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For domain in Sentora I added:
MX
HOSTNAME: @
TARGET: zeus.domain.com
SPF
HOSTNAME: zeus
TARGER: v=spf1 a ~all
The error output is:
zone domain.com/IN: domain.com/MX 'zeus.domain.com' has no address records (A or AAAA) zone domain.com/IN: 'zeus.domain.com' found SPF/SPF record but no SPF/TXT record found, add matching type TXT record zone domain.com/IN: loaded serial 2015022528 OK
Then adding TXT:
HOSTNAME: zeus
TAGERT: IP_of_zeus
Im getting:
ERROR DNS NOT SAVED
Hostnames must be unique.
Same thing when adding A record for zeus
I had to bypass checking via adding those by hand to database, which make them work, but still this is a bug that will prevent people to do this the safe way (via gui that validate data)
The text was updated successfully, but these errors were encountered:
Note that the bug report here: #49 has been resolved by checking if DNS records exist of the same type and name - which is actually fine - it's called round robin DNS.
Again I suggest we could simply remove the same-name same-domain DNS check - it's never valid to block DNS records with the same name and same domain, regardless of whether they are the same type.
For domain in Sentora I added:
MX
HOSTNAME: @
TARGET: zeus.domain.com
SPF
HOSTNAME: zeus
TARGER: v=spf1 a ~all
The error output is:
zone domain.com/IN: domain.com/MX 'zeus.domain.com' has no address records (A or AAAA) zone domain.com/IN: 'zeus.domain.com' found SPF/SPF record but no SPF/TXT record found, add matching type TXT record zone domain.com/IN: loaded serial 2015022528 OK
Then adding TXT:
HOSTNAME: zeus
TAGERT: IP_of_zeus
Im getting:
ERROR DNS NOT SAVED
Hostnames must be unique.
Same thing when adding A record for zeus
I had to bypass checking via adding those by hand to database, which make them work, but still this is a bug that will prevent people to do this the safe way (via gui that validate data)
The text was updated successfully, but these errors were encountered: