Neil wrote:
Jason S writes:
I had absolutely no trouble just setting up axfrdns and using the
'Import Domains via AXFR' tool in vegadns. It was very minimal work.
Here's an explanation of the data file format:
http://cr.yp.to/djbdns/tinydns-data.html
Hi Jason,
Axfrdns is now working. I was able to import the dns entries. However, I
have a question regarding a record that was imported. Earlier, when I
created this MX, I didn't see any trailing dot.
BEFORE in vega: mail.nonexistent.com
AFTER import in vega: mail.nonexistent.com.
Now, I imported it via vega and it has a trailing dot now. Are there any
issues with it? I remember back in my BIND days when I create SOA. There
should be a trailing dot. However, what I'm showing is an MX record. The
trailing dot also happened to the NS record after it was imported.
Thanks,
Any fully qualified domain name SHOULD have a trailing dot. Many times
they are left off, though. tinydns allows them to be optional in the
data file. But it advertises them, which is why axfrdns is advertising
them. All VegaDNS does is parse the output from axfr-get. It is not
adding the trailing dot.
Regards,
Bill
