AD Integrated DNS, Capitalization of FQDN problem

External Since: Jun 25, 2008 Posts: 1

Hello, new to the group,

I am having a strange problem with a DNS server capitalizing a few
entries in our AD integrated DNS server.

When I type in a particular set of hosts and aliases for these hosts,
after:

1) a restart of DNS
2) a refresh of the mmc console
and
3) a reload of the DNS

the FQDN of the machine is all in caps. I have tried everything
apparent to me, including:

- deleting the entries, clearing the cache, reloading DNS, updating
server files, making sure WINS is turned off, and every combination of
the above.

This is an issue because we have Solaris boxes using this DNS and when
it returns the names/aliases as all caps we have apps that cannot
handle that.

Google was not helpful, and I have not see this issue before. Anyone
seen anything like this?

Thanks,
Kelly

External Since: Dec 31, 2006 Posts: 454

"kkoechel" <kkoechel.DeleteThis@gmail.com> wrote in message
news:d680acb8-e4fb-4448-ab36-c308807a71a5@z72g2000hsb.googlegroups.com...
> Hello, new to the group,
>
> I am having a strange problem with a DNS server capitalizing a few
> entries in our AD integrated DNS server.

DNS resolution is not case sensitive so it is only a cosmetic issue.

> When I type in a particular set of hosts and aliases for these hosts,
> after:
>
> 1) a restart of DNS
> 2) a refresh of the mmc console
> and
> 3) a reload of the DNS
>
> the FQDN of the machine is all in caps. I have tried everything
> apparent to me, including:

What machine?

Where and how are you seeing this? Use NSLookup and specify both
the lookup name AND the DNS server to use (post request command
and the answer along with an IPConfig /all.)

> - deleting the entries, clearing the cache, reloading DNS, updating
> server files, making sure WINS is turned off, and every combination of
> the above.
>
> This is an issue because we have Solaris boxes using this DNS and when
> it returns the names/aliases as all caps we have apps that cannot
> handle that.

Odd since DNS is not supposed to be cases sensitive no app should care.

Those apps are broken -- while it is normal for Unix-like machines to
use case sensitive FILE names -- case sensitive DNS is not according
to the RFCs

> Google was not helpful, and I have not see this issue before. Anyone
> seen anything like this?

Are you perhaps using a CAPITALIZED Primary (or connection specific)
DNS Suffix and then not specifying a suffix on the lookup?

(Client would then supply the capitalized suffix which the DNS Server
will happily resolve since DNS is not case sensitive.)