Cisco Bug: CSCup77391 - ISDN GW DNS lookup issues when absolute rooted FQDN is not used
May 05, 2015
- Cisco TelePresence ISDN Gateway
Known Affected Releases
Symptom: ISDN GW DNS lookup issues when absolute rooted FQDN is not used Condition: - The GW has a domain name (DNS suffix) specified under Network -> DNS - The GW will always treat an address as an FQDN if the address has a trailing period/dot ('.'). For example: mcu.com. or mcu. (both are treated as FQDN). This is expected behaviour and defined in the RFC. This format is known as an absolute 'rooted' FQDN where the trailing '.' is for DNS root. - If however, an address doesn't end with a trailing dot, the resolver client will realize that it is not an absolute 'rooted' FQDN. In the case of ISDN GW, this results in its DNS resolver performing the following: For example, if the user is trying to resolve: a.com and has a DNS suffix configured with b.com, 1) It will first lookup will be: a.com.b.com. 2) If the first lookup fails, the resolver will then try: a.com While this is actually correct behaviour, the problem happens if the DNS server returns a successful reply to a.com.b.com and it is not what the user is expecting. Some users may expect a.com to be treated as an FQDN, when an absolute FQDN should in fact be: 'a.com.' . The problem is further exacerbated if the lookup is happening beyond user intervention (e.g. a DNS SRV lookup returns an FQDN without the trailing '.' due to misconfiguration and the GW then treats this as a non-FQDN address).
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases