Forum Discussion
P_K
Altostratus
AltostratusBIg-IP DNS Listener question
Hello Folks, I'm having hard time understanding how a listener and wide IP works in the Big-IP DNS realm. Hoping to get an answer here. I understand that Listener on Big-IP DNS listens and...
You need to delegate the zone for production.company.com from company.com
So the zone file for company.com contains the following records:
production.company.com NS ns1.production.company.com production.company.com NS ns2.production.company.com ns1.production.company.com A 1.1.1.1 ns2.production.company.com A 2.1.1.1So when someone queries www.production.company.com, they will send a NS query to a .com nameserver for company.com, and get a reply.
They then send a NS query to the company.com nameserver asking for a production.company.com nameserver.
The company.com nameserver replies that an NS record for production.company.com is at ns1.production.company.com, and to help you out, the A record for ns1.production.company.com is 1.1.1.1.
The client then sends a www.production.company.com A record request to 1.1.1.1 which resolves the WideIP for 1.1.1.1.
This is a standard DNS zone delegation, and your DNS provider or manager should be able to set this up without any difficulty at all.
Simon_Blakely
Employee
EmployeeYou need to delegate the zone for production.company.com from company.com
So the zone file for company.com contains the following records:
production.company.com NS ns1.production.company.com
production.company.com NS ns2.production.company.com
ns1.production.company.com A 1.1.1.1
ns2.production.company.com A 2.1.1.1So when someone queries www.production.company.com, they will send a NS query to a .com nameserver for company.com, and get a reply.
They then send a NS query to the company.com nameserver asking for a production.company.com nameserver.
The company.com nameserver replies that an NS record for production.company.com is at ns1.production.company.com, and to help you out, the A record for ns1.production.company.com is 1.1.1.1.
The client then sends a www.production.company.com A record request to 1.1.1.1 which resolves the WideIP for 1.1.1.1.
This is a standard DNS zone delegation, and your DNS provider or manager should be able to set this up without any difficulty at all.
P_KAltostratus
AltostratusThat's great explanation man!
Just to sum it up, i have 2 data centers which means i would just use one NS IP as listener per data center. So 1.1.1.1 is listener in DC 1 and 1.1.1.2 is the listener in DC2. does that look right?
- Simon_Blakely
Yes, that is correct.
- P_K
I came across a question while thinking through this. If i have 2 NS records on my public DNS provider for the FQDN i want to load balance and use one NS as listener at each data center.
Now, when a user query the fqdn and DNS provider responds with a Name server (Listener) IP of DC1 but actually i want user to end up on DC2, how can i make the request end up in DC2 rather than DC1. is it achieved through GTM sync group?
- Simon_Blakely
Where the DNS query is made (DC1 or DC2) does not affect which DC the resolved IP address is pointing to - that is determined by the rules governing IP resolution (GTM pools, priority, topology etc) and both GTMs have the same information via the GTM Sync group and iQuery.