> -----Original Message----- > From: Thomas E. Dukes > Sent: Sunday, June 22, 2003 11:15 AM > Subject: RE: DNS problem: Can't resolve myself > > > > Exactly why are you loading the above zone? Your DNS server > > is NOT the SOA for dnsalias.net. Since I have never used > > dnsalias.net, I can only guess that they would have a > > "delegation" record in their dnsalias.net zone that delegates > > palmetto.dnsalias.net to your SOA server. IN other words, > > shouldn;t you be loading palmetto.dnsalias.net? > > Its just a file name. I changed it as you suggested.
I understood the difference between the filename and the zone names. (see below) > > > > dnsalias.net.zone: > > > $ttl 38400 > > > palmetto.dnsalias.net. IN SOA > > > ns1.palmetto.dnsalias.net. > > > edukes.palmetto.dnsalias.net. ( > > > 2003033006 > > > 10800 > > > 3600 > > > 604800 > > > 38400 ) Above you are specifying an SOA record for palmetto.dnsalias.net, in your previous post example you loaded the zone as dnsalias.net, not palmetto.dnsalias.net. > > > palmetto.dnsalias.net. IN NS > > > ns1.palmetto.dnsalias.net. > > > palmetto.dnsalias.net. IN A 10.10.0.1 > > > mail.palmetto.dnsalias.net. IN CNAME Above are the NS, A and CNAMES all for palmetto.dnsalias.net, but my point was you loaded the zone as dnsalias.net in named.conf, not palmetto.dnsalias.net. In a normal delegation, the TLD (dnsalias.net) would specify the NS records (the delegation records) for palmetto.dnsalias.net in their zone file. > palmetto.dnsalias.net. > > > > You are specifying dnsalias.net in your zone definition > > (named.conf) above, but loading the delegated zone > > (palmetto.dnsalias.net) without first specifying the glue > > records for dnsalias.net. i.e. the TLD. > Can you please explain. It is/was just a file name. Hopefully, the above has helped to clarify this. > > > Personally, I do not see how this has ever worked. Again, I > > have never used dnsalias.net, but I would think the zone name > > specified in named.conf should match. i.e. palmetto.dnsalias.net. > > Its worked fine except for not being able to access the sites from the > server. After making the filename changes, restarting named, > still have the same problem. Since this seems to be magically working, your problem is probably related to your resolver lib configuration. Check your /etc/resolv.conf and make sure you are specifying your own name server "first". Plus make sure your /etc/hosts file is not accidently specifying something you do not want. Steve COwles -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list