I get the warning: "SOA 'mname' field does not exist" for fcom.ch (and all other zones on that DNS server as they all are configured that way).
The SOA MNAME is configured as ".", this as the MNAME is used by customers's machines to lookup the host they can send DNS UPDATEs (https://tools.ietf.org/html/rfc2136)
Of course, we do not allow DNS UPDATE to our authoritive, static server. There are thus a lot of DNS UPDATE queries being sent to any host configured in the MNAME (fcom.ch is used for reverse DNS for 400k++ cable hosts), which otherwise causes a lot of useless traffic.
Setting the MNAME to '.' (or empty when dot-stripping as likely happens in the test), indicates to DNS UPDATE tools that there is no DNS server to send DNS UPDATEs too, as there is no host specified that could receive them.
As such, having a SOA MNAME configured to just '.' is quite valid and actually recommended for most locations as most locations do not support DNS UPDATEs.
Greets,
Jeroen
I get the warning: "SOA 'mname' field does not exist" for fcom.ch (and all other zones on that DNS server as they all are configured that way).
The SOA MNAME is configured as ".", this as the MNAME is used by customers's machines to lookup the host they can send DNS UPDATEs (https://tools.ietf.org/html/rfc2136)
Of course, we do not allow DNS UPDATE to our authoritive, static server. There are thus a lot of DNS UPDATE queries being sent to any host configured in the MNAME (fcom.ch is used for reverse DNS for 400k++ cable hosts), which otherwise causes a lot of useless traffic.
Setting the MNAME to '.' (or empty when dot-stripping as likely happens in the test), indicates to DNS UPDATE tools that there is no DNS server to send DNS UPDATEs too, as there is no host specified that could receive them.
As such, having a SOA MNAME configured to just '.' is quite valid and actually recommended for most locations as most locations do not support DNS UPDATEs.
Greets,
Jeroen