Is pFsense writing invalid MX dns entry for TinyDNS?

janisve

Hello.

I have a problem with DNS Server package. All works well except for MX records - when I define MX record for host example.com to use mail.example.com and afterwards use A entry for mail.example.com to x.x.x.x

then when i

dig example.com MX

;; ANSWER SECTION:
example.lv.		86400	IN	MX	0 10.mx.example.com.

which is not mail.example.com… :(. Well it works if i define A entry for 10.mx.example.com. but for some situations i actually need to put ASPMX.L.GOOGLE.COM. there.

cat /var/etc/tinydns/root/data
```gives

...
@example.com:mail.example.com.:10
...


According to documentation (http://www.pjvenda.net/linux/doc/tinydns/) shouldn't there be

@example.com::mail.example.com.:10


Edit:
**Workaround 1**
Ohh, writing this topic i noticed the RAW entry I can use:
![](http://img253.imageshack.us/img253/8106/ss20101109150603.png)

and dig'ging works as expected:

;; ANSWER SECTION:
example.com. 86400 IN MX 10 ASPMX.L.GOOGLE.COM.
example.com. 86400 IN MX 20 alt1.ASPMX.L.GOOGLE.COM.


**Workaround 2**
Also, i found that you can just prepend ':' character before record data for mx to work as expected:
![](http://img254.imageshack.us/img254/5971/ss20101109151544.png)

jimp

Should be fixed now, once my checkins sync to the package server (~5 minutes).

I just happened to have a call from a support customer who noticed the same thing, then remembered a forum post mentioning MX records…

You can enter either an IP, a hostname, or both as ip:hostname in the box for an MX record. All are valid. If you enter ip:host, it will make an A record internally that points that hostname to the given IP.