Forum Discussion

Bhanu_9561's avatar
Feb 11, 2013

DNS Issue while using GTM with regular DNS

Today, GTM is not used as primary DNS at our enterprise. GTM is authoritative for a few domains, and we have forwarders on the primary DNS for those domains. One such is wip.company.com.

 

Any DNS query within the wip.company.com domain is forwarded to GTM.

 

One of the app teams needs active/standby scenario for the two Data Centers we have, so they are pointing their machines to GTM as their primary DNS. Everything is fine with their app. The issue is with an existing login app which has a CNAME in the DNS which points to GTM.

 

applogin.company.com CNAME applogin.wip.company.com

 

The resolution for this url (critical app) is failing for this particular url for the app team.

 

GTM does not know about the company.com domain, so asks regular DNS (recursive lookup). DNS has a CNAME entry which it sends back to GTM. I would think GTM would resolve this, as it is SOA for the wip.company.com domain.

 

Here is what is sent back:

 

 

C:\dig>dig @gtm04.company.com applogin.wip.company.com

 

 

; <<>> DiG 9.5.0-P2 <<>> @gtm04.company.com applogin.company.com

 

; (1 server found)

 

;; global options: printcmd

 

;; Got answer:

 

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1960

 

;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0

 

 

;; QUESTION SECTION:

 

;applogin.company.com. IN A

 

 

;; ANSWER SECTION:

 

applogin.company.com. 2519 IN CNAME applogin.wip.company.com

 

 

;; AUTHORITY SECTION:

 

wip.company.com. 500 IN NS gtm04.company.com.

 

wip.company.com. 500 IN NS gtm04.company.com.

 

 

 

May be some loop prevention mechanism?

 

 

Any help is appreciated.

 

 

Thanks!

 

 

 

No RepliesBe the first to reply