MX records for new additional domain on existing authoritative name servers
Matthew Pounsett
matt at conundrum.com
Tue Mar 30 20:50:41 UTC 2010
Hi Karen.
Please don't start a new thread by replying to an email in an existing discussion -- your message can get lost in that other discussion, rather than appearing as a new topic for anyone who threads their email.
On 2010/03/30, at 16:30, Lear, Karen (Evolver) wrote:
> I'm adding a new domain to my existing authoritative name servers, and need to add an MX record for a device on the existing domain. That device will serve both domains until we get a new box in and then we will have separate MX records/devices for each domain. I have created a new zone file and modified named.conf to include the new zone. When I run named-checkzone, I get a message about the MX record being out of zone and not having an A record. However, at the end of my named-checkzone output, I get "OK." Can I restart named as is without causing problems or do I need to address these messages?
It sounds like you're including a record for mx1.olddomain.gov in the newdomain.gov zone. It's hard to be sure without seeing specifics from your configuration though.
>
> Thx,
>
> [klear at mynameserver]$ sudo named-checkzone -t /dns/chroot/conf -D NEWDOMAIN.gov MYNEWZONEFILE
> zone NEWDOMAIN.gov/IN: NEWDOMAIN.gov/MX 'MX1.OLDDOMAIN.gov' (out of zone) has no addresses records (A or AAAA)
> zone NEWDOMAIN.gov/IN: NEWDOMAIN.gov/MX 'MX2.OLDDOMAIN.gov' (out of zone) has no addresses records (A or AAAA)
> OK
> _______________________________________________
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
More information about the bind-users
mailing list