> -----Original Message----- > From: Anthony E. Greene > Sent: Saturday, February 22, 2003 7:01 PM > Subject: Re: Sendmail Problem > .... > Your NS records for icesource.com look strange too. I'm not a > BIND guru, but it doesn't seem right to have the name of the > target domain appended directly onto the nameserver's hostname: > > ************************************************************** > ********** > > [EMAIL PROTECTED] agreene]$ host -a icesource.com > Trying "icesource.com." > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16649 > ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 1, ADDITIONAL: 0 > > ;; QUESTION SECTION: > ;icesource.com. IN ANY > > ;; ANSWER SECTION: > icesource.com. 37796 IN NS > ns1.axelis.com.icesource.com. > icesource.com. 37796 IN A 66.12.123.173 > > ;; AUTHORITY SECTION: > icesource.com. 37796 IN NS > ns1.axelis.com.icesource.com. > > Received 90 bytes from 68.48.0.5#53 in 22 ms > ************************************************************** > *********** > > > I queried several other domains, and none looked like that. > As I said, I'm not a guru. but if you don't know why that > appears like that, you should check it out.
You are correct! The OP forgot to fully qualify his name server record (trailing dot) so bind will append the zone origin (icesource.com in this case) to the name. i.e. icesource.com. in ns ns1.axelis.com vs. icesource.com. in ns ns1.axelis.com. This is a very common configuration mistake. Steve Cowles -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
