Name Records Transfers Look Odd -> Using Webmin to administer Bin d 9.1

phn at icke-reklam.ipsec.nu phn at icke-reklam.ipsec.nu
Mon Apr 29 18:27:34 UTC 2002


Brian Guild <Brian at body1.com> wrote:

> Guys,

> Below is my zone record for one of my domains, shoulder1.com.  As you can
> see, I have listed two name servers in the master zone because I was told
> this is good practice.  When using Webmin, for some reason it populates the
> first column of the NS record with the zone name, even when I leave that
> entry space blank.

> Now, when I set up my slave zone, all of the records transfer perfectly,
> except for the NS records.  On the slave DNS server, it receives
> "dns1.body1.com.shoulder.com" as primary name server, but it also lists
> "dns2.body1.com.shoulder1.com" as the secondary.  Seems as though it is
> reapplying the zone name to the end of the NS record.  There is no doubt it
> is doing this because it is reading it off of the primary.  I am concerned
> this will cause a problemHas anyone seen anything like this? Does anyone
> know how to get webmin to not insert the zone name prior to the NS record
> without having to manually edit the record file?

Your problems occur since you forgot the trainging dot '.' after the 
nameservers names. 

It should look like :

shoulder1.com.	IN	NS	dns1.body1.com.
shoulder1.com.	IN	NS	dns2.body1.com.

"Everything lacking traing period will have $DOMAIN appended :-)"



> Thank you,

> Brian

> $ttl 38400
> shoulder1.com.	IN	SOA	dns1.body1.com. domains.body1.com. (
> 			1019505347
> 			10800
> 			3600
> 			604800
> 			38400 )
> www.shoulder1.com.	IN	A	65.214.51.100
> shoulder1.com.	IN	NS	dns1.body1.com
> shoulder1.com.	IN	NS	dns2.body1.com
> shoulder1.com.	IN	MX	10 63.220.53.195


-- 
Peter Håkanson         
        IPSec  Sverige      (At the Riverside of Gothenburg, home of Volvo)
           Sorry about my e-mail address, but i'm trying to keep spam out.
	   Remove "icke-reklam" and it works.


More information about the bind-users mailing list