Win 2003 DNS and Bind Issue

[Eyas]

Hi

I'm trying to set up an environment using a Win2003 DNS as primary server and a Linux-based Bind (unsure of the version but it isn't the newest installation) as a secondary DNS. I get the zone transfers to work just fine but there seems to be some problem with how the different servers interpret the records.

The Win DNS zone [ex12345.zone.com] is setup in the following way:

ex12345. A 192.168.0.1
server. CNAME ex12345.
www. CNAME ex12345.

This file is transfered to the Bind server looking exactly the same. The . at the end of each host is automatically added by the Win DNS. If I recall it correctly the . will tell the Bind server that it is the complete hostname and thus it will not add the rest of the words, in this case ex12345.zone.com. Is this correct?

The question in short:
The Win DNS will interpret the server name as ex12345.ex12345.zone.com while the Bind DNS interpret it as ex12345. Is this correct? If yes, which one is right according to the RFC?

T.I.A.

/Tommy

 

[ShackDaddy]

It doesn't sound to me like the Win server is properly formatting the zone file. According to RFC, there shouldn't be any trailing . on those short records.

As far as your question: I think your expectation of how each server will interpret the names is accurate, unless there's something special about zone transfer files that make those extra .'s ok. From the RFC, there shouldn't be any. Technically, both servers should refuse to add on the domain name, but if the Windows server ignores the period, I wouldn't be surprised.

Is the zone in question AD-integrated?

When you ping one of those cnames or the A-record name from a client that is pointed at your Windows server, does the ping also include a fully resolved name that lists everything back to the .com?

Was there anything non-standard about how the records were initially created? When you use the DNS Admin tool on the Windows server, do the periods appear?

ShackDaddy

 

[Eyas]

Hi

I've managed to solve the matter. It turns out that the command DNSCMD adds a "." to the end of a CNAME-record. This is interpreted as a FQDN.

When I add the CNAME-racord via the admin tool in Windows it works fine.

Thanks for the answer.

/Tommy