Follow

Termination DNS Info

Please send outbound calls to the following:

DNS SRV: srv.lcr.thinq.com
OR
DNS A: a.lcr.thinq.com

 

Current IP's we are using with our DNS option:

192.81.237.60
192.81.236.31
192.81.236.32
192.81.237.61
 

To look up the DNS srv and a records for the LCRs as they appear to the internet, the following commands can be used to check how the records resolve using Google or other public DNS servers (Google example shown), note the the trailing “.” at the the end of the thinq.com domain is significant. It signifies that the DNS resolver should not append any other domain and must query the DNS root to find thinq.com. This is usually a misconfigured resolver.


For the SRV record:
dig: dig @8.8.8.8 _sip._udp.srv.lcr.thinq.com. SRV
host: host -t srv _sip._udp.srv.lcr.thinq.com. 8.8.8.8

nslookup:

1) nslookup
2) server 8.8.8.8
3) set type=srv
4) _sip._udp.srv.lcr.thinq.com.

To check the “smart” A records, use:
dig: dig @8.8.8.8 a.lcr.thinq.com. A

host: host -t a a.lcr.thinq.com. 8.8.8.8

nslookup:

1) nslookup
2) server 8.8.8.8
3) set type=a
4) a.lcr.thinq.com.


DNS commands for customers to try if there is an issue:
This is a list of commands that customers can try using their own DNS servers:


The SRV record:
dig: dig _sip._udp.srv.lcr.thinq.com. SRV

Example:

dig _sip._udp.srv.lcr.thinq.com. SRV

; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> _sip._udp.srv.lcr.thinq.com. SRV
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35685
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;_sip._udp.srv.lcr.thinq.com. IN SRV

;; ANSWER SECTION:
_sip._udp.srv.lcr.thinq.com. 60 IN SRV 200 50 5060 lcr-lb01.dfw.thinq.com.
_sip._udp.srv.lcr.thinq.com. 60 IN SRV 200 50 5060 lcr-lb02.dfw.thinq.com.
_sip._udp.srv.lcr.thinq.com. 60 IN SRV 100 50 5060 lcr-lb01.rdu.thinq.com.
_sip._udp.srv.lcr.thinq.com. 60 IN SRV 100 50 5060 lcr-lb02.rdu.thinq.com.

;; Query time: 4 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Tue Jan 14 18:30:01 UTC 2020
;; MSG SIZE rcvd: 180


host: host -t srv _sip._udp.srv.lcr.thinq.com.

Example:

host -t srv _sip._udp.srv.lcr.thinq.com.
_sip._udp.srv.lcr.thinq.com has SRV record 200 50 5060 lcr-lb02.dfw.thinq.com.
_sip._udp.srv.lcr.thinq.com has SRV record 100 50 5060 lcr-lb01.rdu.thinq.com.
_sip._udp.srv.lcr.thinq.com has SRV record 100 50 5060 lcr-lb02.rdu.thinq.com.
_sip._udp.srv.lcr.thinq.com has SRV record 200 50 5060 lcr-lb01.dfw.thinq.com.

 

nslookup:

1) nslookup
2) set type=srv
3) _sip._udp.srv.lcr.thinq.com.
Example:

"nslookup

> set type=srv
> _sip._udp.srv.lcr.thinq.com.
Server: 127.0.0.53
Address: 127.0.0.53#53

Non-authoritative answer:
_sip._udp.srv.lcr.thinq.com service = 200 50 5060 lcr-lb01.dfw.thinq.com.
_sip._udp.srv.lcr.thinq.com service = 200 50 5060 lcr-lb02.dfw.thinq.com.
_sip._udp.srv.lcr.thinq.com service = 100 50 5060 lcr-lb01.rdu.thinq.com.
_sip._udp.srv.lcr.thinq.com service = 100 50 5060 lcr-lb02.rdu.thinq.com."

Authoritative answers can be found from:


The “Smart” A record:
dig: dig a.lcr.thinq.com. A

Example:

dig a.lcr.thinq.com. A

; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> a.lcr.thinq.com. A
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64345
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;a.lcr.thinq.com. IN A

;; ANSWER SECTION:
a.lcr.thinq.com. 60 IN A 192.81.237.60

;; Query time: 3 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Tue Jan 14 18:35:49 UTC 2020
;; MSG SIZE rcvd: 60

host: host -t a a.lcr.thinq.com.

Example:

host -t a a.lcr.thinq.com.
a.lcr.thinq.com has address 192.81.237.60

nslookup:

1) nslookup
2) set type=a
3) a.lcr.thinq.com.
Example:

nslookup

> set type=a
> a.lcr.thinq.com.
Server: 127.0.0.53
Address: 127.0.0.53#53

Non-authoritative answer:
Name: a.lcr.thinq.com
Address: 192.81.237.61


>

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk