Weird DNS problem...

We have an intranet located internally on a windows 2003 / iis6 server - DNS handled internally on another windows 2003 server.

The intranet, amongst other functions, hosts a ecommerce store I wrote that sells nike apparel embroidered with our company logo. Up until recently, it would send an email to payroll and the cost would be deducted from the employees paycheck.

lets say this store is located at mydomain.com (only available internally)

Now, we've been told by the accountants that we can no longer auto deduct from payroll and the employee needs to pay with a credit card or cash.

So i went to thawte.com and ordered an SSL cert to be on the safe side (even though the CC gateway is secure) and they told me i need to drop the .com from the domain name

Not wanting to mess with a system thats perfectly functional, i created another DNS entry that just points to mydomain (no .com) and left the old one in there.

so they would go to just mydomain

On my Mac (OS X 10.6) i can hit either one just fine

On Windows XP / Windows XP Embedded or Windows 7 (the vast majority of the pc's on our network) mydomain - returns nothing mydomain.com still works https mydomain.com works but says the cert is invalid (as it should, it was issued to mydomain - not mydomain.com)

my question is: why does it work on my Mac and not on a Windows PC (i get dhcp and dns just like any other pc on the network) and will removing the .com one from the DNS server resolve this?

I've done all the usual attempts - ipconfig /flushdns, ipconfig /renew and release

even going so far as to stop and restart DNS client on my Windows 7 box; rebooting and shutting down - adding a regedit entry something along the lines of SecureResponses and rebooting

nothing works... I think its the .com and the not conflicting in DNS but i'm not sure - and why not on OS X

We're closed on sunday and i'm going to remote in and see what happens if i remove the .com from DNS but any other ideas?

| improve this question | | | | |

On the problem machines try "domain.", note the trailing ".". The trailing period signifies an FQDN and should prevent windows from appending the internal domain name onto what looks to the OS like a host name.

You may want to use a two part domain name, shopmydomain.local, for instance and then create that zone in your internal DNS. MS doesn't recommend single part internal domain names so it may continue to be problematic.

| improve this answer | | | | |
  • still having a problem. changed mydomain to mydomain.local - nothing. the FQDN part makes sense to me - forgot about that. copied the intranet to a linux VM - reconfiged the VM to have a hostname of mydomain - no good :( apache is config'd correctly - it produces the page, i just cant hit it via mydomain - weird weird weird.... – lsiunsuex Nov 29 '10 at 15:21
  • What does nslookup return for mydomain.local and mydomain.local.? Use nslookup /? for syntax, it works on both Mac & PC's. – Ed Fries Nov 30 '10 at 5:23

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.