- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- DNS entries to Alias two completely different doma...
Operating System - HP-UX
1752285
Members
4901
Online
108786
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-14-2004 03:46 PM
тАО03-14-2004 03:46 PM
DNS entries to Alias two completely different domains.
Hi,
Is it appropriate to use CNAME to Alias a machine in a completely different domain such that it appears to be a machine in a domain "controlled" (if that's the right word) by our Primary DNS?
ie. I want fred.xxx.net to appear to be in our domain as fred.yyy.com - our DNS forwards to this host (the .net one) which is also a DNS in that domain (and will eventually be an Active Directory server to all our domains). It is accessible directly from our network.
An nslookup to our DNS presently shows it up as it really is.
We have used CNAMES extensively within many of the domains defined in our DNS system but it is usually (well, always as far as I can tell) just an aliasing of another name to the real one within the same domain or sub- domain.
ie..yyy.com aliased to fred.yyy.com
thanks in advance for any assistance -I'm just treading carefully as we have a fairly complex DNS setup, and I really don't know that testing this in isolation is going to prove what might happen in the real world.
I read somewhere that DNS's should not be aliased???
regards
David
Is it appropriate to use CNAME to Alias a machine in a completely different domain such that it appears to be a machine in a domain "controlled" (if that's the right word) by our Primary DNS?
ie. I want fred.xxx.net to appear to be in our domain as fred.yyy.com - our DNS forwards to this host (the .net one) which is also a DNS in that domain (and will eventually be an Active Directory server to all our domains). It is accessible directly from our network.
An nslookup to our DNS presently shows it up as it really is.
We have used CNAMES extensively within many of the domains defined in our DNS system but it is usually (well, always as far as I can tell) just an aliasing of another name to the real one within the same domain or sub- domain.
ie.
thanks in advance for any assistance -I'm just treading carefully as we have a fairly complex DNS setup, and I really don't know that testing this in isolation is going to prove what might happen in the real world.
I read somewhere that DNS's should not be aliased???
regards
David
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-14-2004 06:34 PM
тАО03-14-2004 06:34 PM
Re: DNS entries to Alias two completely different domains.
CNAMEs are OK, provided they are the only RR, and they should not be used as targets of for NS and MX RR (RFC 2181 "Clarifications to the DNS Specification", 10.3):
10.3. MX and NS records
The domain name used as the value of a NS resource record, or part of the value of a MX resource record must not be an alias. Not only is the specification clear on this point, but using an alias in either of these positions neither works as well as might be hoped, nor well fulfills the ambition that may have led to this approach. This domain name must have as its value one or more address records. Currently those will be A records, however in the future other record types giving addressing information may be acceptable. It can also have other RRs, but never a CNAME RR.
10.3. MX and NS records
The domain name used as the value of a NS resource record, or part of the value of a MX resource record must not be an alias. Not only is the specification clear on this point, but using an alias in either of these positions neither works as well as might be hoped, nor well fulfills the ambition that may have led to this approach. This domain name must have as its value one or more address records. Currently those will be A records, however in the future other record types giving addressing information may be acceptable. It can also have other RRs, but never a CNAME RR.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-16-2004 01:49 AM
тАО03-16-2004 01:49 AM
Re: DNS entries to Alias two completely different domains.
I cannot speak to the standard, but I can say that this functions perfectly in our environment.
A MUCH larger company purchased my company, and our ERP was moved to the HQ datacentre. All we did was alias* localerp.localsite.oldcompany.com to oldcomapnyerp.datacenter.hq.bigcorp.com
When we reintegrated our DNS hierarchy later on, we ended up aliasing everything in localsite.oldcompany.com to Bizgroup.bigcorp.com to ease migration woes. localsite.oldcompany.com still exists, but only as a container for CNAMEs in an un unmaintained state.
*This story is true; the names have been changed to protect the cowardly, er ah innocent.
A MUCH larger company purchased my company, and our ERP was moved to the HQ datacentre. All we did was alias* localerp.localsite.oldcompany.com to oldcomapnyerp.datacenter.hq.bigcorp.com
When we reintegrated our DNS hierarchy later on, we ended up aliasing everything in localsite.oldcompany.com to Bizgroup.bigcorp.com to ease migration woes. localsite.oldcompany.com still exists, but only as a container for CNAMEs in an un unmaintained state.
*This story is true; the names have been changed to protect the cowardly, er ah innocent.
There have been Innumerable people who have helped me. Of course, I've managed to piss most of them off.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP