out of place mx records.

[Andrey G. Sergeev (AKA Andris)]

Hello Sten,


Thu, 28 Oct 2010 02:48:36 +0200 Sten Carlsen wrote:

> To me it looks redundant, "named-compilezone -o - zone file" should
> show you how bind interprets these.
> My guess is that they will be listed only once in the output.
> 
> I don't see how they could belong to each subdomain, to do that there
> should be a"@..." to set a new origin?

; Set current origin to "mail02"
mail02          IN      A       192.168.xx.xx
; Two lines below are still under the same origin "mail02"
		IN	MX	10	mcvpemr01	
 		IN	MX	10	mcvpemr02
; Time to set a new origin
nelson          IN	A	202.xx.xx.1
[...]


> On 28/10/10 2:14, Ian Manners wrote:
>> Hi Gregory,
>>
>>> mail02          IN      A       192.168.xx.xx
>>> 		IN	MX	10	mcvpemr01	
>>> 		IN	MX	10	mcvpemr02
>>> nelson          IN	A	202.xx.xx.1
>>> 		IN	MX	10	mcvpemr01
>>> 		IN	MX	10	mcvpemr02
>>> My question is why would "IN    MX    10    mcvpemr01" and "IN
>>>    MX 10    mcvpemr02" be repeated trough the zone file surely
>>> this is redundant ?
>> It looks like an old way of specifying the MX for each subdomain.


-- 

Yours sincerely,

Andrey G. Sergeev (AKA Andris)     http://www.andris.name/