bschwarting
asked on
Microsoft DNS, Sun Solaris, and Domain Alias
We recently made some additions to our DNS server to be locally authoritative for our domain. After this change our Sun Solaris box could no longer email internally to our exchange server. We figured out what the problem was, and a temporary fix, but it's just temporary. Looking for a permanent fix.
before DNS changes the email showed up as user@doman.com (correct)
after DNS changes the email shows up as user@www.domain.com (incorrect, and only an issue with the Sun box)
we figured out that if we removed the domain alias (in Microsoft DNS) to translate domain.com to www.domain.com it worked again and the emails started going to user@domain.com.
Ideas of how we can fix this permanently?
before DNS changes the email showed up as user@doman.com (correct)
after DNS changes the email shows up as user@www.domain.com (incorrect, and only an issue with the Sun box)
we figured out that if we removed the domain alias (in Microsoft DNS) to translate domain.com to www.domain.com it worked again and the emails started going to user@domain.com.
Ideas of how we can fix this permanently?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
i figured it out. i made them both an A record and it worked. they both resolve correctly now.
any reason i should do this?
any reason i should do this?
ASKER
sorry, any reason i shouldn't do this.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
>sorry, any reason i shouldn't do this.
I don't think there's a reason, but the way you were doing it originally was definitely broken - you are allowed (per RFC) to have a CNAME for www pointing to your domain name, but not the other way around.
Of course, Microsoft GUIs love to let you do things that violate RFCs - otherwise, they wouldn't be Microsoft, would they?
Cheers,
-Jon
I don't think there's a reason, but the way you were doing it originally was definitely broken - you are allowed (per RFC) to have a CNAME for www pointing to your domain name, but not the other way around.
Of course, Microsoft GUIs love to let you do things that violate RFCs - otherwise, they wouldn't be Microsoft, would they?
Cheers,
-Jon
ASKER
thanks for the help guys, split points to all.
answer accepted on Cyclops3590 because he got me thinking along the lines when he said, "is there a reason that the domain.com can't be the A record and the www.domain.com be the CNAME entry; just reverse the two."
i just used the 1st part.
answer accepted on Cyclops3590 because he got me thinking along the lines when he said, "is there a reason that the domain.com can't be the A record and the www.domain.com be the CNAME entry; just reverse the two."
i just used the 1st part.
ASKER
The--Captain,
I'm sure you are correct, per RFC, but I'm curious...
Why would I need a CNAME for a www record that is already covered in an A record?
Side Note: Yes, just like Microsoft :)
I'm sure you are correct, per RFC, but I'm curious...
Why would I need a CNAME for a www record that is already covered in an A record?
Side Note: Yes, just like Microsoft :)
CNAME is short for conical (sp?) name
A records associate an fqdn with an IP
CNAME creates an alias for an fqdn
example
www.example.com A 1.2.3.4
www2.example.com CNAME www.example.com
www3.example.com CNAME www.example.com
This way if you run virtual hosts on your web server (meaning serve out different pages depending upon url used to connect to it) you can take advantage of the CNAME entries. Also, if you need to change the IP of the web server (that hosts all the urls) then you only need to change one entry.
A records associate an fqdn with an IP
CNAME creates an alias for an fqdn
example
www.example.com A 1.2.3.4
www2.example.com CNAME www.example.com
www3.example.com CNAME www.example.com
This way if you run virtual hosts on your web server (meaning serve out different pages depending upon url used to connect to it) you can take advantage of the CNAME entries. Also, if you need to change the IP of the web server (that hosts all the urls) then you only need to change one entry.
ASKER
good explanation, thanks!
ASKER