DNS CNAME Record windows 2003 R2 server by IP address

aliascname-recorddomain-name-systemwindows-server-2003

I am trying to add a CNAME record to point to an ip address. I have added the CNAME record to the primary DNS server that looks like this:

foobar Alias(CNAME) 192.168.50.11

I restarted the DNS server service. When I ping the new name I get the following:

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

ping foobar

Pinging 192.168.50.11 [67.215.75.132] with 32 bytes of data:

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Ping statistics for 67.215.75.132:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

I have no idea where it is getting the 67.215.75.132 address.

nslookup returns:

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

nslookup foobar

Server: 1server

Address: 192.168.10.10

Name: 192.168.50.11

Address: 67.215.75.132

Aliases: foobar

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

1server is the machine with the DNS server service.

Best Answer

You should set a CNAME to point to the host name defined in the ADDRESS (A) record of the target host instead of the IP. So whatever hostname 192.168.50.11 is is what goes in the record, not the IP.

foobar Alias(CNAME) targetmachine

Related Solutions

Windows Server 2003 DNS added CNAME not working

Create the CNAME record "portal.domain.com" referring to "obscureServer32324name.domain.com" in the "domain.com" DNS zone. From a command-prompt, do a:

nslookup portal.domain.com

What do you get back?

Bear in mind that if "domain.com" is an Active Directory-integrated zone you could have a slight delay before the DNS server begins to resolve it.

Also on the Active Directory integrated DNS front, bear in mind that your DNS client might not be trying to resolve against a DNS server that's "looking at" the same copy of AD where you added the record (via DNSMGMT) a moment before. Force AD replication or wait 5 minutes for AD replication to complete.

You don't need to stop / restart the Microsoft DNS server for changes like this to "take".

Edit re: your comments:

Bizarre. I'm at a bit of a loss. That's a pretty common configuration, so it ought to work fine. I have several Customers with servers that are configured just that way (w/ CNAME records like "WSUS" or "antivirus", etc).

The computer you're testing from is configured to use the server computer where you added the CNAME as its DNS server-- correct?

Do the following, just be sure that you're querying out of the right zone:

nslookup -querytype=SOA domain.com

You should get back something like this:

domain.com
        primary name server = server.domain.com
        responsible mail addr = hostmaster
        serial  = 425
        refresh = 900 (15 mins)
        retry   = 600 (10 mins)
        expire  = 86400 (1 day)
        default TTL = 3600 (1 hour)
server.domain.com     internet address = 192.168.1.1

Be sure the SOA record that you get back really is referring to the server computer you expect to be seeing the zone hosted from.

We'll figure it out, it just may take a moment.

DNS Server resolves server name but NOT fully qualified domain name

Run dcdiag (dcdiag /q -show errors; dcdiag /fix - fix problems)

Related Topic